Start here
Start with a short game you can finish.
Choose the fantasy, the player's main activity and one target device. Scope a short sequence with a clear ending, then pick the path below that fits how the game plays. Use the finished sequence to estimate the art, writing and testing for the rest.
01. Visual novel
For writers building an adult game around character chemistry and meaningful choices. Begin with one short route and a small cast; branching dialogue and consistent character art are where the workload grows. Recommended engine: Ren'Py. Work through the guides in order, then test the packaged game on your target device.
Plan a small adult game you can finish
Define the player experience, count the assets, and choose a release route before your first adult game grows beyond its budget.
Read the guide →S reading priorityBuild a first Ren'Py story with two endings
Learn dialogue, choices, state, saves and release checks with a small, non-explicit Ren'Py story.
Read the guide →S reading priorityKeep illustrated and rendered characters consistent
Keep a character recognizable across expressions, poses and camera angles with an approved reference and editable production files.
Read the guide →S reading priorityPreserve saves across episodic updates
Keep old saves usable with stable IDs, versioned state, representative test saves and clear update and recovery policies.
Read the guide →A reading priority02. Browser story
Linked passages and a portable HTML release suit writers focused on the story. Start with a handful of passages and one tracked choice; complex state makes routes and access to adult scenes harder to test. Recommended engine: Twine. Work through the guides in order, then test the packaged game on your target device.
Build a browser story with Twine and SugarCube
Build a small SugarCube story with a remembered choice, two endings, and a practical workflow for publishing HTML and testing saves.
Read the guide →S reading priorityDesign route flags, branches and endings
Give choices clear consequences, keep story conditions readable, and test the routes that matter without checking every combination.
Read the guide →A reading priorityTest and release a small adult game
Test routes, controls, saves and the delivered package, then release a build you can identify, support and recover.
Read the guide →A reading priority03. 2D RPG or simulation
Choose this path when exploration or simulation should drive encounters and relationships. Build one map, a small cast and a complete gameplay loop first; extra systems add balancing and testing work. Recommended engine: Godot / RPG Maker. Work through the guides in order, then test the packaged game on your target device.
Choose an engine by the game you are making
Choose between Ren'Py, Twine, Godot, RPG Maker MZ, Unity and Unreal by testing the work your game actually needs.
Read the guide →S reading priorityDesign route flags, branches and endings
Give choices clear consequences, keep story conditions readable, and test the routes that matter without checking every combination.
Read the guide →A reading priorityBudget assets for mobile and browser builds
Budget downloads, memory, video and input responsiveness on target devices while protecting the approved look.
Read the guide →A reading priorityLocalize a narrative game without breaking its interface
Keep character voice, text identifiers, terminology and interface testing aligned across release languages.
Read the guide →A reading priority04. Real-time 3D
For creators who want movement and animated characters to shape the adult experience. Start with one bounded environment, editable assets and a performance budget for the target device; animation and optimization add work beyond assembling the scene. Recommended engine: Godot / Unity / Unreal. Work through the guides in order, then test the packaged game on your target device.
Scope and evaluate a real-time 3D game
Compare Godot, Unity and Unreal with a playable scene, an interaction loop and a performance budget for your target device.
Read the guide →B reading priorityTurn a generated mesh into a game-ready asset
A practical pipeline for cleaning a generated mesh, checking materials and animation, and accepting its runtime cost on target devices.
Read the guide →B reading priorityKeep 3D characters consistent and choose generation or Blender authoring
Keep a recurring 3D character recognizable across poses and outfits, with an editable source, clear permissions and a practical choice of production tools.
Read the guide →A reading priorityBefore release: check rights, the build and publishing rules.
Track rights for Blender, Daz and purchased assets
Track software and asset licenses, distinguish rendered output from runtime data, and document permission for your planned release.
Read the guide →S reading priorityTest and release a small adult game
Test routes, controls, saves and the delivered package, then release a build you can identify, support and recover.
Read the guide →A reading priorityChoose a publishing route for the actual game
Plan an adult game release around storefront rules, AI disclosure, public previews, memberships and payments.
Read the guide →S reading priority