THE OPEN-SOURCE GAME CREATION WORKFLOW
From imagination.To playable worlds.
Explore GameFactory-3A: the 3A game-generation skill connecting assets, gameplay and engines. Real demos. Clear guides. Your next starting point.
FANTASY RPG / CINEMATIC STUDYA closer look at what you can create.
01 / IN THE WILD
Ideas, brought to life.
Explore gameplay and cinematics shared by the original project. Every preview leads back to its source.
02 / THE TOOLKIT
Every part of the world.
From the first reference image to the interface a player touches. Eight connected areas, one considered workflow.
Image preparation
Turn a concept or character reference into a clear input for the next asset task.
Explore capability3D objects
Build characters, props and reusable objects, then check how the pieces fit.
Explore capabilityScenes & environments
Establish the ground and layout, then compose a coherent place to play.
Explore capabilityMotion & animation
Connect a character to the movement the game actually needs.
Explore capabilityAudio & atmosphere
Prepare dialogue, effects and ambience around the timing of gameplay.
Explore capabilityGame cinematics
Shape an opening, a story beat or a trailer into a directed video task.
Explore capabilityGameplay systems
Translate the core loop into rules, behavior and engine-native mechanics.
Explore capabilityGame interfaces
Give game state a readable interface: HUDs, menus and responsive feedback.
Explore capability03 / HOW IT WORKS
A process. Not a magic button.
A coding agent coordinates the work. Planning, reviewing and actually playing the result are part of the process.
- 01
Define the idea
Choose an engine, a visual direction, a player loop and clear acceptance criteria.
- 02
Make a plan
Map controls, scenes, assets and the checks that will prove the experience works.
- 03
Create & review
Generate or source assets, then inspect their quality and suitability.
- 04
Bring it together
Integrate mechanics, assets and UI through the selected engine context.
- 05
Play. Refine. Repeat.
Launch the game, exercise representative actions and review a recording before calling it ready.
04 / YOUR ENVIRONMENT
Your engine. Your direction.
Choose the environment for your project, then follow its own API context. Each has a distinct role.
Native worlds, engine-native workflows.
Follow the UEClient boundary for project work and the UE5 guide for native integration and validation.
UnityA familiar home for game prototypes.
Use UnityClient and the documented Unity context to connect generated assets, mechanics and interfaces.
GodotA focused path into Godot 4.
Verify the requested Godot executable before project work, then use the public GodotClient workflow.
three.jsInteractive worlds for the browser.
The upstream three.js toolchain has its own Node and engine requirements. This PHP guide does not run that toolchain.
BlenderPrepare the pieces of a world.
Use the documented bpy environment for neutral asset processing, rigging and repair. Blender is not presented here as a shipped game runtime.
05 / DESIGNED TO CONNECT
The pieces work together.
The framework organizes the handoffs that make assets useful inside a game.
Task-aware skills
Read the skill for the task at hand, instead of loading every unrelated engine and pipeline.
Useful handoffs
Keep asset preparation, gameplay, interface and engine execution responsibilities clear.
Quality in context
Check how an asset behaves inside the actual game, alongside its technical structure.
06 / FIND YOUR START
A place for your next idea.
Start with the part of game creation you want to explore.
Independent developers
Explore a playable slice before expanding the scope of a game.
Agent builders
Understand how task skills and engine context guide a coding agent.
Artists & technical artists
Follow the path from references and assets to an integrated scene.
Researchers & contributors
Read the contracts and contribute through the framework development harness.
07 / FIRST STEPS
Give your idea a brief.
Choose a target, describe the player experience, and let the guide point you to the right skills.
This website is a guide. Run the upstream project in your own prepared development environment. The repository is not a one-command installation of every engine and model.
Start buildinggit clone https://github.com/OpenDCAI/GameFactory-3A.git
cd GameFactory-3A
→ agent_skills/setting_overview.md08 / GO DEEPER
Less searching. More context.
A task-based map of the upstream documentation, with direct links to the source.
Start here
The task entry point for a coding agent: brief, plan, asset review, integration and iteration.
02Assets & quality
A map of asset skills, environment setup and visual quality checks.
03Engine context
Choose one engine context and understand its integration boundary.
04Gameplay mechanics
Understand the gameplay contract and the responsibilities of generated mechanics.
09 / GOOD TO KNOW
Before you begin.
The practical answers, without the fine print.
01What is GameFactory-3A?
It is OpenDCAI’s open-source game-generation skill and asset framework. A coding agent uses its task guides and engine context to coordinate assets, gameplay and interfaces.
02Can I generate a game on this website?
This site provides curated explanations, demos and guides. It does not run a generation service, collect API keys or execute game engines. Use the upstream project in your own environment.
03Does “3A” guarantee a finished commercial game?
No. The project name describes its ambition and scope. A playable result still needs planning, appropriate assets, engine integration and direct runtime review.
04Is using the project free?
The repository is open source. Coding agents, model APIs, hardware, engine services and third-party assets can have separate costs or terms. Check the route you plan to use.
05Which engines and tools are covered?
The upstream guides cover UE5, Unity, Godot 4, three.js and Blender. Blender mainly serves asset processing in the engine contract. Exact versions and workflows are documented upstream.
06Are all the demo assets AI-generated?
No. Several demos combine generated objects with engine-library assets, downloaded scenes or externally sourced animation. The source notes on this site preserve those distinctions.
07Can I use every asset commercially?
The repository uses Apache-2.0, but third-party engines, models, weights and assets retain their own licenses. Review the terms of each component before shipping it.
08Is this the official project website?
This is an independently maintained content guide. The original project and source code belong to OpenDCAI and its contributors; the GitHub repository is the source of the latest documentation.
YOUR NEXT WORLD STARTS WITH AN IDEA
Make the first move.
Explore the project. Choose your direction. Start with a plan.