Nereu Game License and Content Terms

This Game License explains what a maker owns, what Nereu and asset publishers continue to own, and what may travel with a published or exported game. It is part of the Nereu Terms of Service.

The short version is: you own the game you make, subject to the licenses for the ingredients you did not make. You may publish and commercially use the playable result. Nereu's editor, runtime, and supplied assets do not become yours as standalone materials.

1. Your work

You keep ownership of your original writing, rules, art, audio, code, and other content. You also own your game-specific creative selection and arrangement of ingredients: which assets you choose, how you place them, what they do, and how the game plays.

You may host, share, and commercially use the playable result, subject to these terms and any third-party rights. Nereu does not claim ownership merely because you made, saved, published, or exported a game with Nereu.

You are responsible for having the necessary rights to content you upload or otherwise bring to Nereu. Do not use another person's work just because it is available online.

2. Three layers of rights

A Nereu game can contain three legally different layers:

1. Your game-specific work. You own it as described above.
2. Nereu ingredients. Nereu keeps ownership of its editor, player, runtime, Bibi, original presets, authored content, and other software or content. Nereu licenses only the parts needed to run your published game or a build Nereu provides.
3. Third-party ingredients. An asset publisher keeps any rights it has. The source license governs what the asset allows. The current catalog is mostly CC0, but Nereu must not assume every asset is CC0.

The editable project, Bibi conversation, account records, collaboration records, and authoring metadata are not part of a playable build unless an approved export expressly includes them. A downloadable build is not currently a shipped feature.

3. License for Nereu ingredients

When Nereu publishes your game or provides an approved downloadable build, Nereu gives you a nonexclusive, worldwide, royalty-free license to reproduce and distribute the Nereu player, runtime components, and Nereu-owned content included in that playable result. You may run, host, demonstrate, market, and sell access to the game.

This license is limited to the playable game. Unless a separate license says otherwise, you may not extract, sell, sublicense, or distribute Nereu's editor, runtime, presets, source files, or content as standalone products or as part of a competing editor, runtime, software development kit, template library, or raw-asset pack.

The Nereu name and marks are not licensed except for factual statements such as "Made with Nereu" and any branding that Nereu includes in a player or build.

4. Supplied asset packs

An asset cleared for game use may be combined into a meaningful game and published or commercially used as part of that game. An export must include any attribution or notice the source license requires. Nereu should generate a game-specific notice rather than make the maker investigate the catalog.

Do not use Nereu primarily to scrape, extract, or repackage supplied files as a competing raw-asset library. Do not design a game or download whose main purpose is to give other people the supplied source assets in a form they can readily extract.

That product rule does not rewrite a source license. In particular, CC0 lets a person copy, modify, distribute, and commercially use the covered work without attribution, including as a standalone file. If you obtain a CC0 asset from its publisher or otherwise rely directly on CC0, Nereu does not take that right away. Counsel must confirm how Nereu may enforce a no-extraction rule for the copy delivered through its service without misrepresenting the underlying CC0 grant.

Future packs may use a different license. Before adding one, Nereu must confirm that the license permits commercial games, hosted play, downloadable builds, and reasonable technical transformation, and must record attribution and standalone-redistribution rules. A license that permits embedded game use but forbids resale of raw files should say so in the pack's notice. Unknown terms do not count as permission.

5. Current catalog license record

This record describes the evidence found in the repository on 2026-10-08. It is a drafting inventory, not a substitute for a complete rights audit or the source licenses.

Binbun catalog pack ids

All seventeen ids below have committed CC0 evidence:

binbun:beam-vfx, binbun:fire-vfx, binbun:food, binbun:ice-vfx, binbun:impact-vfx, binbun:loot-vfx, binbun:magic-area-vfx, binbun:magic-orb-vfx, binbun:magic-projectiles-vfx, binbun:muzzle-flash-vfx, binbun:poison-vfx, binbun:portal-vfx, binbun:rpg-weapons, binbun:skies, binbun:smoke-vfx, binbun:tools, and binbun:treasure.

Kay/KayKit catalog pack ids

These thirty-two ids draw their files from the pack directories under marketplace/publishers/kay/, each with a LICENSE.txt recording CC0 evidence captured 2026-10-08:

kay:adventurers, kay:block-bits, kay:buildings, kay:characters, kay:city-builder-bits, kay:dungeon-remastered, kay:forest-nature, kay:furniture-bits, kay:halloween-bits, kay:holiday-bits, kay:items, kay:medieval-hexagon, kay:mystery-4-clown, kay:mystery-4-driver, kay:mystery-4-orc-raider, kay:mystery-4-robot, kay:mystery-4-space-ranger, kay:mystery-4-werewolf, kay:mystery-5-helpers, kay:mystery-5-superhero, kay:mystery-5-tiefling, kay:mystery-5-witch, kay:platformer, kay:props, kay:prototype-bits, kay:resource-bits, kay:restaurant-bits, kay:rpg-tools-bits, kay:skeletons, kay:space-base-bits, kay:vehicles, and kay:weapons.

Kenney catalog pack ids

These fifty-one ids draw their files from the pack directories under marketplace/publishers/kenney/, each with a license record. kenney:skyboxes keeps Kenney's own license file; the others record the asset page, captured 2026-10-08, or Kenney's publisher-wide statement where no page was found:

kenney:animated-characters-bundle, kenney:blaster-kit, kenney:blocky-characters, kenney:brick-kit, kenney:building-kit, kenney:car-kit, kenney:castle-kit, kenney:city-kit-commercial, kenney:city-kit-industrial, kenney:city-kit-roads, kenney:city-kit-suburban, kenney:coaster-kit, kenney:conveyor-kit, kenney:fantasy-town-kit, kenney:food-kit, kenney:furniture-kit, kenney:graveyard-kit, kenney:hexagon-kit, kenney:holiday-kit, kenney:marble-kit, kenney:mini-arcade, kenney:mini-arena, kenney:mini-characters-1, kenney:mini-dungeon, kenney:mini-market, kenney:mini-skate, kenney:minigolf-kit, kenney:modular-buildings, kenney:modular-dungeon-kit, kenney:modular-space-kit, kenney:nature-kit, kenney:nature-kit-classic, kenney:pirate-kit, kenney:platformer-kit, kenney:prototype-kit, kenney:racing-kit, kenney:retro-medieval-kit, kenney:retro-urban-kit, kenney:road-pack, kenney:skyboxes, kenney:space-kit, kenney:space-station-kit, kenney:survival-kit, kenney:tower-defense-classic, kenney:tower-defense-kit, kenney:toy-car-kit, kenney:train-kit, kenney:vehicles, kenney:watercraft-pack, kenney:weapon-pack, and kenney:whitebox.

Quaternius catalog pack ids

• quaternius:tanks: pack-root CC0 1.0 license.
• quaternius:medieval-village: source delivery CC0 1.0 license preserved in docs/asset-ingest/quaternius-megakits-monsters-audit.md.
• quaternius:ultimate-monsters: source delivery CC0 1.0 grant, with the wrong-product header warning recorded in that audit.
• quaternius:mechs: CC0 1.0 is recorded in the committed texture README and traced to the free Quaternius delivery.
• quaternius:sci-fi-guns: CC0 1.0 is recorded in the committed parts README.

RG Poly catalog pack ids

• rg-poly:desert-canyon: CC0 1.0; direct product-page evidence is recorded.
• rg-poly:viking-world: CC0 1.0 according to purchaser inventory; provenance warning applies.
• rg-poly:sci-fi-arena: current merged pack built from licensed Sci-Fi Arena 2 and related sources; it is not the excluded unlicensed Sci-Fi Arena v1.
• rg-poly:sci-fi-stash: current merged pack built from the CC0-recorded Cargo and Blue Base sources; product-specific evidence should be strengthened.

Nereu catalog pack ids

The current Nereu ids are nereu:cameras, nereu:characters, nereu:dirty-hal, nereu:floors, nereu:paint-dummies, nereu:particles, nereu:players, nereu:tracks, nereu:vehicles, and nereu:water. marketplace/publishers/nereu/RIGHTS.md records each one's contents and origin.

6. Other ingredients that can reach a game

Catalog packs are not the only third-party ingredients in a playable result. The repository also records:

• Binbun Ultimate Toon and Hologram FX as CC0 1.0, based on their product-page license statements;
• Binbun Modular Transitions as converted Nereu loading chrome, but its audit records no license file and does not state a specific storefront license;
• Quaternius animation sources as CC0; and
• mixed Nereu-authored, commissioned, Kay-derived CC0, and Quaternius-derived CC0 animation material, with source notes in marketplace/publishers/nereu/animations/README.md.

Every runtime ingredient that can ship in a downloadable build needs the same machine-readable rights record as a catalog asset. Binbun Modular Transitions must be treated as an unresolved license until its purchase terms are captured and reviewed.

7. AI-generated asset packs

Nereu's current catalog policy rejects AI-generated asset packs. A maker should not infer from a catalog listing that Nereu guarantees every source's authorship beyond its recorded audit. Publishers and Nereu must preserve provenance evidence, and a disputed or falsely described pack may be removed or blocked from publishing and export.

8. Remix copies and demo copies

When a maker enables "Make your own," the maker licenses another Nereu maker to create and edit a separate copy inside Nereu. That license covers the maker's game-specific work only to the extent needed to use the copy. Asset and runtime restrictions travel with it. The remixer owns new original work but does not acquire the source maker's ownership or a standalone asset license beyond what the original publisher grants.

A Nereu demo on /start is a copy, not a pointer to the maker's original game. Nereu does not receive permission to create a house-owned demo copy from this Game License. It must get separate, specific permission until Arturo and counsel approve a durable demo rule.

9. Notices and export gate

Before downloadable builds launch, each asset and runtime ingredient must carry machine-readable fields for its source, license identifier, evidence, attribution text, export permission, and standalone-redistribution rule. The exporter must:

1. list every ingredient in the build;
2. refuse an ingredient whose license or export permission is unknown;
3. include required licenses and attribution in a human-readable notice;
4. include only the runtime files needed to play the game; and
5. test that editable projects, Bibi history, credentials, unrelated assets, and source libraries are absent.

The current catalog manifest does not carry that complete license record. Consequently, this draft is not authority to enable downloadable exports.

10. Removal and continuing use

If Nereu loses the right to offer an ingredient or reasonably believes its provenance is unsafe, Nereu may stop new use, publishing, or export of that ingredient and help the maker replace it. Counsel must decide whether and when an already published game may continue running.

A license validly granted for a completed downloadable build should remain with that build to the extent the source license and law allow. Nereu should not promise that durability until each ingredient's terms support it.

11. No warranty of third-party rights

Nereu will use reasonable review and provenance records, but third-party publishers remain responsible for rights they claim to grant. Any disclaimer, remedy, takedown process, liability allocation, and maker indemnity must be written or revised by counsel for the launch jurisdictions.