Submission Guidelines

These guidelines apply to all categories of submissions, ensuring that all content on Codefling meets our quality and usability standards. By submitting your work to Codefling, you agree to the following terms and conditions.

Be Original and Authentic

All submissions must be your original work or properly licensed. These guidelines apply to all content submitted to Codefling, regardless of type, category, format, or purpose.

AI-assisted work is allowed when AI is used as a tool, not as the author. You may use AI to help brainstorm, explain concepts, clean up wording, debug, refactor, or speed up parts of your workflow. However, you must understand the work, be able to maintain it yourself, and take full responsibility for what you submit.

We do not accept vibe coded files. “Vibe coded” means content that was mostly generated by AI through prompts, with little meaningful understanding, control, or authorship from the submitter. If the file depends on AI to create, explain, repair, or maintain it, it does not meet our standards.

Testing the file does not make an AI-generated submission acceptable. Even if it appears to work, was carefully tested, or only uses AI-generated sections, it may still be rejected if AI replaced human authorship. There are no exceptions for paid submissions.

AI-generated files may only be considered when they are:

• Free.
• Transformative.
• 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 any other submission.

If a free AI-generated submission is accepted, it does not prevent a human developer from later creating their own version of the same idea. Human-developed submissions may take priority and may be accepted even if they are similar in concept, since Codefling prefers submissions from authors who can fully understand, maintain, update, and support their work.

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 are allowed only when they meet a clear quality standard and accurately represent the submission. Low-quality AI images, obvious AI slop, fake screenshots, distorted visuals, unreadable text, strange anatomy, incorrect objects, misleading scenes, or images that do not reflect the actual product will not be accepted.

Your product images are part of how users judge the quality and trustworthiness of your work. If a submission is presented with generic or low-quality AI artwork, it makes the product look rushed, misleading, or unsupported. Even simple organic images are better than poor AI images. In-game screenshots, editor screenshots, clean UI previews, or basic images showing the actual content are strongly preferred.

Product images should help users understand what they are getting. They should not be used to make a submission look more polished, complex, or feature-rich than it actually is.


Follow Licensing and Fork Policies

You are responsible for setting the appropriate license for your content. Ensure your licensing prevents unauthorized redistribution or modification. For forked content:

• Comply with the original author’s licensing terms.
• Include significant improvements or differences from the original.
• Avoid using any assets from the original submission unless explicitly permitted.

Maintain Quality and Functionality

To uphold the marketplace’s standards, ensure your submissions are functional, error-free, and well-documented:

• For maps and prefabs, check for issues like overlapping geometry, flickering, missing assets, or improper alpha masks. Include terrain modifiers (height, splat, topology, biome) for non-standalone prefabs where applicable.
• For plugins, scripts, and tools, your code must be free of critical errors and tested in a live or simulated environment. Avoid excessive performance overhead, and use efficient, modern coding practices.
• Provide clear documentation and setup instructions so users can install and configure your submission with minimal confusion.
• Submissions must remain compatible with the latest versions of the software they’re intended for. Content that is no longer maintained or fails to meet current standards may be suspended or removed.

Ultimately, if you're sharing something meant for others to use, take the time to polish it. Submissions that feel rushed, broken, or poorly supported won’t be accepted.

Provide Clear and Informative Descriptions

Help users understand your content by including:

• A concise summary in the first paragraph (raw text, no formatting).
• A detailed explanation of the purpose and functionality of your submission.
• A note if your submission is a standalone prefab or includes specific requirements.

Respect Platform Standards

Codefling reserves the right to:

• Reject submissions that fail to meet these guidelines.
• Remove content that is reported as broken, misrepresented, or non-functional.
• Suspend access to inactive submissions without updates or support.
   

No DRM or Third-Party Authentication

Submissions must not include any form of Digital Rights Management (DRM) that requires third-party authentication, external licenses, or verification services. We do not allow such systems because they depend on the author’s ability to maintain uptime for external services, and sunsetting such systems creates significant issues for users. All content must be fully functional without requiring external servers or services to authenticate or validate usage.

No Phone-Home or Unnecessary External Communication

Submissions must not contain code or functionality that “phones home” or communicates with external services unless such communication is required for core functionality that is clearly explained in the description. Plugins, scripts, and tools should not send or receive data from outside the user’s environment for purposes unrelated to their intended operation. Any required external communication must be essential to the plugin’s functionality (for example, retrieving live game data) and must be documented in the submission details.

This restriction includes analytics, usage tracking, or any form of hidden network activity. Authors must not implement remote kill-switches, silent update checks, or external service dependencies except where explicitly necessary and disclosed.

Support Your Users

As the author, you are solely responsible for providing support and handling refund inquiries. Maintaining engagement and updates ensures the long-term success of your submission.
 

Report Issues

If you notice violations or encounter issues with submissions, report them to our support team at https://codefling.com/help.
 

Consequences for Non-Compliance

Violations of these guidelines may result in:

• Rejection of your submission.
• Removal of existing content.
• Account suspension or termination in cases of repeated or severe infractions.
   

We reserve the right to modify these guidelines at any time. Your continued use of Codefling signifies your acceptance of the latest policies. Thank you for contributing to a vibrant and innovative community!