Licensing

Game Developer License

This page is a plain-English summary of the Game Developer License (sometimes called an “Interactive License”). It’s designed for developers using 3D Universe assets in real-time engines and interactive software.

In short

You can use the asset in games and interactive projects, ship commercially, and modify it to fit your pipeline — just don’t redistribute the model files themselves.

What you can do

Use the asset in games, apps, VR/AR projects, simulations, and interactive software.
Use in real-time engines like Unity, Unreal Engine, Godot, or custom engines.
Modify and optimize (retopo, UV changes, baking, LODs, texture changes, format conversion).
Use for commercial and non-commercial releases.
Ship to any platform (PC, console, mobile, web) as part of your compiled/packaged project.

What you can’t do

Do not resell, share, or redistribute the 3D model or source files as a standalone item.
Do not include the asset in asset packs, templates, “starter kits”, or libraries where others can extract/reuse it.
Do not claim authorship of the original model as if you created it from scratch.

Redistribution inside a game

You may embed the asset into your compiled game or application so end users can interact with it as part of the experience. However, end users must not gain access to the raw files (e.g., .fbx, .obj, source textures, rig files) in a way that allows reuse outside your project.

Ownership & royalties

The creator retains copyright of the original asset.
You receive a perpetual, royalty-free license for interactive usage.
Credit is appreciated but not required unless stated otherwise.

Common examples

Allowed: A character used as an NPC in a Unity game (compiled build), including LODs and baked textures.

Allowed: A prop used in a VR experience, shipped on Steam or Meta Quest as an application.

Not allowed: Uploading the model files to a GitHub repo, “mod kit”, or downloadable extras where users can extract the asset.

Not allowed: Selling the model as part of a “50 game-ready assets pack”.

Standard License vs Game Developer License

Use case	Standard	Game Dev
Still renders / illustrations	✅ Yes	✅ Yes
Animations / video	✅ Yes	✅ Yes
Games / interactive apps	❌ No	✅ Yes
Modify / optimize for real-time	✅ Yes	✅ Yes
Redistribute model/source files	❌ No	❌ No

Note: This table is a plain-English overview. If you need custom terms (multi-seat, studio-wide, or redistribution for a closed-source SDK), contact us and we’ll quote a tailored license.

Need something custom?

If your project involves modding tools, user-generated content, downloadable asset bundles, or SDK distribution, we can provide a custom agreement that fits your use case.