COULDINJECT
Home Forums Wiki Store About us CISS Support
Sign in
COULDINJECT / ANANTA

ANANTA Project Statement

The ANANTA project's position, development status, technical scope, creative work, rights and cooperation statements.

Statement date: 2026-09-19

SupportPrivacy PolicyTerms of Service ANANTA Project StatementANANTA Content PolicyDownload original (.md)

This page provides a translation of the current document. Translation does not change its original publication or effective date. Please contact Support with any questions about the wording.

This document preserves the statements made on September 19, 2026. For subsequent rights notices and handling updates, see the public handling record. View the public handling record

Contents
CouldInject ANANTA Compatible ServerREADME / Accompanying Statement for a Non-Public Server, Fan Creations, Rights, Cooperation and Risk CommunicationImportant Information / Please Read FirstNavigationPart One: Project Positioning, Non-Public Status and Advance Statements1. About CouldInject2. Purpose and Scope of This README3. Non-Public Status, Build Terminology and Scope of Authorization4. Project Background5. ANANTA-Related Packages Previously Received6. Server Development, Builds and Maintenance7. Why the Server Has Not Been Publicly Released8. Why This README Is Included in Advance9. If the Server Is Found Circulating beyond Its Intended Scope10. Infrastructure Changes Planned for September 24, 2026Part Two: Local Operation, Security, Compatibility and Support11. Local Deployment and Network Information12. If Unusual External Connections Are Detected13. Third-Party Modified Versions14. Basic Security Advice15. What CouldInject Develops, Maintains and Supports16. What CouldInject Does Not Provide17. Client Compatibility18. Current Known Issues and Repair Plan19. Bug and Support-Ticket Rules20. Logs and PrivacyPart Three: Third-Party Rights, Usage Boundaries and User Creations21. ANANTA’s Original Works, Assets and Intellectual Property22. Relationship with NetEase and ANANTA’s Official Representatives23. Content-Publication Requirements before September 24, 202624. Content Publication and Third-Party Rights25. User Creations, Recordings and Fan Works26. Using the Server Does Not Confer ANANTA Rights27. The Compatible Server Does Not Authorize Third-Party Content28. Respect ANANTA and Relevant Rights Requirements before Publishing29. Unauthorized Content, NDAs and Confidentiality Obligations30. NDAs, Testing Agreements and Users’ Own Contractual Obligations31. CouldInject Does Not Assert Infringement against Creators Solely for Normal Server Use32. Users’ Works Do Not Automatically Represent CouldInject33. Independent User Publication and CouldInject’s Liability Boundaries34. If Clearly Unauthorized Content Is Discovered35. Independent User Creation, Voluntary Contributions and Submitted Materials36. Boundaries on Server Modification, Copying and RedistributionPart Four: CouldInject’s Own Fan Creations and AI Production Principles37. CouldInject’s Own Original Contributions38. We Do Not Claim a Monopoly over ANANTA Fan Creation39. Fan Creations and Legal Exceptions40. Generative Artificial Intelligence41. AI Outputs and CouldInject’s Rights Claims42. Transparency about AI Content43. Real People, Voices and Personality-Related Content44. Public Information, Sources and Risk Assessment45. Fan-Work Content and Official Story46. Content Risk Control47. Production Records and Evidence of Rights48. Suggested Short Rights StatementPart Five: Republication, Open Source, Community Cooperation and Risk Sharing49. Sharing Does Not Mean Relinquishing Rights50. Limited Republication License for Original Documents and Principles for Republishing Fan WorksLimited Republication License for DocumentsPrinciples for Non-Commercial Republication of Other Fan Content51. Open-Source Projects and ANANTA Assets Must Be Kept Separate52. Community Cooperation We Welcome53. Fee-Charging Communities54. Joint Creation55. Cooperation Does Not Mean Mutual Endorsement56. Sharing Risk Experience between Communities57. Boundaries of Risk Communication58. Our Approach to Community DisputesPart Six: Rights Contacts, Risk Communication and Dispute Handling59. We Believe Proactive Communication Is Very Important60. Rights Claims, Unusual Circulation and Contacting UsEmailSupport Center61. Communication with NetEase and Other Rights Holders62. Communication with Government and Regulatory Authorities63. Handling Rights Notices64. Rights Claims to Video or Hosting Platforms65. We Prefer to Resolve the Actual Issue First66. Where a Platform Complaint Has Already Been Made67. Correcting and Withdrawing ContentPart Seven: Original Legal References, Policy Updates and Liability Boundaries68. International Copyright Principles Cited in the Original Fan-Creation Statement69. Chinese Copyright Rules Cited in the Original Fan-Creation Statement70. United States Copyright Rules Cited in the Original Fan-Creation Statement71. European Union Copyright Rules Cited in the Original Fan-Creation Statement72. Legal and Policy ReferencesInternationalChinaUnited StatesEuropean Union73. Legal Updates74. This README Is Not a Public Software-Release Announcement or Third-Party Authorization75. Liability Boundaries of This READMEPart Eight: Principles, Final Statement and Contact Information76. Our Principles77. Final Statement

CouldInject ANANTA Compatible Server

README / Accompanying Statement for a Non-Public Server, Fan Creations, Rights, Cooperation and Risk Communication

Version: 2026.09 (consolidated revised draft)
Statement Date: 2026-09-19
Community: CouldInject
Since: 2016
Server Status: Not yet publicly released


Important Information / Please Read First

As of September 19, 2026, CouldInject has not publicly released the CouldInject ANANTA Compatible Server.

This README accompanies relevant builds or materials solely as a project description and advance statement. Its primary purpose is to explain the project’s origins, boundaries of rights, non-public status and contact channels if Server files circulate beyond their originally intended recipients, actual authorization or intended use scenarios.

This README is not a public-release announcement, an invitation to download, an open-testing notice or a software license for the public at large. Files appearing externally, being downloadable, retaining CouldInject branding or including this README do not mean that CouldInject has proactively released them to the public, authorized distribution through that channel or approved a third-party version.

Publication of CouldInject’s own fan creations, community articles, videos, images or cooperation information is a separate matter from whether Server software, source code, related builds or non-public materials are public. Statements here about fan creations, republication, open-source components and cooperation should not be expanded into permission to obtain, use or redistribute this Server.

If you cannot confirm a file’s source or the scope of authorization, pause execution and stop forwarding it. Contact the email address or Support Center at the end of this document for confirmation. Do not re-upload the complete Server or sensitive materials in public spaces.

September 24, 2026 concerns previously planned infrastructure changes and phased branding arrangements. This README does not thereby establish a public-release date for the Server or automatically lift its non-public status or any restrictions that actually apply.


Navigation

  • Part One: Project Positioning, Non-Public Status and Advance Statements
  • Part Two: Local Operation, Security, Compatibility and Support
  • Part Three: Third-Party Rights, Usage Boundaries and User Creations
  • Part Four: CouldInject’s Own Fan Creations and AI Production Principles
  • Part Five: Republication, Open Source, Community Cooperation and Risk Sharing
  • Part Six: Rights Contacts, Risk Communication and Dispute Handling
  • Part Seven: Original Legal References, Policy Updates and Liability Boundaries
  • Part Eight: Principles, Final Statement and Contact Information

Where this document refers to fan content, documents or announcements made or published by CouldInject, “publication” refers only to that content; it does not mean the current Server has been publicly released. Legal references from the original fan-creation statement are retained separately. Listing them does not constitute a new verification of legal compliance or third-party authorization.


Part One: Project Positioning, Non-Public Status and Advance Statements

1. About CouldInject

CouldInject is an invitation-only gaming technology community founded in 2016.

The community has long worked on:

  • Gaming technology research;
  • Compatibility analysis;
  • Research into program behavior;
  • Development tools;
  • Security analysis;
  • Organization of reference materials;
  • Technical exchange;
  • Support for users’ issues.

It continues to serve community members through the community, Wiki, ticketing system and other technical-support channels.

CouldInject respects the copyrights, trademarks, trade secrets, privacy rights and other lawful rights and interests of game developers, publishers, players, creators and other third-party rights holders.

CouldInject is not ANANTA’s developer, publisher or official operator.

The CouldInject ANANTA Compatible Server discussed in this README is a local compatible-server project independently developed and maintained by CouldInject in response to community users’ actual technical-support needs.

In addition to those technical activities, CouldInject and community members may create unofficial fan works involving games, characters, fictional worlds, technology and related cultural content that interest them.

This README also explains the Compatible Server’s origins, non-public status, usage and distribution boundaries, together with CouldInject’s principles concerning its own fan creations, creators’ rights, community cooperation and risk communication.

2. Purpose and Scope of This README

This README is a project description and advance statement accompanying builds or materials associated with the CouldInject ANANTA Compatible Server.

As of the date of this statement, September 19, 2026, CouldInject has not publicly released this Server.

The primary purpose of preparing and including this README is to explain in advance the project’s origins, unofficial nature, third-party rights, usage boundaries and contact channels if server files, related builds or materials circulate beyond their originally intended recipients, actual authorization or intended use scenarios, reducing misunderstanding and the risk of further distribution.

This document is not:

  • A public-release announcement for the server;
  • An invitation to download or an open-testing notice for the public;
  • A software-use or redistribution license granted to any unspecified recipient;
  • Approval of external download pages, cloud drives, mirrors, repositories or third-party operated services;
  • Retroactive authorization of any unauthorized circulation;
  • A license to use ANANTA, NetEase or other third-party content.

This README covers:

  • The server’s origins, development, builds, maintenance and non-public status;
  • Unexpected circulation of server files, source verification and security communication;
  • Local operation, compatibility, known issues, logs and privacy;
  • Boundaries of rights and responsibilities when users create content with the tools;
  • CouldInject’s own fan creations, AI-assisted creation and digital-production principles;
  • Distinctions among original contributions, republication, open-source projects and third-party assets;
  • Non-commercial community cooperation, restrictions concerning fee-charging communities and risk sharing;
  • Contact and communication with rights holders, creators, businesses and public authorities.

Statements about fan creations, republication or cooperation should be understood according to their respective subject matter and scope. They cannot be expanded into permission to distribute the unreleased Server or related non-public materials.

3. Non-Public Status, Build Terminology and Scope of Authorization

This project is not currently software publicly released to the public at large.

The terms “CouldInject original build,” “CouldInject’s own build” and “version developed, built and maintained by CouldInject” distinguish the project’s origins from third-party modified, repackaged or impersonated versions. They do not mean that the version has been publicly released.

“CouldInject” in these terms always means this community itself, not NetEase, ANANTA or its official operator.

Whether a particular build may be received, run, tested, copied, modified or redistributed depends on the software license that actually applies, CouldInject’s express authorization and existing valid agreements between the parties. Permission cannot be inferred solely because:

  • A file can be downloaded from the internet or third-party channels;
  • The file includes this README;
  • The file name, interface or archive contains the CouldInject name or logo;
  • The file runs normally;
  • The file’s hash matches an original build;
  • Other users have obtained, run or forwarded the file;
  • CouldInject or community members have published related videos, images, articles or other fan works.

Whether a build’s origin is genuine and whether obtaining, using, copying or redistributing it is authorized are separate questions.

Publication of fan works does not mean that the production tools, Server, source code, configurations or related non-public materials have been made public.

Any future change in the server’s public status will be governed by an explicit, verifiable statement specifically concerning that server issued by CouldInject at that time. This README does not promise a future public release or establish a date on which a release becomes public automatically.

4. Project Background

This project originated in technical-support requests submitted by CouldInject community users.

After the community received ANANTA-related technical questions, security tickets and compatibility requests, some users wanted CouldInject to provide further local-server support for:

  • Local operation;
  • Technical research;
  • Functional testing;
  • Compatibility verification;
  • Reproducing bugs;
  • Technical exchange.

Following an internal assessment of those needs, CouldInject decided that its development team would independently build and maintain a compatible server for the client.

The project is therefore positioned as:

A third-party local compatible-server project independently designed, developed and continuously maintained by the CouldInject gaming technology community in response to users’ technical-support needs.

This project is not:

  • NetEase’s official server software;
  • An official ANANTA server;
  • A modified version of NetEase server software;
  • A cracked version of official server software;
  • A repaired version of leaked server software;
  • A re-release of official server software;
  • A private server authorized by NetEase to operate;
  • A replacement for ANANTA’s official online services.

5. ANANTA-Related Packages Previously Received

Before formal development of this project, CouldInject received files described by their submitters as “leaked ANANTA packages” in connection with security tickets from community users.

CouldInject’s handling of those files was limited to necessary security analysis.

The main checks concerned:

  • Viruses;
  • Trojans or malicious programs;
  • Unusual network connections;
  • Data theft;
  • Suspicious startup entries;
  • Unknown additional programs;
  • Potential effects on the security of community users’ devices and data.

The main purpose was to assess basic security risks where community users had already encountered files of unknown origin, and, as far as possible, prevent users running unknown programs from suffering:

  • Viruses;
  • Trojans;
  • Malicious injection;
  • Data theft;
  • Account risks;
  • Other threats to device and data security.

For those files, CouldInject:

  • Did not use them as the code base for the current compatible server;
  • Did not use server programs in them as the development basis for this project;
  • Did not modify or build the current server from their contents;
  • Did not repackage and release server programs contained in them;
  • Did not publicly distribute those packages as part of an official CouldInject project;
  • Did not substitute their contents for this project’s independent development work.

After the security checks ended, CouldInject did not continue server development based on that package.

The earlier security-analysis work and the current compatible-server development process are independent of each other.

6. Server Development, Builds and Maintenance

The current CouldInject ANANTA Compatible Server is independently designed, developed and continuously maintained by CouldInject’s development team.

Development uses the following as the basis for compatibility:

  • The client’s actual operating state;
  • Protocol interactions;
  • Observable program behavior;
  • Verifiable functional behavior.

The relevant server modules are independently designed and implemented by CouldInject’s development team, including but not limited to:

  • Overall server architecture;
  • Protocol adaptation;
  • Request and response handling;
  • State management;
  • Data processing;
  • Game-function logic;
  • NPC behavior logic;
  • Scene-state handling;
  • Gameplay logic;
  • Client-compatibility modules;
  • Related runtime and scheduling modules.

In developing this project, CouldInject did not use NetEase’s official server programs, official server source code or any third-party leaked server as a development base, and did not modify, port or repair those materials for re-release.

The server code, core logic and operating mechanisms in the currently maintained build are implemented by CouldInject itself.

This project:

  • Is independently developed by CouldInject;
  • Is built by CouldInject;
  • Is continuously maintained by CouldInject;
  • Is an independent server implementation developed for client-compatibility needs;
  • Contains no original NetEase server source code;
  • Contains no original NetEase server programs;
  • Is not a modified version of NetEase’s server;
  • Is not a repaired version of a leaked server;
  • Does not use the previously mentioned package of unknown origin as its development base.

For its own original builds, within the scope of support actually provided, CouldInject undertakes:

  • Development;
  • Version maintenance;
  • Compatibility adjustments;
  • Bug fixes;
  • Technical support.

Those development, build, maintenance and support activities should not be understood as a public release of the server.

7. Why the Server Has Not Been Publicly Released

CouldInject did not release the compatible server to the public after completing early development. As of this statement’s date, the Server remains unreleased to the public.

This is a project-management and risk-control measure taken proactively by CouldInject.

Before this project took shape, CouldInject had encountered files of unknown origin described by submitters as leaked ANANTA packages through community security tickets. Publicly releasing the compatible server immediately around that time could have led outsiders to link two independent technical processes incorrectly.

Possible misunderstandings include:

  • Believing CouldInject first made those unknown-origin files public;
  • Believing CouldInject participated in their leak;
  • Believing the current server comes directly from those files;
  • Believing CouldInject modified and re-released those server programs;
  • Confusing community security analysis with current server development;
  • Mistaking CouldInject for a principal participant in the relevant leak.

None of those situations reflects the project’s actual circumstances.

Accordingly, during the project’s early stages, CouldInject chose not to release it publicly for the time being, while continuing to complete:

  • Confirmation of the independent development process;
  • Documentation of project origins;
  • Code maintenance;
  • Compatibility verification;
  • Security checks;
  • Organization of the version-release system;
  • Infrastructure changes;
  • Improvements to community rules;
  • Alignment with the User Agreement and privacy rules;
  • Improvements to project explanations and support documentation.

Maintaining non-public status is a proactive project-management and risk-control arrangement, not a promise of future public release.

It does not mean that the current server was developed from the unknown-origin files previously received.

8. Why This README Is Included in Advance

Preparing and including this README does not mean that CouldInject has now decided to release the Server publicly.

It primarily addresses a possible situation: server files intended for specified recipients or expressly authorized uses may enter unintended channels or reach unintended recipients through forwarding, uploads, mirrors, repackaging or other causes.

Even before a public release, it is necessary to explain in advance:

  • The project’s actual development origins and unofficial nature;
  • The distinction between earlier security analysis and current server development;
  • That files appearing on third-party channels do not mean CouldInject proactively released them publicly;
  • That an included README or retained branding does not give third parties distribution authorization;
  • That original builds, files of unknown origin and third-party modified versions require separate verification;
  • That the technical capability to run locally does not provide permission to publish third-party content;
  • That users’ works, CouldInject’s fan works and Server software are distinct subjects;
  • How to contact CouldInject about unusual circulation, security issues or rights issues.

This README also retains existing compatibility, known-issue and support information for the intended recipients and users within the actual scope of authorization.

Providing these explanations is not an invitation for the public to download, test, sell, mirror or operate the Server.

This README is an advance explanation, not a public-release statement for the server.

9. If the Server Is Found Circulating beyond Its Intended Scope

If you find a purported CouldInject ANANTA Compatible Server on an unknown cloud drive, in a public group, forum, resource site, code or file hosting platform, paid resource package, third-party launcher or other unconfirmed channel, do not judge its origin or authorization solely from its name or accompanying explanation.

Externally available files may be original builds circulating without permission, modified versions, versions bundled with additional programs or entirely impersonated versions. Until verified, they should not all be presumed to be original, malicious or authorized versions.

If you are not an intended recipient or cannot confirm the actual scope of authorization, please:

  • Pause execution and stop forwarding files whose source and permissions are unclear;
  • Do not continue mirroring, selling or re-uploading them, or make them available as public resources;
  • Confirm their origins and permitted uses through the email or Support Center listed in this README;
  • Preferably provide the discovery page, link, time, file name, version number, file hash and necessary redacted screenshots;
  • Do not re-upload the complete Server, access credentials or other non-public materials in public merely to demonstrate the situation.

If subsequent verification requires a file submission, first confirm an appropriate receiving method with CouldInject.

The appearance of such files does not itself mean that CouldInject has proactively released them publicly, authorized distribution, approved the channel or ratified the third party’s actions.

Assessments of external files’ origins and specific conduct should be based on verifiable facts. This statement does not prejudge every instance of external circulation as a leak committed by a particular party.

These explanations also do not exclude CouldInject’s corresponding liability for conduct it actually performs, participates in, controls or is legally responsible for.

10. Infrastructure Changes Planned for September 24, 2026

Under CouldInject’s current infrastructure plan, some community servers, release systems and core service infrastructure are planned to migrate or switch gradually to infrastructure located in the United States (US), beginning September 24, 2026.

The changes mainly concern CouldInject’s own:

  • Core community services;
  • Project-release environment;
  • File-distribution system;
  • Technical-support system;
  • Version-maintenance facilities;
  • Basic community services.

These changes are CouldInject’s own technical-architecture, infrastructure and operational arrangements.

A change in infrastructure location does not change the project’s development origins or these facts:

  • The current compatible server is independently developed by CouldInject;
  • It is not NetEase’s official server;
  • It is not a modified version of NetEase’s official server;
  • It is not a derivative development of a leaked server;
  • It does not use the previously mentioned unknown-origin files as its code base;
  • CouldInject does not thereby acquire ANANTA- or NetEase-related intellectual property;
  • Rights in ANANTA and related content remain with the respective rights holders.

CouldInject does not regard a change in infrastructure location, by itself, as a basis for exemption from intellectual-property, contractual or other legal liability.

The infrastructure changes primarily aim to further unify community services, version releases, maintenance environments and long-term technical support.

In this README, September 24, 2026 refers to the infrastructure plan above, not a public-release arrangement for this Server.

Infrastructure migration, domain or system changes, community announcements and branding-rule changes do not automatically change the Server’s non-public status or lift existing authorization limits, confidentiality agreements or third-party rights restrictions.


Part Two: Local Operation, Security, Compatibility and Support

11. Local Deployment and Network Information

The compatible server developed and built by CouldInject itself uses a local-deployment model.

Its core functions do not require any of the following to operate normally:

  • CouldInject cloud servers;
  • Remote APIs;
  • Online authorization servers;
  • Advertising servers;
  • Telemetry servers;
  • Remote-control platforms.

Under normal circumstances, CouldInject’s original server builds will not proactively upload the following to CouldInject or unknown public-internet servers under the pretext of running the server:

  • Local game data;
  • Local private files;
  • Account passwords;
  • Local documents;
  • Other personal data unrelated to server operation.

Please note:

Normal communication between a client and local server through localhost, loopback, a local-area network or a user-configured network is not the abnormal public-internet data transmission referred to here.

“Local deployment” here mainly means:

CouldInject’s original server build itself does not depend on unknown public-internet servers to perform its core functions.

12. If Unusual External Connections Are Detected

If a purported CouldInject server does any of the following:

  • Continuously connects to unknown public IP addresses;
  • Accesses unknown domains;
  • Uploads local files;
  • Uploads user data;
  • Requests account passwords unrelated to running the server;
  • Downloads additional unknown executables;
  • Starts unknown background processes;
  • Establishes unexplained remote connections;

Stop running that version immediately and first check its download source.

The program may be a third-party version produced by:

  • Modification;
  • Tampering;
  • Injection;
  • Repackaging;
  • Bundling;
  • Extensive unofficial alteration;
  • Redistribution;

Of files obtained by that third party. These possibilities require verification. Unusual external connections alone do not establish that third-party tampering necessarily caused them.

Third parties can copy CouldInject’s:

  • Project name;
  • File names;
  • Logo;
  • UI;
  • README;
  • Program icons.

Consequently, a program’s name, logo or interface alone cannot prove that it is an original CouldInject build, much less that public distribution is authorized.

13. Third-Party Modified Versions

This README alone cannot prevent third parties from modifying files they obtain, and CouldInject cannot control the specific behavior of their modified versions.

CouldInject cannot guarantee the safety of the following in third-party modified, repackaged or republished versions:

  • Network behavior;
  • Data collection;
  • DLLs;
  • Injection modules;
  • Launchers;
  • Updaters;
  • Additional scripts;
  • Remote-control modules;
  • Other added programs.

If you suspect that you downloaded a modified version, please provide CouldInject with as much of the following as possible:

  1. The acquisition page, download address or forwarding source;
  2. The third party’s display or release page, if any;
  3. The file’s version number;
  4. Its hash;
  5. Firewall records;
  6. Domains involved in unusual connections;
  7. Unusual IP addresses;
  8. Antivirus reports;
  9. Steps that reliably reproduce the abnormal behavior.

CouldInject may compare the files and program behavior against its original build as necessary.

This can help determine whether a program has been modified by a third party and reduce the risk of other community users encountering malicious versions.

14. Basic Security Advice

Running the local compatible server does not require users to give CouldInject:

  • NetEase account passwords;
  • Email passwords;
  • Payment passwords;
  • Bank-card information;
  • Identity documents;
  • Private keys;
  • Tokens unrelated to operation;
  • Remote-control accounts.

If a purported CouldInject version requests this information, stop running it immediately and recheck the file’s source.

15. What CouldInject Develops, Maintains and Supports

The current project’s development, maintenance and support within the actual scope of authorization mainly cover:

  • The independently developed local compatible server;
  • Server configuration;
  • Server version updates;
  • Bug fixes;
  • Client-compatibility adjustments;
  • Technical documentation;
  • Known-issue descriptions;
  • Ticket-based support;
  • Server-related technical maintenance.

Listing what the project contains or maintains does not mean those materials have been made available to the public at large.

16. What CouldInject Does Not Provide

CouldInject does not provide:

  • The official ANANTA client;
  • Official NetEase accounts;
  • Official NetEase online services;
  • Official NetEase servers;
  • Official NetEase server source code;
  • Official NetEase server programs;
  • NetEase internal server files;
  • NetEase’s non-public internal technical materials;
  • Official NetEase commercial authorization;
  • Official ANANTA operation services;
  • Blanket copyright permission for third-party ANANTA content;
  • Authorization allowing users to bypass their own NDAs or other confidentiality obligations.

Users should independently confirm the lawful origin and appropriate usage permissions for third-party:

  • Clients;
  • Files;
  • Assets;
  • Models;
  • Audio;
  • Videos;
  • Images;
  • Other content;

That they use.

17. Client Compatibility

CouldInject’s server is an independent compatible implementation.

Because it is not the official server, some client behavior may differ from the official environment, including but not limited to:

  • Numerical values;
  • State synchronization;
  • NPC behavior;
  • UI state;
  • Story triggers;
  • Scene state;
  • Gameplay logic;
  • Client versions;
  • Protocol-compatibility issues.

These issues will continue to be fixed and improved as development progresses.

The following observed in the Compatible Server:

  • Story triggers;
  • NPC behavior;
  • Feature states;
  • Numerical behavior;
  • Scene states;
  • Other runtime results;

Should not be treated as confirmation of ANANTA’s released version, official story, future versions or official design merely because they appear in the Compatible Server.

18. Current Known Issues and Repair Plan

The following issues have been confirmed and included in CouldInject’s current repair plan.

If you encounter exactly the same issue, please do not submit multiple duplicate tickets.

Current known issues include:

  • Buying property through the in-game phone Compatibility problems following a recent server-protocol upgrade.

  • Taking photos through the in-game phone Compatibility problems following a recent server-protocol upgrade.

  • Akasha Assistant (阿卡夏助手)

  • Console one-click action unlock

  • Console one-click journal unlock

  • Console one-click relationship unlock

  • Console one-click talent unlock

  • Adding talent points through the console

  • Character statistics panel

  • Character health and related state synchronization

  • Midnight Echo (午夜回响)-related gameplay Including dancing and dice games.

  • Sonic Boom (音爆)-related gameplay Including performance cheering, playing instruments and darts.

  • UI interaction key for special apartment elevators

  • Patrol-officer patrol gameplay Some causes preventing the feature from working correctly have been identified.

  • Some stories associated with patrol-officer patrols

  • Bowling gameplay

  • Car behavior trees

  • NPC behavior trees

  • Low-detail car model loading logic

  • Low-detail NPC model loading logic

These items are current near-term priorities.

Under the near-term development plan as of this statement’s date, September 19, 2026, CouldInject will seek to complete fixes and builds for more of these issues, and updates within the existing support scope, during the following two weeks.

Actual repair timing may be affected by:

  • Issue complexity;
  • Changes to client protocols;
  • Feature dependencies;
  • Test results;
  • Client-version changes;
  • Newly discovered compatibility problems.

The timing is therefore a current development plan, not an absolute completion-date commitment.

These repairs and version updates are not a plan or commitment to release the server publicly.

19. Bug and Support-Ticket Rules

If an issue is already listed under “Current Known Issues,” please do not create multiple tickets for the same issue.

Duplicate tickets will not raise an issue’s priority.

You may submit a ticket normally if you discover:

  • A new bug;
  • Behavior clearly different from a known issue;
  • A new reliable reproduction method;
  • A new compatibility problem after an update;
  • A new security issue.

Please preferably include:

  • The version;
  • Where the issue occurs;
  • The exact actions taken;
  • The expected result;
  • The actual result;
  • Whether it reproduces reliably;
  • Relevant logs;
  • Relevant screenshots.

Complete reproduction information helps the development team locate issues more quickly.

Ordinary bugs, source-verification questions and security issues may be discussed through the relevant support channels. The ability to submit a ticket does not give the submitter permission to obtain, use or redistribute the Server.

20. Logs and Privacy

If troubleshooting requires logs to be submitted to CouldInject, provide only information necessary to resolve the issue.

Before submitting, check whether logs contain:

  • Passwords;
  • Tokens;
  • Private keys;
  • Identity information;
  • Payment details;
  • Personal data unrelated to troubleshooting.

Do not proactively submit sensitive personal information in public community spaces.

For data-processing rules for the CouldInject website and related community services, see:

User Agreement: https://couldinject.com/terms.php

Privacy Policy: https://couldinject.com/privacy.php


Part Three: Third-Party Rights, Usage Boundaries and User Creations

21. ANANTA’s Original Works, Assets and Intellectual Property

ANANTA and CouldInject are independent projects.

Rights in the ANANTA (《无限大》) name, trademarks, characters, fictional world, artwork, models, animation, music, sound effects, story, text, game client, official videos, official promotional materials and other protected original content belong to NetEase and/or the other relevant rights holders.

CouldInject respects those rights holders’ intellectual property.

CouldInject:

  • Does not claim ANANTA’s copyright;
  • Does not claim ANANTA’s trademarks;
  • Does not claim NetEase’s intellectual property;
  • Does not operate ANANTA on NetEase’s behalf;
  • Does not provide official servers on NetEase’s behalf;
  • Does not provide technical support on NetEase’s behalf;
  • Has no right to grant third parties commercial-use rights in ANANTA content;
  • Does not acquire rights in ANANTA’s original works by developing the Compatible Server;
  • Does not acquire rights in ANANTA’s original works because users create content with the Compatible Server.

Names appearing in this document, such as:

  • ANANTA;
  • 网易;
  • NetEase;
  • NetEase Games;
  • Naked Rain;

Are used only to identify the relevant works, client, compatibility target or technical environment.

Their appearance does not indicate official authorization, approval or endorsement.

CouldInject respects rights statements made by NetEase, NetEase Games, Naked Rain and other relevant rights holders concerning ANANTA-related assets that they expressly claim to own, control or hold rights in under law.

CouldInject does not claim ownership of ANANTA’s original works by making fan creations.

CouldInject does not claim:

  • To own ANANTA;
  • To own ANANTA’s original characters;
  • To own ANANTA’s original fictional world;
  • To own NetEase’s trademarks;
  • To own ANANTA’s official story;
  • To own official game assets;
  • To own official game models;
  • To own official music or sound effects;
  • Authority to license ANANTA content to third parties on NetEase’s behalf;
  • Exclusive rights in ANANTA’s original works arising from fan creation.

Where an asset involves complex ownership involving NetEase, partners, music rights holders, actors, voice performers, external creators or other third parties, the actual verifiable rights and applicable rules govern.

CouldInject’s respect for rights statements should not be interpreted as an ability to make final legal determinations about third-party ownership outside its control.

22. Relationship with NetEase and ANANTA’s Official Representatives

CouldInject is an independently operated, invitation-only gaming technology community.

Unless an explicit and verifiable written authorization exists in the future:

CouldInject has no authorization, agency, subordinate or joint-operation relationship with NetEase, NetEase Games, Naked Rain or ANANTA’s official representatives.

Within this compatible-server project, CouldInject develops and maintains its independently implemented compatible server and related technical support, not services provided by NetEase or ANANTA’s official representatives.

This README does not constitute:

  • NetEase’s authorization of CouldInject;
  • Official ANANTA authorization of CouldInject;
  • NetEase’s approval of the Compatible Server;
  • A sublicense of ANANTA content from CouldInject;
  • An interpretation of rules made by CouldInject on ANANTA’s official behalf.

ANANTA-related videos, images, articles, animations, tools, projects and other fan creations published by CouldInject are unofficial third-party content.

Merely using ANANTA characters, its fictional world or other elements of original works does not make that content:

  • An official ANANTA work;
  • An official NetEase work;
  • Official story;
  • Official setting;
  • Official promotion;
  • Official server content;
  • Official leaked content;
  • Officially authorized fan creation;
  • Official approval;
  • Official endorsement.

References here to published videos, images, articles and other content should not be read as stating that the current Server has been publicly released. Whether individual tools and projects are public should be checked separately against their actual status.

23. Content-Publication Requirements before September 24, 2026

Before September 24, 2026, for display content that has separately obtained the relevant usage and publication permissions and includes ANANTA footage produced or recorded using CouldInject’s compatible server, please conceal or blur any:

  • CouldInject name;
  • CouldInject logo;
  • CouldInject-specific branding;

Appearing in the footage.

This requirement primarily avoids content from a server still under continuing development and infrastructure adjustment being mistaken for:

  • An official ANANTA version;
  • An official NetEase server;
  • A formal commercial release;
  • CouldInject’s official external promotional content;
  • Project content directly connected to the earlier package of unknown origin.

Also avoid titles, covers, video descriptions or other presentation that would lead third parties to believe:

  • CouldInject is an official NetEase project;
  • CouldInject is an official ANANTA server;
  • CouldInject is authorized by NetEase to operate ANANTA;
  • A third-party published server is officially operated by CouldInject;
  • CouldInject provided or leaked the relevant unknown-origin files.

Branding and publication rules after September 24, 2026 are subject to CouldInject’s latest explanation at that time.

This provision concerns only display of CouldInject’s own branding. It does not authorize anyone to obtain the Server, disclose non-public builds, publish restricted test content or distribute third-party assets.

The arrival of September 24, 2026 does not automatically lift the Server’s non-public status, confidentiality obligations or other publication restrictions, and should not be understood as allowing unrestricted forwarding of the Server from that date.

24. Content Publication and Third-Party Rights

Concealing the CouldInject name or logo only satisfies CouldInject’s requirements for displaying its own branding.

Doing so does not mean that the publisher has obtained:

  • Authorization for ANANTA content;
  • A NetEase trademark license;
  • A NetEase copyright license;
  • Commercial-use rights in game assets;
  • Any other third-party intellectual-property permission.

Publishers remain responsible for checking that the way they publish, display, livestream or distribute content complies with:

  • Valid requirements of the relevant rights holders;
  • Contractual obligations they have accepted;
  • The relevant platform’s rules;
  • Applicable law and other relevant rules.

25. User Creations, Recordings and Fan Works

The CouldInject ANANTA Compatible Server is a technical compatibility tool and a local operating environment.

A user’s work does not automatically become CouldInject’s work merely because the user uses the Compatible Server to:

  • Run a client;
  • Test features;
  • Record gameplay footage;
  • Take screenshots;
  • Make videos;
  • Make animations;
  • Write stories;
  • Make images;
  • Livestream;
  • Make tutorials;
  • Make mods;
  • Conduct technical research;
  • Make other ANANTA-related fan creations.

Unless the user and CouldInject expressly agree otherwise, CouldInject will not claim copyright, ownership or other exclusive rights in a user’s work merely because it:

  • Uses the Compatible Server;
  • Runs in the Compatible Server environment;
  • Uses game features implemented by the server;
  • Records the server’s runtime results;
  • Demonstrates its compatibility;
  • Is made with technical tools supplied by CouldInject.

Rights that users or other creators may lawfully hold in their original contributions remain matters for the actual creators or other relevant rights holders under applicable law and the actual rights relationships.

This section explains the rights boundaries between tool users and their works. It does not grant Server-use or content-publication permissions to recipients who have not already obtained them.

26. Using the Server Does Not Confer ANANTA Rights

Because a user makes ANANTA fan works using the Compatible Server, CouldInject will not claim that:

  • ANANTA characters in the user’s work belong to CouldInject;
  • ANANTA’s fictional world in the user’s work belongs to CouldInject;
  • ANANTA artwork, music, models, story or other original content in the user’s work belongs to CouldInject;
  • Providing the compatible server gives CouldInject intellectual-property rights held by NetEase or other relevant rights holders;
  • CouldInject is authorized to grant ANANTA-related permissions for the work on NetEase’s behalf;
  • Making fan creations through the Compatible Server is equivalent to authorization from NetEase or ANANTA’s official representatives.

Existing intellectual property in ANANTA and its original works remains with NetEase and/or the other relevant rights holders.

CouldInject’s provision of the Compatible Server does not change that ownership.

27. The Compatible Server Does Not Authorize Third-Party Content

The Compatible Server provides technical compatibility capabilities.

Its ability to:

  • Run a feature;
  • Display an image;
  • Trigger client behavior;
  • Record content;
  • Help users record content;

Does not mean CouldInject has authorization for the relevant third-party content, or authority to grant users:

  • Copyright licenses;
  • Trademark licenses;
  • Commercial-use rights;
  • Rights to communicate content publicly;
  • Exemptions from confidentiality obligations;
  • Other intellectual-property or contractual rights.

The ability to run something does not mean it may be made public.

The ability to display something does not mean it has been made public.

The ability to record something does not mean publication permission has been obtained.

28. Respect ANANTA and Relevant Rights Requirements before Publishing

CouldInject’s decision not to assert its own rights over normal fan creations does not relieve publishers of respect for and compliance with relevant requirements of ANANTA, NetEase and other rights holders.

Before publicly publishing ANANTA-related content made, recorded or generated through the Compatible Server, publishers should reasonably ascertain and respect, according to the circumstances:

  • Officially published ANANTA requirements on fan creation, publication or asset use that apply to the content;
  • Lawful requirements asserted by NetEase, NetEase Games, Naked Rain and other relevant rights holders that apply to the content;
  • Rights requirements for third-party music, artwork, models, voices, fonts, videos and other assets used;
  • The publishing platform’s community rules, copyright rules and other applicable policies;
  • Potentially applicable laws and regulatory requirements in the relevant jurisdiction;
  • Other lawful requirements concerning production, public display, uploading, livestreaming or distribution of the particular work.

If ANANTA or a relevant rights holder has expressly published restrictions on particular content, assets, characters, music, test content, unreleased content, commercial uses or other usage methods, publishers should check whether those conditions apply to their work.

CouldInject’s references, explanations and reminders concerning ANANTA-related rules are intended only to help community members identify potential third-party rights and publication requirements.

They should not be understood as meaning that:

  • CouldInject interprets ANANTA policy on its official behalf;
  • CouldInject grants authorization on NetEase’s behalf;
  • CouldInject can change or waive official ANANTA requirements;
  • CouldInject can guarantee that a particular fan work complies with every applicable rule;
  • CouldInject can make the legal assessment of a specific work for its publisher.

29. Unauthorized Content, NDAs and Confidentiality Obligations

A user’s ability to run, view, record or process content through the Compatible Server does not mean CouldInject has confirmed that it may be published publicly.

If users themselves publish, upload, livestream, distribute, republish, leak or otherwise disclose:

  • Content not authorized for public release by its rights holder;
  • Content still subject to an NDA (Non-Disclosure Agreement);
  • Content subject to a testing agreement;
  • Content subject to confidentiality obligations;
  • Content restricted by an access agreement or other contractual obligation;
  • Test content not yet officially disclosed by the rights holder;
  • Internal versions;
  • Internal assets;
  • Non-public materials;
  • Content obtained through unauthorized channels;
  • Leaked files;
  • Leaked assets;
  • Trade secrets;
  • Content infringing third-party copyrights, trademarks, privacy, personality rights or other lawful interests;
  • Other content that the user may not publicly distribute under law, contract or applicable valid rules;

The publication is, in principle, conduct undertaken by the relevant user, creator or publisher themselves.

CouldInject will not proactively treat that publication as its own merely because the user used the Compatible Server.

30. NDAs, Testing Agreements and Users’ Own Contractual Obligations

If a user violates an existing NDA, confidentiality agreement, testing agreement, access agreement or other valid obligation with:

  • ANANTA;
  • NetEase;
  • NetEase Games;
  • Naked Rain;
  • A test operator;
  • A content provider;
  • An employer;
  • A partner;
  • Another third party;

The user should ascertain and address the resulting responsibility for their own conduct.

Unless CouldInject is itself a party to the agreement or otherwise has responsibility under law:

CouldInject does not assume on users’ behalf NDAs, confidentiality obligations or other contractual duties accepted by those users personally or by the entities to which they belong.

The Compatible Server’s technical ability to display, run or record relevant content does not mean those obligations have expired.

For example:

Content running normally in the Compatible Server

Does not mean that it has been officially made public.

Content being displayed by the client

Does not mean the user has permission to distribute it publicly.

Content being recordable

Does not mean it may be published on video platforms, social media or other public channels.

Content having appeared elsewhere on the internet

Does not automatically mean its public disclosure was lawfully authorized or that it is no longer subject to an NDA, confidentiality, copyright or other restrictions.

31. CouldInject Does Not Assert Infringement against Creators Solely for Normal Server Use

CouldInject will not claim that creators infringe its rights solely because they use the Compatible Server to make, record or publish normal fan creations.

However, where the conduct separately involves:

  • Copying CouldInject’s original code without permission;
  • Distributing CouldInject software without permission;
  • Copying CouldInject’s original assets without permission;
  • Removing or falsifying CouldInject creator credits;
  • Impersonating official CouldInject works;
  • Misusing CouldInject branding;
  • Presenting a third-party modified version as an original CouldInject build;
  • Violating the relevant software license;
  • Violating a separate agreement between the parties;
  • Other rights issues independent of “normal use of the Compatible Server to make content”;

Those issues should still be assessed individually according to the actual circumstances.

CouldInject’s decision not to assert its own rights against normal fan creation using the Compatible Server does not mean it can permit publication on behalf of ANANTA, NetEase or other third-party rights holders.

32. Users’ Works Do Not Automatically Represent CouldInject

Works made or published by users through the Compatible Server should not be understood, merely because they use CouldInject’s server, as:

  • Official CouldInject works;
  • Official CouldInject promotion;
  • Official CouldInject story;
  • Official CouldInject videos;
  • CouldInject’s approval of the content;
  • CouldInject’s confirmation of factual statements in the work;
  • Cooperation between CouldInject and the creator;
  • Legal or intellectual-property endorsement of the creator by CouldInject;
  • Works authorized by NetEase or ANANTA’s official representatives.

Users wishing expressly to publish a work as:

  • A CouldInject joint creation;
  • An official CouldInject community work;
  • A CouldInject cooperative project;

Should separately confirm this with CouldInject in advance.

33. Independent User Publication and CouldInject’s Liability Boundaries

Content independently made, selected, edited, uploaded, livestreamed, published or distributed by a user is decided by that user.

Providing:

  • The Compatible Server;
  • Technical support;
  • Bug fixes;
  • A compatible environment;
  • Technical documentation;

Does not, by itself, mean that CouldInject:

  • Participates in deciding all of the user’s content;
  • Guarantees rights in third-party assets in the work;
  • Automatically becomes a joint author;
  • Automatically becomes its publisher;
  • Automatically becomes the authorizing party for use of third-party rights;
  • Automatically assumes liability for infringement or contractual breaches independently committed by the user.

Where a dispute principally arises from a user:

  • Publicly disclosing content without authorization;
  • Disclosing content while knowing it remains subject to an NDA or confidentiality obligation;
  • Using assets they have no right to distribute;
  • Violating a testing agreement they accepted;
  • Violating a contract they signed with a third party;
  • Obtaining content from an unauthorized source and continuing to distribute it;

The fact that the content ran, was displayed or was recorded through the Compatible Server is not, by itself, a basis to claim that CouldInject authorized, required, directed or performed the publication.

CouldInject does not accept automatic attribution to itself of a user’s independently committed infringement, contractual breach or unauthorized distribution solely because “the content ran or was recorded through the CouldInject Compatible Server.”

However, this section does not exclude responsibility expressly imposed by applicable law on CouldInject for conduct it actually performs, participates in, controls or is legally responsible for.

The liability explanations in this README do not exclude liabilities that cannot lawfully be excluded or limited by agreement.

34. If Clearly Unauthorized Content Is Discovered

CouldInject does not encourage using the Compatible Server to make or distribute content that is clearly not authorized for public disclosure.

If reasonable, verifiable information enables CouldInject to confirm that content may involve:

  • A valid NDA;
  • Express confidentiality requirements;
  • Testing restrictions not yet lifted;
  • Leaked materials;
  • Stolen project files;
  • Trade secrets;
  • User privacy;
  • Other materials clearly unsuitable for public distribution;

CouldInject may, according to the circumstances and within its control:

  • Alert the publisher;
  • Request further source verification;
  • Pause distribution within the community;
  • Remove community links;
  • Restrict display on official CouldInject channels;
  • Decline promotion or assistance associated with that specific distribution;
  • Communicate with the relevant rights holders or parties;
  • Take other reasonable risk-control measures.

These measures do not automatically mean CouldInject has made a final legal determination of the dispute.

35. Independent User Creation, Voluntary Contributions and Submitted Materials

Independently making a work and voluntarily submitting it to CouldInject are different matters.

Using the Compatible Server to make a work does not transfer or grant rights in that work to CouldInject.

If a creator later voluntarily:

  • Contributes a work;
  • Submits assets;
  • Applies for community display;
  • Participates in a joint creation;
  • Asks CouldInject to publish it;
  • Asks CouldInject to edit, translate or modify it;
  • Participates in another community project;

The relevant content’s:

  • Scope of use;
  • Attribution;
  • Modification;
  • Publication;
  • Republication;
  • Licensing;

Will be governed by the applicable submission or project rules, or what the parties separately confirm.

Without a separate agreement, a creator should not be presumed to have transferred copyright to CouldInject solely because the work was made through the Compatible Server.

Community members and collaborating creators should, as far as possible, confirm that they are entitled to submit works, assets or other content to CouldInject.

Please do not proactively submit:

  • Third-party private materials that you clearly have no right to distribute;
  • Stolen creator project files;
  • Account credentials;
  • Private keys;
  • Users’ private information;
  • Sensitive materials obtained without authorization;
  • Malware;
  • Other content clearly unsuitable for distribution.

Where content includes third-party works, identify their sources and rights status as far as possible.

36. Boundaries on Server Modification, Copying and Redistribution

This section explains identification of third-party versions and authorization boundaries. It does not grant general permission to modify, copy or republish the Server.

Third parties may act only within the scope of permissions actually obtained. If modification and redistribution are permitted, the resulting version should clearly be identified as a third-party modification.

Retaining CouldInject’s name, logo, README, interface or other branding must not mislead users into believing that a third-party modified version is still:

  • Proactively released to the public by CouldInject;
  • Officially maintained by CouldInject;
  • Officially reviewed by CouldInject;
  • Covered by an official CouldInject security guarantee;
  • An original CouldInject build.

The following resulting from third-party modifications:

  • Network connections;
  • Data collection;
  • Feature malfunctions;
  • Security issues;
  • File corruption;
  • Additional programs;
  • Other runtime behavior;

Do not represent the behavior of CouldInject’s original builds.

Copying, modifying, redistributing and otherwise using the software should also comply with the license actually accompanying it or the relevant authorization conditions.

This README does not replace a software license.

Unauthorized copying, modification, repackaging or distribution by a third party does not become authorized merely by including this README, retaining attribution, declaring non-commercial use or labeling it a third-party version.


Part Four: CouldInject’s Own Fan Creations and AI Production Principles

37. CouldInject’s Own Original Contributions

Respecting rights in ANANTA’s original works does not mean CouldInject relinquishes rights it may lawfully hold in its own original contributions.

Without affecting the existing rights of NetEase or other third parties, CouldInject and/or the relevant creators reserve legally assertable rights in independently completed content meeting the applicable requirements for protection, including but not limited to:

  • Original scripts;
  • Original dialogue;
  • Original story arrangements;
  • Original fan-work settings;
  • Original IF / AU content;
  • Storyboarding;
  • Directorial design;
  • Shot design;
  • Performance design;
  • Action design;
  • Editing;
  • Creative selection and arrangement of materials;
  • Audiovisual structure;
  • Original animation;
  • Original 3D assets;
  • Original scenes;
  • Original graphics;
  • Original UI;
  • Original visual presentation;
  • Original effects;
  • Original music;
  • Original sound effects;
  • Original voice performances;
  • Original post-production;
  • Original code;
  • Original tools;
  • Original workflows;
  • Original technical documentation;
  • CouldInject’s own name, marks, brand designs and other assets.

These rights extend only to new original contributions actually made by CouldInject or the relevant creators and in which they are entitled to assert rights.

They must not be interpreted as extending to ANANTA’s original works themselves.

This reservation concerns contributions actually made by CouldInject or the relevant creators in which they may assert rights. It does not change the earlier explanation of ownership of users’ independent works or automatically transfer other creators’ rights because they use this community’s Server.

38. We Do Not Claim a Monopoly over ANANTA Fan Creation

Making ANANTA fan works does not lead CouldInject to claim a monopoly over the entire field of ANANTA fan creation.

We do not claim exclusive ownership of:

  • A character pairing or ship;
  • A character relationship;
  • A common plot;
  • An ordinary romantic scenario;
  • A slice-of-life situation;
  • A real-world city element;
  • A common setting;
  • A general idea;
  • A subject matter;
  • An artistic style;
  • Normal fan works independently made by other creators.

Different creators may independently arrive at identical or similar ideas.

CouldInject protects its own specific original expression and production results that may lawfully be protected. It does not seek exclusive control over ANANTA’s original works or an entire creative direction merely by being a fan creator.

39. Fan Creations and Legal Exceptions

Labels such as “fan creation,” “non-commercial,” “fan work” and “Fan-made” do not automatically make content lawful in every jurisdiction.

Different countries and regions may recognize:

  • Fair use;
  • Fair dealing;
  • Quotation;
  • Review;
  • Criticism;
  • Parody;
  • Caricature;
  • Pastiche;
  • Education;
  • Research;
  • Other copyright limitations and exceptions.

Their conditions are not identical.

CouldInject therefore does not assert in advance through this README that:

“All CouldInject fan creations automatically constitute fair use.”

Nor does it assert in advance that:

“All CouldInject fan creations automatically constitute parody, pastiche or another statutory exception.”

Whether a particular work meets a jurisdiction’s legal exception should be assessed individually with regard to:

  • The specific work;
  • The actual manner of use;
  • The purpose of use;
  • The content used and its proportion;
  • The effect on normal exploitation of and the market for the original work;
  • Local law;
  • Local judicial interpretations or case law;
  • Other relevant facts.

40. Generative Artificial Intelligence

Some CouldInject fan creations may use:

  • Generative image models;
  • Generative video models;
  • Generative audio models;
  • Large language models;
  • 3D models;
  • Motion capture;
  • Procedural generation;
  • Frame interpolation;
  • Super-resolution;
  • Video compositing;
  • Image editing;
  • Audio editing;
  • Other AI or digital-production tools.

AI is one of the technical tools that may be used in CouldInject’s creative process.

Using AI does not change ownership of ANANTA’s original works.

41. AI Outputs and CouldInject’s Rights Claims

CouldInject does not automatically claim exclusive copyright over all machine-generated content merely because it:

  • Enters prompts;
  • Clicks generate;
  • Calls a model;
  • Uses an AI service.

For works containing generative-AI content, CouldInject generally asserts rights only to the extent permitted by applicable law in actual human contributions that meet the relevant conditions for protection.

These contributions may include:

  • Original scripts;
  • Original dialogue;
  • Directorial design;
  • Storyboards;
  • Character staging;
  • Performance arrangements;
  • 3D blocking;
  • Action design;
  • Human-made assets;
  • Manual modifications;
  • Creative choices among multiple outputs;
  • Creative arrangement;
  • Editing;
  • Compositing;
  • Post-production;
  • Sound design;
  • Other human-original contributions.

In developing this policy, CouldInject referred to the U.S. Copyright Office’s reports concerning generative AI and copyrightability.

42. Transparency about AI Content

CouldInject generally supports appropriate disclosure of significant AI involvement in a work.

Where suitable, we may explain the involvement of generative AI or other AI tools through:

  • Video descriptions;
  • Page explanations;
  • End credits;
  • Metadata;
  • Project READMEs;
  • Other methods that do not substantially interfere with enjoyment of the work.

Where the EU Artificial Intelligence Act or similar transparency rules apply, CouldInject will adjust its disclosures according to the work’s nature, usage and applicable requirements.

For clearly artistic, creative, satirical, fictional or similar works, we prefer disclosures that explain AI involvement without unduly interfering with the normal experience of the work.

43. Real People, Voices and Personality-Related Content

Making fan creations with ANANTA characters does not automatically permit copying or imitating a particular real person without permission.

For real-world:

  • Actors;
  • Voice actors;
  • Developers;
  • Creators;
  • Public figures;
  • Private individuals;

Their likenesses, voices, identifying features and other potentially protected personality interests should be treated separately from fictional characters themselves.

CouldInject generally discourages creating digital replicas of clearly identifiable real people’s voices or appearances that may mislead the public, without appropriate permission or another lawful basis.

44. Public Information, Sources and Risk Assessment

ANANTA-related public information, promotional materials, version information and source materials should be assessed according to their actual status when they were created and made public.

The public internet may contain all of the following:

  • Official websites;
  • Official promotional videos;
  • Official gameplay demonstrations;
  • Official livestreams;
  • Official social-media posts;
  • Official interviews;
  • Trade-show demos;
  • Media reporting;
  • Players’ publicly posted videos;
  • Community compilations;
  • Wikis;
  • Community speculation;
  • Real-world references;
  • Materials of unknown origin;
  • Unverified information.

CouldInject will not simply equate “searchable on the internet” with:

“Officially confirmed”

Or:

“Authorized for public distribution.”

Information should be assessed individually according to its actual source, degree of public availability, reliability and other specific factors.

45. Fan-Work Content and Official Story

CouldInject’s ANANTA fan creations may contain substantial amounts of:

  • Original story;
  • Original slice-of-life content;
  • Character-pairing content;
  • IF timelines;
  • AUs;
  • Original relationship development;
  • Original events;
  • Original scenes;
  • Original dialogue;
  • Developments entirely different from the official game.

Accordingly:

Unless CouldInject explicitly cites publicly available, verifiable official information, a fan work’s story, relationships, dialogue, locations, events and character behavior should not be understood as confirming ANANTA’s official story, future story or future-version content.

Similarity or overlap between a fan work and future official content does not, by itself, prove a direct source relationship.

Producing, displaying or publishing a fan work does not state whether the Server is public. Whether footage or content was actually made with the Server depends on that work’s production process. It cannot be inferred solely from ANANTA elements, CouldInject branding or similar images.

46. Content Risk Control

CouldInject may assess publication risks internally according to each work’s circumstances.

For potentially higher-risk content, we may independently:

  • Modify it;
  • Regenerate it;
  • Redesign it;
  • Replace scenes;
  • Replace assets;
  • Reduce the recognizability of particular information;
  • Delay publication;
  • Restrict distribution;
  • Suspend publication;
  • Delete content;
  • Verify further;
  • Take other reasonable measures.

These are CouldInject’s independent risk-management actions.

Proactively modifying, restricting or deleting content does not itself automatically constitute an admission of infringement, illegality or other liability.

47. Production Records and Evidence of Rights

For important original projects, CouldInject may retain, as actually needed:

  • Script versions;
  • Storyboards;
  • Original project files;
  • 3D projects;
  • Original materials;
  • Editing projects;
  • Generation-process records;
  • Original asset source files;
  • Final masters;
  • File hashes;
  • First-publication dates;
  • Contributor records.

These materials may be used for:

  • Project management;
  • Creator attribution;
  • Version tracing;
  • Content disputes;
  • Evidence of originality;
  • Security investigations;
  • Other reasonable purposes.

CouldInject does not guarantee that all internal production records will be made public.

48. Suggested Short Rights Statement

Where a short statement is suitable, wording along these lines may be used:

“This work is an unofficial ANANTA fan creation made by CouldInject.

ANANTA and the relevant original works, characters, trademarks and other existing intellectual property belong to NetEase and/or the relevant rights holders.

CouldInject does not claim rights in those original works.

Only to the extent permitted by applicable law, CouldInject and the relevant creators reserve rights in their own legally protectable original scripts, storyboards, direction, editing, original assets, creative selection and arrangement, and other new original contributions to this work.

This work may use generative AI and other digital-production technologies.

Fan-made / Unofficial.”

This example applies to works actually made or published by CouldInject. Other creators should not use it directly in a manner that misleadingly suggests an official CouldInject work or cooperative relationship.

The sentence about generative AI should be adjusted to the actual production circumstances. This example does not prove that a particular work uses AI and does not replace labeling or disclosure requirements applicable to that work.

If a work actually involves this Server and an additional clarification of its availability is needed, the following may be added:

“Publication of this work does not mean the CouldInject ANANTA Compatible Server has been publicly released, and does not grant permission to obtain, use or redistribute that Server.”


Part Five: Republication, Open Source, Community Cooperation and Risk Sharing

49. Sharing Does Not Mean Relinquishing Rights

CouldInject supports knowledge sharing.

However, willingness to share does not mean:

  • All CouldInject content automatically enters the public domain;
  • Anyone may remove original authors’ credits;
  • Anyone may impersonate the original author;
  • Anyone may repackage a work and claim to have made it;
  • Anyone may place non-commercially shared content behind a paywall;
  • Anyone may directly sell CouldInject’s original work;
  • Anyone may use CouldInject branding to create a false impression of official cooperation;
  • Anyone may arbitrarily alter a work’s rights statements.

Unless a specific work has an express license stating otherwise, public accessibility of CouldInject content does not automatically permit unrestricted copying, commercial use, modification or sublicensing.

50. Limited Republication License for Original Documents and Principles for Republishing Fan Works

Limited Republication License for Documents

CouldInject supports reasonable, good-faith, non-commercial dissemination of knowledge.

Subject to all conditions in this section, and provided the content does not separately specify another license or prohibit republication, CouldInject generally grants a limited, non-exclusive, non-sublicensable license for non-commercial republication only of README files, technical documents and other original text that it is itself entitled to license.

This license does not include:

  • The Compatible Server software itself;
  • ANANTA’s original works;
  • Works belonging to NetEase or other rights holders;
  • Third-party assets;
  • Content that CouldInject has no right to license further.

Republishers should at least:

  • Retain reasonable attribution;
  • Identify the original source;
  • Not impersonate the original author;
  • Not remove necessary third-party rights statements;
  • Not imply official NetEase or ANANTA authorization;
  • Not use CouldInject branding to fabricate cooperation;
  • Not use the content directly as the core of a paywall or principal paid service;
  • Not directly sell CouldInject’s original documentary content;
  • Not seriously distort its meaning.

For:

  • Complete mirrors;
  • Large-scale republication;
  • Long-term mirrors;
  • Translation;
  • Substantial modifications;
  • Commercial use;
  • Corporate promotion;
  • Sublicensing;

We recommend contacting CouldInject in advance.

Where content has a separate license, that license governs.

This text-republication license does not include the Server software itself, non-public builds, source code, configurations, credentials, runtime data or other materials outside its scope. A document’s permission for republication does not mean the software it describes has been publicly released.

Principles for Non-Commercial Republication of Other Fan Content

CouldInject is generally open to reasonable republication and knowledge sharing by non-fee-charging, non-commercial communities.

Unless other special authorization has been obtained, we ask republishers at least to:

  • Retain reasonable attribution;
  • Identify the original source;
  • Not claim to be the original creator;
  • Not distort CouldInject’s position;
  • Not remove necessary third-party rights information;
  • Not imply official NetEase or ANANTA authorization;
  • Not place the content behind a paywall;
  • Not sell it directly;
  • Not use CouldInject branding in false advertising;
  • Respect other third-party rights in the work.

For:

  • Complete reposts;
  • Large-scale republication;
  • Long-term mirrors;
  • Translation;
  • Further modification;
  • Joint creation;
  • Commercial use;

We recommend contacting CouldInject in advance.

Being generally open to republication of fan works should not be interpreted as a blanket license for all works, all assets or all uses. For a specific work, the scope of permission should also be checked against its accompanying explanation, actual rights relationships and authorization confirmed between the parties.

This section’s express limited license for text, its attitude toward republication of other fan works, and the authorization boundaries for Server software should be understood separately.

51. Open-Source Projects and ANANTA Assets Must Be Kept Separate

CouldInject may release some:

  • Code;
  • Tools;
  • Scripts;
  • Technical components;
  • Data structures;
  • Workflows;
  • Documentation;

Under MIT, Apache, GPL or other open-source licenses.

An open-source license covers only content that CouldInject actually has authority to license.

For example:

A CouldInject tool using the Apache-2.0 License

Does not make the following displayed alongside it Apache-2.0-licensed content:

  • ANANTA character images;
  • Game screenshots;
  • Official models;
  • Official music;
  • Official trademarks;
  • Other third-party assets.

Third-party assets retain their original rights status.

Open-source licenses for some tools, components or documents do not mean that the currently unreleased ANANTA Compatible Server is open source, public or subject to the same license. The actual files expressly included in a license should be checked individually.

52. Community Cooperation We Welcome

CouldInject seeks active, long-term exchange and cooperation with parties sharing similar values, including:

  • Independent gaming communities;
  • Player communities;
  • Technical communities;
  • Open-source communities;
  • Public-interest communities;
  • Nonprofit communities;
  • Non-commercial creator organizations;
  • Educational projects;
  • Academic or research projects.

Cooperation may include:

  • Joint fan creation;
  • Joint video production;
  • Technical cooperation;
  • Open-source projects;
  • Exchange of AI workflows;
  • Exchange of development tools;
  • Technical documentation;
  • Translation and localization;
  • Creator support;
  • Public-interest technical support;
  • Community-security experience;
  • Content-risk management;
  • Intellectual-property risk experience;
  • Community-governance experience;
  • User-support experience;
  • Other mutually agreed non-commercial cooperation.

Welcoming cooperation or technical exchange does not automatically give partners access to the Server, non-public builds or other internal materials. Access requires separate confirmation of its scope and conditions.

53. Fee-Charging Communities

CouldInject currently does not, as a general principle, open the community-cooperation program above to fee-charging communities.

“Fee-charging communities” here mainly means communities that make one or more of the following a necessary condition for users to obtain principal community services, core content or normal participation rights:

  • Paid admission;
  • Mandatory membership fees;
  • Payment to enter principal discussion areas;
  • Payment to access core shared content;
  • Payment to obtain principal resources;
  • Paid access as the main operating model.

The mere existence of:

  • Voluntary donations;
  • Public-interest sponsorship;
  • Support programs that do not affect ordinary users’ normal participation;

Does not automatically make a community a “fee-charging community” within this document’s meaning.

Special public-interest, educational, research or common-good projects may be discussed separately according to their circumstances.

54. Joint Creation

CouldInject welcomes joint creation with other non-fee-charging communities and creators.

For larger collaborations, we recommend confirming before production begins:

  • Each party’s contributions;
  • Creator credits;
  • Ownership of original assets;
  • Sources of third-party assets;
  • The publishing party;
  • The first-release channel;
  • Whether republication is permitted;
  • Whether modification is permitted;
  • Whether open-source release is permitted;
  • Whether commercial use is permitted;
  • Treatment of assets after cooperation ends;
  • Contacts for risks that arise;
  • Other necessary matters.

Cooperation itself does not automatically give a partner usage rights in all CouldInject assets, branding or future works.

Likewise, CouldInject does not automatically acquire all of a partner’s assets or rights through cooperation.

55. Cooperation Does Not Mean Mutual Endorsement

Cooperation with a community, open-source project, public-interest organization or creator does not automatically mean:

  • CouldInject endorses all of that party’s activities;
  • That party endorses all CouldInject activities;
  • The parties have a subordinate relationship;
  • The parties have an agency relationship;
  • The parties jointly assume all liabilities;
  • The parties acquire ownership of each other’s brands;
  • The parties acquire NetEase- or ANANTA-related authorization.

The actual confirmed arrangements determine the specific cooperation scope.

56. Sharing Risk Experience between Communities

CouldInject believes that the most valuable things for communities to share are not only:

Code;

Works;

Tools;

Resources.

They also include:

Risks.

We are willing to exchange with independent, open-source, public-interest and non-fee-charging communities our experience of long-term community operation, including:

  • Issues already encountered;
  • Current issues;
  • Possible future issues;
  • Mistakes already made;
  • Solutions verified to work;
  • Unresolved risks worth considering early.

Topics may include:

  • Intellectual property;
  • Fan creation;
  • AI-generated content;
  • Model licenses;
  • Software licenses;
  • User privacy;
  • Data protection;
  • Software security;
  • Supply-chain security;
  • Malware;
  • Third-party repackaging;
  • Brand impersonation;
  • False information;
  • Authenticity of content sources;
  • Content moderation;
  • Reports and appeals;
  • User-generated content;
  • Community governance;
  • Infrastructure;
  • Creators’ rights and interests;
  • Sustainable community operation;
  • Other issues communities may face together.

If another community has resolved an issue CouldInject is facing, we are willing to learn.

If CouldInject has handled an issue another community faces, we are also willing to share experience within reasonable limits.

57. Boundaries of Risk Communication

Sharing risk experience does not mean unconditionally disclosing all information.

CouldInject will not indiscriminately disclose material merely in the name of “community exchange” or “open source” where it may involve:

  • Personal privacy;
  • User identities;
  • Passwords;
  • Tokens;
  • Private keys;
  • Details of security-vulnerability exploitation;
  • Non-public credentials;
  • Trade secrets;
  • Contractually protected information;
  • Information that may create real-world safety risks;
  • Other content unsuitable for public distribution.

We support responsible disclosure.

Where appropriate, we will first give affected projects, developers, communities or service providers a reasonable opportunity to verify and address the issue.

Non-public Server builds, recipient scope, access credentials and other non-public materials likewise do not automatically become publicly distributable through “risk sharing” or “community cooperation.”

58. Our Approach to Community Disputes

Misunderstandings, conflicting views and risks between communities can be normal occurrences in long-term operation.

When a problem arises, CouldInject generally seeks to:

  1. Confirm the facts;
  2. Establish direct communication;
  3. Understand the parties’ positions;
  4. Identify the actual issue;
  5. Assess the impact on users and third parties;
  6. Find an actionable solution;
  7. Make necessary changes;
  8. Explain the situation to the community where needed;
  9. Learn from the experience;
  10. Improve processes.

We do not seek a supposed competitive advantage by creating community antagonism, information asymmetry or public-opinion conflict.

Problems that can be resolved through communication should not grow because communication is absent.


Part Six: Rights Contacts, Risk Communication and Dispute Handling

59. We Believe Proactive Communication Is Very Important

CouldInject believes:

Proactive, direct, honest and verifiable communication is one of the most important foundations for long-term trust among communities, creators, developers, businesses, rights holders, open-source projects, public-interest organizations and public authorities.

We do not believe every potential issue should first be addressed through:

  • Public confrontation;
  • Community conflict;
  • Public attacks;
  • Malicious reporting;
  • Legal proceedings.

Where circumstances permit, we would prefer first to:

Confirm the facts;

Make contact;

Understand each other’s positions;

Identify the actual issue;

Find a solution.

60. Rights Claims, Unusual Circulation and Contacting Us

If you, or a party you represent under law or authorization, including:

  • A rights holder;
  • A creator;
  • A company;
  • A studio;
  • A development team;
  • A community;
  • An open-source project;
  • A public-interest organization;
  • A nonprofit organization;
  • Another lawful entity;

Believe that content made, displayed, provided or published by CouldInject may affect your lawful rights, or discover possible circulation of this Server beyond its intended scope, please contact us directly.

Email

[email protected]

Support Center

Support Center - CouldInject

To help us verify and address a matter promptly, we recommend that a rights claim include at least:

  • The particular work, page, video, file or project involved;
  • The corresponding link;
  • The specific timestamp, image, file location or content location;
  • The particular right you believe is affected;
  • Your relationship, or that of the party you represent, to the relevant rights;
  • Materials demonstrating those rights or authorization within a reasonably necessary scope;
  • The specific reason you believe there is an issue;
  • The action you would like CouldInject to take;
  • Contact details for further communication.

CouldInject welcomes good-faith, specific and reasonably verifiable rights notices.

Feedback may also concern improper asset use, incorrect attribution, misunderstandings about identity or authorization, and other actual impacts on lawful interests.

CouldInject will seek to verify carefully and address proactively good-faith, specific and reasonably verifiable reports. Provide only materials necessary for verification. Do not submit a complete non-public Server, third-party sensitive materials or irrelevant personal information in public spaces.

61. Communication with NetEase and Other Rights Holders

If NetEase, NetEase Games, Naked Rain or other relevant rights holders believe CouldInject’s ANANTA fan creations affect their lawful rights and interests, we welcome direct contact through verifiable channels.

After reasonable confirmation, we are willing to discuss, according to the circumstances:

  • Additional rights statements;
  • Content modifications;
  • Replacement of assets;
  • Distribution restrictions;
  • Publication pauses;
  • Content removal;
  • Changes to future usage;
  • Other solutions both parties consider reasonable.

CouldInject respects rights and does not make fan creations for the purpose of provoking conflict with rights holders.

62. Communication with Government and Regulatory Authorities

CouldInject does not consider communities and government, regulatory bodies or other public authorities inherently opposed.

Where a government agency, regulator or other public authority with the relevant lawful powers believes CouldInject’s content may concern:

  • Applicable law;
  • Regulatory requirements;
  • Users’ rights and interests;
  • Data protection;
  • Information security;
  • Intellectual property;
  • Content compliance;
  • Public interests;
  • Other matters within its statutory authority;

We welcome contact through formal, verifiable means.

CouldInject will handle the contact and requirements with regard to:

  • The requester’s identity;
  • Its relevant statutory powers;
  • Applicable law;
  • The request’s scope;
  • Lawful process;
  • Users’ and third parties’ lawful rights and interests.

Establishing communication does not mean CouldInject relinquishes legally available rights, defenses or procedural protections.

63. Handling Rights Notices

On receiving a relevant notice, CouldInject may, according to the circumstances:

  • Confirm the rights holder’s identity;
  • Verify materials;
  • Confirm content sources;
  • Check internal production records;
  • Communicate with relevant creators;
  • Temporarily restrict distribution;
  • Add explanations;
  • Modify content;
  • Replace assets;
  • Correct attribution;
  • Pause publication;
  • Delete or remove content;
  • Restore content;
  • Raise objections;
  • Appeal or submit a counter-notice under applicable platform rules;
  • Take other reasonable measures.

Receiving a rights claim, communicating or voluntarily taking interim measures does not itself mean CouldInject admits:

  • Infringement;
  • Illegality;
  • Fault;
  • Other legal liability.

Likewise, objecting to a notice does not mean CouldInject denies a genuine rights holder’s lawful rights.

64. Rights Claims to Video or Hosting Platforms

CouldInject respects rights holders’ right to protect their lawful interests under law.

We also understand that:

  • Video platforms;
  • Social platforms;
  • File-hosting services;
  • Code-hosting services;
  • Other online platforms;

May offer copyright complaints, trademark complaints, content reports, takedown notices or other rights-protection mechanisms.

At the same time, erroneous, incomplete or insufficiently verified platform rights claims may directly cause:

  • Removal of videos or works;
  • Restrictions on content distribution;
  • Channel or account sanctions;
  • Frozen revenue;
  • Inaccessible project pages;
  • Disruption of normal community operation;
  • Harm to CouldInject’s or the relevant creators’ own lawful rights.

Accordingly, in the absence of:

  • An obvious urgent risk;
  • Ongoing substantial harm;
  • A mandatory legal requirement;
  • A court order;
  • A regulatory requirement;
  • A safety emergency;
  • Another situation genuinely requiring immediate action;

CouldInject strongly hopes and requests that claimants first establish direct communication through [email protected] or the Support Center, and reasonably confirm basic facts and rights status before deciding whether platform takedowns, copyright strikes, account sanctions or other significantly consequential measures are necessary.

65. We Prefer to Resolve the Actual Issue First

If an issue can reasonably be resolved through:

  • Additional attribution;
  • Additional rights statements;
  • Changes to images;
  • Changes to audio;
  • Replacement of assets;
  • Changes to descriptions;
  • Changes to titles;
  • Removal of specific segments;
  • Restrictions on distribution of specific content;
  • Other narrower adjustments;

We would prefer first to discuss such solutions that reduce unnecessary losses for both sides.

This request is CouldInject’s proposal for good-faith communication and dispute resolution.

It does not require anyone to relinquish their legally available:

  • Lawful rights;
  • Statutory notice rights;
  • Right to litigate;
  • Rights-protection mechanisms lawfully provided by platforms.

For real-world safety threats, privacy disclosures, malware, fraud, substantial ongoing harm, court orders, regulatory requirements or other emergencies that cannot reasonably await communication, this preference for communication does not restrict relevant parties from promptly taking necessary lawful measures.

66. Where a Platform Complaint Has Already Been Made

If a platform rights claim has already been made concerning CouldInject content, we still welcome the claimant providing CouldInject with:

  • The relevant notice;
  • The basis of the rights;
  • The content involved;
  • Necessary supporting evidence;

So the parties can confirm the facts and seek a solution promptly.

For platform claims that are clearly erroneous, duplicative, impersonated, lacking a relevant rights basis or otherwise reasonably disputed, CouldInject and the relevant creators reserve their rights under applicable law and platform rules to:

  • Appeal;
  • Submit counter-notices;
  • Provide additional proof of rights;
  • Request restoration;
  • Request correction of erroneous claims;
  • Protect their own lawful rights.

CouldInject does not want any party to use copyright, trademark, reporting or platform-complaint mechanisms to generate unnecessary community conflict.

Where facts can be confirmed and issues resolved through direct communication, we prefer communication first.

67. Correcting and Withdrawing Content

If CouldInject subsequently confirms that content it made, displayed, provided or published:

  • Contains factual errors;
  • Contains incorrect attribution;
  • Has source issues;
  • Presents intellectual-property risks;
  • Presents privacy issues;
  • Presents security risks;
  • Is likely to cause substantial misunderstanding;

CouldInject may, according to the circumstances:

  • Add explanations;
  • Modify it;
  • Correct it;
  • Re-upload it;
  • Restrict distribution;
  • Temporarily hide it;
  • Delete it;
  • Withdraw it;
  • Publish an explanation.

CouldInject does not consider acknowledging and correcting verifiable problems to weaken community credibility.

Acknowledging and correcting verifiable problems is part of continuous community improvement. These actions should not be understood as meaning that the current Server has been publicly released.


Part Seven: Original Legal References, Policy Updates and Liability Boundaries

68. International Copyright Principles Cited in the Original Fan-Creation Statement

CouldInject referred to international copyright frameworks, including the Berne Convention for the Protection of Literary and Artistic Works, when developing this policy.

The Berne Convention’s rules on adaptations, musical arrangements and other alterations reflect an important principle:

An original adaptation or other creation based on an existing work may receive protection for the new work, without affecting copyright in the original work itself.

At the same time, original authors have rights under law to authorize adaptations, musical arrangements and other alterations.

CouldInject’s basic position is therefore:

Respecting rights in original works and protecting our new original contributions are not mutually exclusive.

69. Chinese Copyright Rules Cited in the Original Fan-Creation Statement

CouldInject referred to the Copyright Law of the People’s Republic of China when developing this policy.

The original fan-creation statement summarized Chinese copyright rules as follows: works resulting from adaptation, translation, annotation or arrangement of existing works may give rise to corresponding copyright, but exercising those rights must not infringe copyright in the original works.

CouldInject therefore does not believe that potentially holding rights in new portions of fan creations also gives it rights in ANANTA’s original works.

Conversely, protection of ANANTA’s original works does not automatically make other creators’ independently completed original contributions that qualify for legal protection public content that anyone may repost unconditionally.

70. United States Copyright Rules Cited in the Original Fan-Creation Statement

CouldInject referred to United States copyright law, Title 17, when developing this policy.

Its rules on compilations and derivative works distinguish between:

  • Preexisting works;
  • Material added by the later author.

Any protection available for a derivative work extends only to new material actually contributed by the later author, not to the preexisting work itself.

United States fair-use rules require multiple factors to be considered together in light of the particular facts.

CouldInject therefore does not treat:

“Non-commercial”

“Community use”

“Fan work”

Or:

“Educational / research purpose”

Alone as a final conclusion that any particular work automatically constitutes fair use under United States law.

71. European Union Copyright Rules Cited in the Original Fan-Creation Statement

CouldInject referred to the European Union copyright framework when developing this policy.

EU rules provide specific frameworks of limitations and exceptions for quotation, criticism, review, caricature, parody and pastiche, among other uses.

In particular online settings, such as user-uploaded content, relevant EU directives require Member States to ensure that users can rely on some of these exceptions under particular conditions.

Those provisions do not mean every fan creation automatically falls within a copyright exception.

The circumstances of individual works and Member States’ implementing rules may differ.

CouldInject therefore does not make a blanket legality determination for all ANANTA fan creations on the basis that “the EU allows parody / pastiche.”

72. Legal and Policy References

The following retains public laws, treaties and official explanatory materials listed in the original fan-creation statement. This is a consolidation of references from the original document, not a representation that all legal developments, conditions of application or compliance of the specific project in every jurisdiction have been verified as of this statement’s date.

International

[INT-01] Berne Convention for the Protection of Literary and Artistic Works Particular reference to Article 2(3) and Article 12.

[INT-02] World Intellectual Property Organization (WIPO) Guide to the Copyright and Related Rights Treaties Administered by WIPO.


China

[CN-01] Copyright Law of the People’s Republic of China Particular reference to provisions concerning adaptation rights, adapted works and rights in original works, including Articles 10 and 13.


United States

[US-01] 17 U.S.C. §103 Subject matter of copyright: Compilations and derivative works.

[US-02] 17 U.S.C. §107 Limitations on exclusive rights: Fair use.

[US-AI-01] U.S. Copyright Office Copyright and Artificial Intelligence, Part 2: Copyrightability January 2025.


European Union

[EU-01] Directive 2001/29/EC Particular reference to Article 5, including caricature, parody, pastiche and the related limitations-and-exceptions framework.

[EU-02] Directive (EU) 2019/790 Particular reference to Article 17(7) concerning safeguards for user-uploaded content, quotation, criticism, review, caricature, parody and pastiche.

[EU-03] European Commission Guidance on Article 17 of Directive (EU) 2019/790.

[EU-AI-01] Regulation (EU) 2024/1689 — Artificial Intelligence Act Particular reference to Article 50 concerning transparency for certain AI-generated or manipulated content.

73. Legal Updates

Copyright, AI, platform liability, data protection and other relevant laws and policies continue to develop.

CouldInject may update this README in response to:

  • Legislative changes;
  • Court decisions;
  • Regulatory rules;
  • Official guidance;
  • Platform policies;
  • Technological changes;
  • Practical operating experience.

Referring to a law or official document means only that CouldInject used it as one reference when developing the current policy.

It does not mean CouldInject considers one jurisdiction’s rules automatically applicable to all activities worldwide.

74. This README Is Not a Public Software-Release Announcement or Third-Party Authorization

This README should not be understood as:

  • A statement that CouldInject has publicly released the Server;

  • Permission for a recipient to run, copy, modify or redistribute the Server merely by obtaining its files;

  • Authorization by CouldInject of external downloads, mirrors, sales or third-party operations;

  • NetEase’s authorization of CouldInject;

  • Official ANANTA approval of the Compatible Server;

  • A sublicense of ANANTA content from CouldInject;

  • Permission for users to disclose any ANANTA content merely by relying on this README;

  • Permission for users to breach NDAs by relying on this README;

  • Permission to distribute leaked third-party materials by relying on this README;

  • A final determination of the legality of any particular work;

  • A guarantee of the result of applying law in any jurisdiction;

  • A prediction of the outcome of a particular dispute.

If an activity requires formal authorization, obtain it from the party that actually holds the relevant rights.

75. Liability Boundaries of This README

This README’s main purposes are:

  • To explain the project’s origins and the Server’s unreleased status;
  • To provide advance explanation if files circulate beyond their intended recipients;
  • To explain CouldInject’s relationship with ANANTA;
  • To explain basic boundaries for users of the Compatible Server;
  • To provide rules for publication, security, privacy and rights communication;
  • To explain CouldInject’s own fan-creation, original-contribution and community-cooperation principles;
  • To reduce misunderstandings about identity, authorization and rights relationships.

This README does not constitute legal advice concerning a particular user, work, contract or jurisdiction.

CouldInject does not use this README to claim exclusion of liabilities that cannot lawfully be excluded or limited.

Specific disputes should be assessed individually with regard to:

  • Actual conduct;
  • The parties actually involved;
  • Rights status;
  • Contractual relationships;
  • Applicable law;
  • Other relevant facts.

Explaining non-public status does not automatically prove that every individual recipient signed a confidentiality agreement. Nor does this document prejudge the external appearance of files as infringement, breach or leaking liability attributable to a particular party.

Actual software permissions, existing contractual obligations, third-party rights and liability should be assessed separately against the licenses, agreements, conduct and applicable rules that actually exist.


Part Eight: Principles, Final Statement and Contact Information

76. Our Principles

As an invitation-only gaming technology community, CouldInject seeks to maintain the following principles over the long term:

An unreleased Server does not automatically become publicly distributed software because it appears on external channels.

Public fan works do not mean public production tools or a public Server.

Respect original authors.

Respect the lawful rights of NetEase and other relevant rights holders.

Do not claim others’ works as our own.

Do not relinquish development results we genuinely completed independently merely because we develop for compatibility.

Tools provide technical capability, not third-party authorization on users’ behalf.

The ability to run content does not mean it may be made public.

The ability to record content does not mean publication rights have been obtained.

Using CouldInject tools does not automatically transfer users’ own NDAs, confidentiality obligations or third-party rights obligations to CouldInject.

Users’ normal fan creation does not automatically infringe CouldInject merely because they use the Compatible Server.

Users’ own original contributions do not automatically become CouldInject works merely because they use the Compatible Server.

Communicate proactively when risks are found.

Verify what can be verified as far as possible.

Do not pretend to be certain about what we do not know.

Allow mistakes to be corrected.

Prefer communication for problems it can resolve.

Do not give up what we genuinely create merely because our work is a fan creation.

Be willing to share.

Be willing to cooperate.

Respect attribution.

Protect creators.

Welcome open source.

Welcome public-interest cooperation.

Welcome knowledge exchange among non-commercial communities.

Do not want public knowledge to be artificially closed off by community paywalls.

Where experience can be shared, help other communities avoid repeating unnecessary detours.

77. Final Statement

CouldInject is an invitation-only gaming technology community founded in 2016.

CouldInject currently develops and maintains an ANANTA local compatible server independently designed and implemented by its own team.

As of this statement’s date, September 19, 2026, the Server has not been publicly released.

This README is an advance accompanying explanation for possible circulation beyond originally intended recipients, actual authorization or intended scenarios. It is not a public-release announcement, download invitation or redistribution license.

The server:

Is not NetEase’s official server software.

Is not a modified version of NetEase’s official server software.

Is not a repaired version of any leaked server.

Was not developed from the previously mentioned package of unknown origin.

When CouldInject previously encountered those unknown-origin files through community security tickets, it performed only necessary security analysis to reduce community users’ exposure to viruses, Trojans and other malicious programs.

CouldInject did not use that security-analysis process as the development source for the current server.

The current compatible server is independently developed and maintained by CouldInject based on the client’s actually observable behavior, protocol interactions and verifiable functional behavior.

CouldInject does not provide ANANTA’s official client or online services on behalf of NetEase or ANANTA’s official representatives.

ANANTA and related names, trademarks, clients, artwork, characters, music, story and other intellectual property belong to NetEase and/or other relevant rights holders.

CouldInject has no authorization, agency, subordinate or joint-operation relationship with NetEase, NetEase Games, Naked Rain or ANANTA’s official representatives unless an explicit, verifiable written authorization exists in the future.

Provided the applicable permissions have been obtained and third-party rights and actual agreements are respected, users’ use of the Compatible Server may involve local operation, technical research, functional testing, recording and fan creation. Listing these scenarios does not automatically grant any recipient the relevant permissions.

However:

The Compatible Server provides technical capability, not permission to disclose unauthorized content.

The Compatible Server does not release users from their own NDAs, testing agreements, confidentiality duties or other contractual obligations.

Unauthorized publication, infringement or contractual breaches independently committed by users do not automatically become CouldInject’s conduct merely because the Compatible Server was used.

At the same time:

CouldInject will not claim ownership of users’ works, or assert that users infringe CouldInject, solely because creators normally use the Compatible Server to make fan works.

Before users publish content they want to make public, we ask them to:

Respect original works.

Respect creators.

Respect NetEase and other relevant rights holders.

Respect the NDAs and contractual obligations they have accepted.

Respect other third parties’ lawful rights and interests.

Make the corresponding publication assessment for what they actually publish.

CouldInject and relevant creators do not automatically relinquish rights they may lawfully hold in their new original contributions merely because a work is a fan creation. This reservation does not extend to ANANTA’s original works or automatically acquire rights in other users’ or partners’ works.

CouldInject welcomes non-commercial knowledge exchange, cooperation among non-fee-charging communities, open-source and public-interest projects, and responsible risk communication on the basis of respect for original works, creators, users, other communities, rights holders, law and public interests. The scope of cooperation and specific permissions still require separate confirmation.

Seeing a related work is not the same as obtaining the Server.

Obtaining a file is not the same as obtaining permission to use or distribute it.

A file including this README does not mean CouldInject proactively released it publicly or approved its circulation channel.

Infrastructure changes do not automatically change the Server’s non-public status.

If you find the Server outside its intended scope, or believe CouldInject content may affect your lawful rights, please preferably contact us through:

Email: [email protected]

Support Center: https://couldinject.com/support.php

We are willing to verify issues.

We are willing to hear rights claims.

We are willing to correct issues that can be confirmed.

We will also protect the lawful rights held by CouldInject and the relevant creators.


CouldInject
Invitation-only gaming technology community
Since 2016

Official Website:
https://couldinject.com/

Support Center:
https://couldinject.com/support.php

User Agreement:
https://couldinject.com/terms.php

Privacy Policy:
https://couldinject.com/privacy.php

Rights / Legal / Circulation Contact:
[email protected]

Server status recorded in this draft: as of September 19, 2026, not yet publicly released.

Back to top ↑
COULDINJECT

Building a friendly, harmonious and well-kept player community together
Community since 2016

Navigation

HomeForumsWikiStoreANANTA Intelligence

Support

Help centerFAQContact usCISS

Legal

Terms of ServicePrivacy PolicyANANTA Project StatementANANTA Content PolicyAbout us

© 2016–2026 CouldInject. All rights reserved.