# How to Make a Pokémon-Style Game With AI — Free Monster-Catching RPG Tutorial

Design your own creatures, wild encounters, battles and collection. Play BINXMON, then use independently public examples to build a different original RPG.

Canonical: https://binxforge.com/guides/reimagine-pokemon

Original game: Lantern Wilds
First milestone: One forest, three original creatures, one companion, two abilities, weakening/capture, collection selection and a validated save.

## Build steps
1. Design three creatures with roles
Give each original species a name, silhouette, habitat, base health and two abilities. One individual instance holds a unique ID, current health and experience; species data must not hold shared mutable health.
Expected: Three different companions can be collected without shared-state bugs.
Check: Damage one individual and confirm another of the same species is unchanged.

2. Build exploration first
Use a Godot top-down movement example and one authored forest. Add run as a default speed or a held action, interact, pause, a joystick and large touch buttons. Keep paths and encounter zones visually distinct.
Expected: The player can navigate a small original forest.
Check: Test touch cancellation, menu focus, narrow paths and movement at different frame rates.

3. Enter encounters through one state owner
Use exploration, encounter intro, player choice, resolution and result states. Freeze world movement during battle. Roll encounters only on valid movement/zone events and apply a cooldown after leaving.
Expected: A battle begins once and returns safely to exploration.
Check: Hold movement into a battle and restart twice: no duplicate encounter or stuck input.

4. Resolve abilities consistently
Choose a move, select a valid target, calculate speed order and resolve health once. Show feedback before advancing the state. Clamp health and prevent a defeated creature from acting.
Expected: A two-ability battle is predictable and readable.
Check: Try equal speed, zero health, an invalid target and a rapid double tap.

5. Capture and select companions
Allow capture only in a wild encounter with a capsule available. Consume one capsule once. Make lower health help capture, use a seeded RNG for tests and give success a new individual ID. Collection selection must preserve health.
Expected: Captures grow the collection without duplicating rewards.
Check: Force success and failure in tests; reload after selecting a wounded companion.

6. Persist progression and polish the forest
Save collection instances, selected ID, inventory, XP and quest IDs. Validate all IDs and clamp counts on load. Add original idle/run/attack frames, local sound, status text and image-independent labels.
Expected: One complete explore, battle, capture and resume loop.
Check: Load an older or corrupt save; verify collection selection and rewards after restart.

## 2D — complete AI prompt

BINX Forge — How to Make a Pokémon-Style Game With AI — Free Monster-Catching RPG Tutorial
Build Lantern Wilds, my ORIGINAL 2D rpg game. This is general-mechanics inspiration, not an exact copy of Pokémon.
Guide: https://binxforge.com/guides/reimagine-pokemon
Open selected Forge build: https://binxforge.com/build?v=2&guide=reimagine-pokemon&dimension=2D&camera=Top-down&genre=RPG&theme=Bright+fantasy&engine=Godot&platform=Browser&players=Solo&budget=Free+only&commercial=Yes&buildScope=full

FIRST RESPONSE: give an achievable first playable milestone and begin one reversible implementation step if you can edit my project. If you are chat-only, give exact files and steps without claiming edits. Inspect and preserve working systems first. Reuse before rebuilding; spend AI effort on my original gameplay and polish. Do not demand private uploads just to provide a plan.

PRESENTATION: 2D. Top-down world and sprite creatures with a separate battle screen. The easiest route for a first collection RPG and mobile controls.
Original world and art direction: Lantern Wilds; Design your own creatures, wild encounters, battles and collection. Play BINXMON, then use independently public examples to build a different original RPG. Use the guide’s illustrations as mood concepts, not finished assets or screenshots. Create my own characters, names, environments and UI.
RECOMMENDED ENGINE: Godot, a free MIT engine. Use an editor and demo branch that match, record the version, and test the export. For 2D target desktop and mobile browsers first; for 2.5D/3D start desktop, then profile and verify browser/mobile compatibility before promising it. Camera: Top-down. Do not combine engine-specific code unchanged.
FIRST PLAYABLE: One forest, three original creatures, one companion, two abilities, weakening/capture, collection selection and a validated save.
CORE SYSTEMS:
- Original creature species and individual IDs
- Controlled wild encounters with cooldowns
- Turn-based abilities, speed order and health
- Capture chance with explicit success/failure
- Collection, active companion and experience
- Inventory, quest reward and versioned saving

SOURCE-REVIEWED FREE CODE AND REFERENCES (not a certified combined starter):
Godot demo projects by Godot contributors
https://github.com/godotengine/godot-demo-projects/tree/b761b4cd5718a7118f2c95eb55f181d0a5f004f1
Licence: MIT code; retain notices and inspect each demo’s asset credits
Official terms: https://github.com/godotengine/godot-demo-projects/blob/b761b4cd5718a7118f2c95eb55f181d0a5f004f1/LICENSE.md
Fit: Use a demo branch matching your Godot editor; individual examples supply systems, not a complete game.
Approach: Feature-sized editor projects for movement, physics, tilemaps and UI. No verified AI-authorship claim.

FREE ASSETS FROM THEIR CREATORS:
Kenney Tiny Dungeon — https://kenney.nl/assets/tiny-dungeon — CC0 · 2D tiles/characters; create original creature silhouettes.
Kenney UI Pack — https://kenney.nl/assets/ui-pack — CC0 · menus and battle controls; no franchise UI is bundled.
Existing Forge resources: https://binxforge.com/resources/godot, https://binxforge.com/resources/kenney-tiny-dungeon, https://binxforge.com/resources/kenney-ui-pack, https://binxforge.com/resources/quest-system. Check each is published and fits the selected dimension; a model pack supplies art, not gameplay code.

CONTROLS: remappable WASD/arrows, genre-specific actions and Escape pause. Add native touch joystick/buttons sized for phones, cancellation/blur cleanup and keyboard-accessible menus. Use running where exploration needs it. Preserve control while separating menus and gameplay.
UI: start, pause, settings/mute, readable objective/status, inventory/equipment/collection where needed, results, save status and manual recovery. No fake account/cloud saving.
ANIMATION/VFX/AUDIO: coherent scale and rig, idle/move/action/recovery states, readable anticipation and hits, restrained particles, original or cleared audio; match sounds to actual events and offer mute.
STATE/SAVING: one owner per gameplay transition; stable IDs, versioned schema, validation, clamped counts, one-time rewards, no transient attack/input state in saves, safe failed-storage handling and migration tests.

PHASED DEVELOPMENT AND EXPECTED CHECKS:
1. Design three creatures with roles: Give each original species a name, silhouette, habitat, base health and two abilities. One individual instance holds a unique ID, current health and experience; species data must not hold shared mutable health.
Expected: Three different companions can be collected without shared-state bugs.
Check: Damage one individual and confirm another of the same species is unchanged.

2. Build exploration first: Use a Godot top-down movement example and one authored forest. Add run as a default speed or a held action, interact, pause, a joystick and large touch buttons. Keep paths and encounter zones visually distinct.
Expected: The player can navigate a small original forest.
Check: Test touch cancellation, menu focus, narrow paths and movement at different frame rates.

3. Enter encounters through one state owner: Use exploration, encounter intro, player choice, resolution and result states. Freeze world movement during battle. Roll encounters only on valid movement/zone events and apply a cooldown after leaving.
Expected: A battle begins once and returns safely to exploration.
Check: Hold movement into a battle and restart twice: no duplicate encounter or stuck input.

4. Resolve abilities consistently: Choose a move, select a valid target, calculate speed order and resolve health once. Show feedback before advancing the state. Clamp health and prevent a defeated creature from acting.
Expected: A two-ability battle is predictable and readable.
Check: Try equal speed, zero health, an invalid target and a rapid double tap.

5. Capture and select companions: Allow capture only in a wild encounter with a capsule available. Consume one capsule once. Make lower health help capture, use a seeded RNG for tests and give success a new individual ID. Collection selection must preserve health.
Expected: Captures grow the collection without duplicating rewards.
Check: Force success and failure in tests; reload after selecting a wounded companion.

6. Persist progression and polish the forest: Save collection instances, selected ID, inventory, XP and quest IDs. Validate all IDs and clamp counts on load. Add original idle/run/attack frames, local sound, status text and image-independent labels.
Expected: One complete explore, battle, capture and resume loop.
Check: Load an older or corrupt save; verify collection selection and rewards after restart.

OPTIMISATION: bound world size and agent/effect counts, profile frame time at busiest points, batch terrain work and cull visuals without deleting persistent state. Test desktop and phone layouts, actual keyboard/touch, pause/restart, denied storage, corrupt saves and repeatable progression. Report tests actually run and remaining limits; screenshots must come from the real project.
LICENSING: preserve exact source notices. MIT source does not clear bundled models, audio, logos or promotional screenshots. Check finished-game sale, raw-file redistribution and source/template inclusion separately. Keep uncertain rights unconfirmed and link exact official terms. No franchise files, private BINX Engine source, proprietary systems, purchased pack files, credentials or unpermitted AI uploads. GDQuest non-commercial art must be replaced for commercial use; Open Theft Auto is reference-only; GPL references are not silently copied into a proprietary starter.
FUTURE UPGRADES: Beginner: Creature collection cards — Add role icons, health and selected-companion feedback without extra species.; Intermediate: Abilities and quests — Add status durations and a single optional collection quest with one-time rewards.; Advanced: Ecology and party strategy — Add biome encounter tables and two-creature synergy while keeping battle rules deterministic.. Add each only after its earlier loop passes. Provide a small milestone first, then a larger progression roadmap. Do not invent percentage savings or publish a broken build.

## 2.5D — complete AI prompt

BINX Forge — How to Make a Pokémon-Style Game With AI — Free Monster-Catching RPG Tutorial
Build Lantern Wilds, my ORIGINAL 2.5D rpg game. This is general-mechanics inspiration, not an exact copy of Pokémon.
Guide: https://binxforge.com/guides/reimagine-pokemon
Open selected Forge build: https://binxforge.com/build?v=2&guide=reimagine-pokemon&dimension=2.5D&camera=Isometric&genre=RPG&theme=Bright+fantasy&engine=Godot&platform=Desktop&players=Solo&budget=Free+only&commercial=Yes&buildScope=full

FIRST RESPONSE: give an achievable first playable milestone and begin one reversible implementation step if you can edit my project. If you are chat-only, give exact files and steps without claiming edits. Inspect and preserve working systems first. Reuse before rebuilding; spend AI effort on my original gameplay and polish. Do not demand private uploads just to provide a plan.

PRESENTATION: 2.5D. A 3D or layered isometric world with original sprite/3D creatures. Keep logical battle state independent from presentation.
Original world and art direction: Lantern Wilds; Design your own creatures, wild encounters, battles and collection. Play BINXMON, then use independently public examples to build a different original RPG. Use the guide’s illustrations as mood concepts, not finished assets or screenshots. Create my own characters, names, environments and UI.
RECOMMENDED ENGINE: Godot, a free MIT engine. Use an editor and demo branch that match, record the version, and test the export. For 2D target desktop and mobile browsers first; for 2.5D/3D start desktop, then profile and verify browser/mobile compatibility before promising it. Camera: Isometric. Do not combine engine-specific code unchanged.
FIRST PLAYABLE: One forest, three original creatures, one companion, two abilities, weakening/capture, collection selection and a validated save.
CORE SYSTEMS:
- Original creature species and individual IDs
- Controlled wild encounters with cooldowns
- Turn-based abilities, speed order and health
- Capture chance with explicit success/failure
- Collection, active companion and experience
- Inventory, quest reward and versioned saving

SOURCE-REVIEWED FREE CODE AND REFERENCES (not a certified combined starter):
Godot demo projects by Godot contributors
https://github.com/godotengine/godot-demo-projects/tree/b761b4cd5718a7118f2c95eb55f181d0a5f004f1
Licence: MIT code; retain notices and inspect each demo’s asset credits
Official terms: https://github.com/godotengine/godot-demo-projects/blob/b761b4cd5718a7118f2c95eb55f181d0a5f004f1/LICENSE.md
Fit: Use a demo branch matching your Godot editor; individual examples supply systems, not a complete game.
Approach: Feature-sized editor projects for movement, physics, tilemaps and UI. No verified AI-authorship claim.

FREE ASSETS FROM THEIR CREATORS:
Kenney Tiny Dungeon — https://kenney.nl/assets/tiny-dungeon — CC0 · 2D tiles/characters; create original creature silhouettes.
Kenney UI Pack — https://kenney.nl/assets/ui-pack — CC0 · menus and battle controls; no franchise UI is bundled.
Existing Forge resources: https://binxforge.com/resources/godot, https://binxforge.com/resources/kenney-tiny-dungeon, https://binxforge.com/resources/kenney-ui-pack, https://binxforge.com/resources/quest-system. Check each is published and fits the selected dimension; a model pack supplies art, not gameplay code.

CONTROLS: remappable WASD/arrows, genre-specific actions and Escape pause. Add native touch joystick/buttons sized for phones, cancellation/blur cleanup and keyboard-accessible menus. Use running where exploration needs it. Preserve control while separating menus and gameplay.
UI: start, pause, settings/mute, readable objective/status, inventory/equipment/collection where needed, results, save status and manual recovery. No fake account/cloud saving.
ANIMATION/VFX/AUDIO: coherent scale and rig, idle/move/action/recovery states, readable anticipation and hits, restrained particles, original or cleared audio; match sounds to actual events and offer mute.
STATE/SAVING: one owner per gameplay transition; stable IDs, versioned schema, validation, clamped counts, one-time rewards, no transient attack/input state in saves, safe failed-storage handling and migration tests.

PHASED DEVELOPMENT AND EXPECTED CHECKS:
1. Design three creatures with roles: Give each original species a name, silhouette, habitat, base health and two abilities. One individual instance holds a unique ID, current health and experience; species data must not hold shared mutable health.
Expected: Three different companions can be collected without shared-state bugs.
Check: Damage one individual and confirm another of the same species is unchanged.

2. Build exploration first: Use a Godot top-down movement example and one authored forest. Add run as a default speed or a held action, interact, pause, a joystick and large touch buttons. Keep paths and encounter zones visually distinct.
Expected: The player can navigate a small original forest.
Check: Test touch cancellation, menu focus, narrow paths and movement at different frame rates.

3. Enter encounters through one state owner: Use exploration, encounter intro, player choice, resolution and result states. Freeze world movement during battle. Roll encounters only on valid movement/zone events and apply a cooldown after leaving.
Expected: A battle begins once and returns safely to exploration.
Check: Hold movement into a battle and restart twice: no duplicate encounter or stuck input.

4. Resolve abilities consistently: Choose a move, select a valid target, calculate speed order and resolve health once. Show feedback before advancing the state. Clamp health and prevent a defeated creature from acting.
Expected: A two-ability battle is predictable and readable.
Check: Try equal speed, zero health, an invalid target and a rapid double tap.

5. Capture and select companions: Allow capture only in a wild encounter with a capsule available. Consume one capsule once. Make lower health help capture, use a seeded RNG for tests and give success a new individual ID. Collection selection must preserve health.
Expected: Captures grow the collection without duplicating rewards.
Check: Force success and failure in tests; reload after selecting a wounded companion.

6. Persist progression and polish the forest: Save collection instances, selected ID, inventory, XP and quest IDs. Validate all IDs and clamp counts on load. Add original idle/run/attack frames, local sound, status text and image-independent labels.
Expected: One complete explore, battle, capture and resume loop.
Check: Load an older or corrupt save; verify collection selection and rewards after restart.

OPTIMISATION: bound world size and agent/effect counts, profile frame time at busiest points, batch terrain work and cull visuals without deleting persistent state. Test desktop and phone layouts, actual keyboard/touch, pause/restart, denied storage, corrupt saves and repeatable progression. Report tests actually run and remaining limits; screenshots must come from the real project.
LICENSING: preserve exact source notices. MIT source does not clear bundled models, audio, logos or promotional screenshots. Check finished-game sale, raw-file redistribution and source/template inclusion separately. Keep uncertain rights unconfirmed and link exact official terms. No franchise files, private BINX Engine source, proprietary systems, purchased pack files, credentials or unpermitted AI uploads. GDQuest non-commercial art must be replaced for commercial use; Open Theft Auto is reference-only; GPL references are not silently copied into a proprietary starter.
FUTURE UPGRADES: Beginner: Creature collection cards — Add role icons, health and selected-companion feedback without extra species.; Intermediate: Abilities and quests — Add status durations and a single optional collection quest with one-time rewards.; Advanced: Ecology and party strategy — Add biome encounter tables and two-creature synergy while keeping battle rules deterministic.. Add each only after its earlier loop passes. Provide a small milestone first, then a larger progression roadmap. Do not invent percentage savings or publish a broken build.

## 3D — complete AI prompt

BINX Forge — How to Make a Pokémon-Style Game With AI — Free Monster-Catching RPG Tutorial
Build Lantern Wilds, my ORIGINAL 3D rpg game. This is general-mechanics inspiration, not an exact copy of Pokémon.
Guide: https://binxforge.com/guides/reimagine-pokemon
Open selected Forge build: https://binxforge.com/build?v=2&guide=reimagine-pokemon&dimension=3D&camera=Third-person&genre=RPG&theme=Bright+fantasy&engine=Godot&platform=Desktop&players=Solo&budget=Free+only&commercial=Yes&buildScope=full

FIRST RESPONSE: give an achievable first playable milestone and begin one reversible implementation step if you can edit my project. If you are chat-only, give exact files and steps without claiming edits. Inspect and preserve working systems first. Reuse before rebuilding; spend AI effort on my original gameplay and polish. Do not demand private uploads just to provide a plan.

PRESENTATION: 3D. Third-person exploration and 3D creatures, with readable battle transitions. Budget rigging, collision and camera work separately from capture logic.
Original world and art direction: Lantern Wilds; Design your own creatures, wild encounters, battles and collection. Play BINXMON, then use independently public examples to build a different original RPG. Use the guide’s illustrations as mood concepts, not finished assets or screenshots. Create my own characters, names, environments and UI.
RECOMMENDED ENGINE: Godot, a free MIT engine. Use an editor and demo branch that match, record the version, and test the export. For 2D target desktop and mobile browsers first; for 2.5D/3D start desktop, then profile and verify browser/mobile compatibility before promising it. Camera: Third-person. Do not combine engine-specific code unchanged.
FIRST PLAYABLE: One forest, three original creatures, one companion, two abilities, weakening/capture, collection selection and a validated save.
CORE SYSTEMS:
- Original creature species and individual IDs
- Controlled wild encounters with cooldowns
- Turn-based abilities, speed order and health
- Capture chance with explicit success/failure
- Collection, active companion and experience
- Inventory, quest reward and versioned saving

SOURCE-REVIEWED FREE CODE AND REFERENCES (not a certified combined starter):
Godot demo projects by Godot contributors
https://github.com/godotengine/godot-demo-projects/tree/b761b4cd5718a7118f2c95eb55f181d0a5f004f1
Licence: MIT code; retain notices and inspect each demo’s asset credits
Official terms: https://github.com/godotengine/godot-demo-projects/blob/b761b4cd5718a7118f2c95eb55f181d0a5f004f1/LICENSE.md
Fit: Use a demo branch matching your Godot editor; individual examples supply systems, not a complete game.
Approach: Feature-sized editor projects for movement, physics, tilemaps and UI. No verified AI-authorship claim.

FREE ASSETS FROM THEIR CREATORS:
Kenney Tiny Dungeon — https://kenney.nl/assets/tiny-dungeon — CC0 · 2D tiles/characters; create original creature silhouettes.
Kenney UI Pack — https://kenney.nl/assets/ui-pack — CC0 · menus and battle controls; no franchise UI is bundled.
Existing Forge resources: https://binxforge.com/resources/godot, https://binxforge.com/resources/kenney-tiny-dungeon, https://binxforge.com/resources/kenney-ui-pack, https://binxforge.com/resources/quest-system. Check each is published and fits the selected dimension; a model pack supplies art, not gameplay code.

CONTROLS: remappable WASD/arrows, genre-specific actions and Escape pause. Add native touch joystick/buttons sized for phones, cancellation/blur cleanup and keyboard-accessible menus. Use running where exploration needs it. Preserve control while separating menus and gameplay.
UI: start, pause, settings/mute, readable objective/status, inventory/equipment/collection where needed, results, save status and manual recovery. No fake account/cloud saving.
ANIMATION/VFX/AUDIO: coherent scale and rig, idle/move/action/recovery states, readable anticipation and hits, restrained particles, original or cleared audio; match sounds to actual events and offer mute.
STATE/SAVING: one owner per gameplay transition; stable IDs, versioned schema, validation, clamped counts, one-time rewards, no transient attack/input state in saves, safe failed-storage handling and migration tests.

PHASED DEVELOPMENT AND EXPECTED CHECKS:
1. Design three creatures with roles: Give each original species a name, silhouette, habitat, base health and two abilities. One individual instance holds a unique ID, current health and experience; species data must not hold shared mutable health.
Expected: Three different companions can be collected without shared-state bugs.
Check: Damage one individual and confirm another of the same species is unchanged.

2. Build exploration first: Use a Godot top-down movement example and one authored forest. Add run as a default speed or a held action, interact, pause, a joystick and large touch buttons. Keep paths and encounter zones visually distinct.
Expected: The player can navigate a small original forest.
Check: Test touch cancellation, menu focus, narrow paths and movement at different frame rates.

3. Enter encounters through one state owner: Use exploration, encounter intro, player choice, resolution and result states. Freeze world movement during battle. Roll encounters only on valid movement/zone events and apply a cooldown after leaving.
Expected: A battle begins once and returns safely to exploration.
Check: Hold movement into a battle and restart twice: no duplicate encounter or stuck input.

4. Resolve abilities consistently: Choose a move, select a valid target, calculate speed order and resolve health once. Show feedback before advancing the state. Clamp health and prevent a defeated creature from acting.
Expected: A two-ability battle is predictable and readable.
Check: Try equal speed, zero health, an invalid target and a rapid double tap.

5. Capture and select companions: Allow capture only in a wild encounter with a capsule available. Consume one capsule once. Make lower health help capture, use a seeded RNG for tests and give success a new individual ID. Collection selection must preserve health.
Expected: Captures grow the collection without duplicating rewards.
Check: Force success and failure in tests; reload after selecting a wounded companion.

6. Persist progression and polish the forest: Save collection instances, selected ID, inventory, XP and quest IDs. Validate all IDs and clamp counts on load. Add original idle/run/attack frames, local sound, status text and image-independent labels.
Expected: One complete explore, battle, capture and resume loop.
Check: Load an older or corrupt save; verify collection selection and rewards after restart.

OPTIMISATION: bound world size and agent/effect counts, profile frame time at busiest points, batch terrain work and cull visuals without deleting persistent state. Test desktop and phone layouts, actual keyboard/touch, pause/restart, denied storage, corrupt saves and repeatable progression. Report tests actually run and remaining limits; screenshots must come from the real project.
LICENSING: preserve exact source notices. MIT source does not clear bundled models, audio, logos or promotional screenshots. Check finished-game sale, raw-file redistribution and source/template inclusion separately. Keep uncertain rights unconfirmed and link exact official terms. No franchise files, private BINX Engine source, proprietary systems, purchased pack files, credentials or unpermitted AI uploads. GDQuest non-commercial art must be replaced for commercial use; Open Theft Auto is reference-only; GPL references are not silently copied into a proprietary starter.
FUTURE UPGRADES: Beginner: Creature collection cards — Add role icons, health and selected-companion feedback without extra species.; Intermediate: Abilities and quests — Add status durations and a single optional collection quest with one-time rewards.; Advanced: Ecology and party strategy — Add biome encounter tables and two-creature synergy while keeping battle rules deterministic.. Add each only after its earlier loop passes. Provide a small milestone first, then a larger progression roadmap. Do not invent percentage savings or publish a broken build.

Concept artwork is AI-generated, not gameplay. Creator repositories provide their own original media and scoped licences. Implementation plans are not whole-project runtime certification.