The Charon Builder Code

1. Build your own work

Every corvette you upload should be your own design, or a credited collaboration where every contributor is acknowledged in the description. Copying another builder's corvette and republishing it under your name is the fastest way to lose your upload privileges.

Direct ports of recognizable copyrighted ships (the Millennium Falcon, a Star Destroyer, a USS Enterprise) are allowed as fan tributes — clearly named, clearly described as inspired-by, and not sold or framed as official. Charon doesn't take a position on IP holders' enforcement; that's between you and them.

2. Be honest about how you built it

Every ship is tagged with one of three build methods: In-game, Blender, or Hybrid. Pick the one that actually describes your workflow. There's no premium tier of method — Charon treats all three equally, and customers filter by what they prefer.

Lying about method to look more or less "authentic" damages trust in the catalog for every other builder. If a mod finds a ship tagged In-game that was clearly Blender-built (or vice versa), the tag gets corrected and a note goes on your account.

3. No exploitative content

Charon doesn't host corvettes that exist to harass, demean, or harm. That includes:

• Hate-symbol-shaped builds (regardless of "irony")
• Builds that target specific people for ridicule
• Sexual or pornographic imagery
• Builds whose names, descriptions, or visible text contain slurs or harassment
• Anything designed to crash other players' games

The mod team makes the call on edge cases. If a ship is rejected and you think the call was wrong, you can ask for a senior review in the Discord.

4. Catalog accuracy

Photos should be of the ship customers actually receive. Don't upload a heavily-edited promo render that doesn't match the in-game build. Don't list amenities the ship doesn't include. Don't claim platforms you haven't personally verified on.

Customers report inaccuracies through the delivery issue form. Repeated accuracy complaints from independent customers get a mod review.

5. The 6,000-part threshold

Builds under about 6,000 parts auto-publish to the public catalog. Builds over that threshold get a pre-publish mod review (typical turnaround: 24 hours). This isn't a quality signal — it's a delivery-cost signal. Larger builds put more strain on the bot's session, on the customer's hardware, and on the cross-platform compatibility envelope. The review checks that an oversized build is worth the cost.

If your build clears the review, it gets a "Modern Hardware" tag in the catalog so customers on older platforms know what they're ordering.

6. Verified Builder status

Anyone can upload to the public catalog. Verified Builder is a separate, optional status the mod team grants after reviewing a sample submission. It earns you priority placement in the catalog, a branded profile page, and an invitation-only Private Catalog showroom.

Verified status can be revoked if a builder's later work consistently violates this Code. The mod team doesn't pull badges casually, but the badge means something — keeping it means meeting the bar.

7. Personal builds & the Private Catalog

Verified Builders can keep a separate Private Catalog — unlisted ships visible only to people they invite. This is the space for personal builds, friend-shares, event audiences, and private viewings. Same rules from sections 1–4 still apply (your own work, honest tags, no exploitative content), but discovery is at your discretion.

The Private Catalog is a showroom, not a marketplace. Charon does not facilitate or condone direct payments to builders for ships — money pays for the delivery service, not the build. Builders who turn their Private Catalog into a fee-for-build arrangement risk losing Verified status.

8. How violations are handled

The mod team uses a graduated approach:

• First-time minor issue — note on the ship, request to fix or remove, no account action.
• Repeat minor or first-time major — ship removed from the public catalog, account warning logged.
• Repeat major or anything in section 3 — upload privileges suspended; Verified status revoked if applicable.
• Bad-faith pattern — full account suspension.

Decisions can be appealed in the Charon Discord. The team won't always agree with you, but you'll always get a real human response.

9. Changes to this Code

This Code will evolve. When it changes meaningfully, the team posts a summary in the Discord and updates the "Last revised" date at the top. You'll never be retroactively punished for a build that complied when it was uploaded — but you'll be expected to bring uploads into compliance with new rules going forward.