Be Original and Authentic
All submissions must be your original work or content you have the rights to use and distribute.
You may use AI to brainstorm, explain concepts, improve wording, debug, or refactor your work. You must understand what you submit, be able to maintain it yourself, and take responsibility for it.
We do not accept vibe coded files, except for the limited free submissions described below. “Vibe coded” means content mostly generated through AI prompts with little meaningful understanding, control, or authorship from the submitter. If you depend on AI to explain, repair, or maintain the file, it does not meet our standards.
Testing does not make an AI-generated submission acceptable. A file may still be rejected if AI replaced human authorship, even if it works, has been tested, or only contains some AI-generated sections. There are no exceptions for paid submissions.
AI-generated files may only be considered when they are:
- Free.
- Transformative, with a useful purpose beyond reproducing existing work.
- Not a parody, copy, imitation, or recreation of anything else that exists online, whether on Codefling or elsewhere.
- Useful, functional, and held to the same quality standards as other submissions.
Acceptance of a free AI-generated file does not reserve the idea for its author. We may accept and give priority to a similar submission developed by a human who understands the work and can maintain and support it.
Low-effort, copied, misleading, or misrepresented AI-generated content will be rejected and may result in account action.
AI-Generated Images
AI-generated product images must accurately represent the submission. We do not accept low-quality AI images, fake screenshots, distorted objects, unreadable text, incorrect anatomy, or scenes that misrepresent the product.
Use in-game screenshots, editor screenshots, or clear previews of the actual content wherever possible. Images must not imply that a product includes features, assets, or visual quality it does not provide.
Follow Licensing and Fork Policies
Choose a license you have the right to apply, and make its terms available to buyers. Your license must not conflict with the licenses of any code, assets, or other material included in your submission. Publicly available content is not automatically free to reuse or sell.
For forked content and third-party material:
- Follow the original license, including any requirements for attribution, license notices, or source code.
- Only include code or assets when their license or the rights holder permits your intended use and distribution.
- Make significant improvements or changes when submitting a fork.
- Provide proof of permission or licensing if Codefling requests it.
Respect Game and Platform Terms
Submissions must comply with the Terms of Service, EULA, and applicable modding, server, and monetization policies of the game or platform they are intended for. Content that violates those rules, circumvents restrictions imposed by them, or is designed to enable prohibited activity is not allowed. Authors are responsible for keeping their submissions compliant when those policies change.
Maintain Quality and Functionality
Submit finished work that has been tested and is ready to use:
- For maps and prefabs, check for overlapping geometry, flickering, missing assets, and incorrect alpha masks. Include terrain modifiers (height, splat, topology, and biome) for non-standalone prefabs where needed.
- For plugins, scripts, and tools, fix compilation errors and critical bugs before uploading. Test in a live or simulated environment, and avoid unnecessary resource use.
- Provide clear installation and configuration instructions.
- Keep submissions compatible with the current versions of the software they support. Clearly label any branches intended for older versions.
Rushed, broken, or poorly supported submissions may be rejected or removed.
Upload the Correct Files
Upload the files users need to install and run your submission. For plugins installed as a .cs file, upload that file directly. Use an archive when the submission needs multiple files, and explain where each file belongs.
Do not upload an entire development repository in place of the installable product. Leave out unrelated source files, version control folders, temporary files, build caches, and unnecessary dependencies. Never include passwords, private keys, API tokens, personal information, or data from your test server.
Use English by Default
Product descriptions, required documentation, and setup instructions must be available in English. Default chat messages, interface text, logs, and error output must also be in English. Additional translations are welcome through localization files or language settings.
Describe Your Content Accurately
- Start with a short summary in plain text, without formatting.
- Explain what the submission does and what is included.
- State whether a prefab is standalone or needs other content.
- Disclose known limitations, compatibility issues, and any required setup.
- Use screenshots and videos that show the actual product. Identify anything shown that is sold separately or is not included.
- Only make performance or compatibility claims you can support with testing. Include relevant test conditions when quoting results.
Disclose Dependencies and Extra Costs
List all required plugins, frameworks, accounts, services, and other dependencies in the description before users purchase or download your file. Explain which are required and which are optional, and disclose any additional purchases, subscriptions, or usage fees.
Plugins must not depend on files from another website that require a login or purchase to download or use.
A free download must not be presented as a complete free product if its advertised functionality requires a paid dependency or service. Disclosing a dependency does not exempt it from our rules on DRM, external communication, or quality.
Keep Submissions Safe and Reviewable
Submissions must not contain malware, backdoors, credential theft, hidden commands, or hardcoded access for the author or anyone else. Do not include code that punishes users, damages servers, or interferes with other files in response to disputes, reviews, or license concerns.
If an intended feature deletes data, resets progress, or makes other destructive changes, document it clearly and require the server owner to enable or confirm that action before it runs.
Do not obfuscate or conceal functionality to prevent review. When requested, provide Codefling with the source code needed to review your submission, including custom bundled components. This does not require you to publish private source code to buyers.
No DRM or Third-Party License Authentication
Submissions must not require external license keys, activation servers, purchase verification, or third-party authentication to validate a user’s right to use the file. Buyers must not lose access to a purchased file because an author’s licensing service goes offline.
Authentication needed for a disclosed integration, such as connecting to a game API, is allowed only for that integration. It must not be used to check ownership of the submission or disable unrelated features.
No Phone-Home or Unnecessary External Communication
External communication is allowed only when needed for a feature described in the listing, such as retrieving live game data or sending messages through a configured integration. Document which services the submission contacts, why it contacts them, and what data it sends. Optional integrations must remain inactive until the user enables or configures them.
Analytics, usage tracking, hidden network activity, silent update checks, and remote kill switches are prohibited. Disclosure does not make these features acceptable. Do not collect or transmit data unrelated to the feature the user is using.
Keep Updates Within These Rules
Every update must meet these guidelines. Previous approval does not permit you to add prohibited features later.
Provide a changelog that explains what changed. Clearly flag breaking changes, removed features, new dependencies or costs, and changes to external communication or data handling. Update the description and installation instructions before releasing a version that changes those requirements. Include migration steps when an update affects existing configurations or stored data.
Support Your Users
You are responsible for supporting your submission and responding to refund inquiries under Codefling’s policies. Keep your support instructions current, respond to reported problems, and let users know about known issues. If you can no longer maintain a file, contact Codefling so we can address its status and support for existing buyers.
Respect Platform Standards
Codefling may reject, suspend, or remove submissions that break these guidelines, are unsafe or misleading, no longer work, or are no longer supported. We may request corrections, documentation, licensing evidence, or source code needed for review before approving or restoring a file.
Report Issues
Report problems or suspected violations through our Help Center. Include the file link and enough detail for us to investigate. Send security issues privately, and do not post credentials or other sensitive information in public reports.
Consequences for Non-Compliance
Violations may result in:
- Rejection of your submission.
- Suspension or removal of existing content.
- Account suspension or termination for repeated or serious violations.
We may update these guidelines as needed. You are responsible for keeping your listings and files compliant with the current rules. Continued submission or distribution of your content through Codefling means you agree to the updated guidelines.