# How to Make a Terraria-Style Game With AI — Free 2D Sandbox Survival Code

Make an original side-view mining and base-building game. Keep tiles authoritative, crafting transactional and one cave biome playable before growing the world.

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

Original game: Deepwild Hearth
First milestone: A small surface, one cave biome, four mineable materials, a workbench recipe, one enemy, a buildable cabin and saved tile changes.

## Build steps
1. Author surface and cave data
Define air, soil, stone, timber and ore tile IDs. Make a bounded map with a starting ledge, surface trees and a cave entrance. Store tile data independently from the visible layers.
Expected: An original surface and cave with a safe spawn.
Check: Walk and jump across the surface; no spawn or cave exit can be buried.

2. Reuse movement and update collisions
Use Godot 2D platform movement and tile collisions. Tune jump height to your authored ledges. Mine through one coordinate API that changes data, visible tile and collision together.
Expected: Mining opens a real traversable tunnel.
Check: Mine beside the player, at a chunk boundary and below a ceiling.

3. Gather trees and ore consistently
Tree harvest and ore mining emit stable item IDs into inventory. Tool speed may vary but each tile can drop only once. Bound pickup lifetimes and merge nearby resource pickups.
Expected: Materials support a repeatable gather loop.
Check: Hold mining on one cell and reload immediately after harvest: no duplicate item.

4. Craft and build a first cabin
Validate a workbench recipe and material totals, then commit once. Let the player place background walls separately from solid blocks. Reject solid placement inside the player or beyond reach.
Expected: A compact base the player actually built.
Check: Try crafting with missing materials and placing a block over the character.

5. Add one cave enemy and combat
Use patrol, notice, attack and recovery states. Ground enemies read walkable terrain after mining changes it. Give the player one clear melee attack and a visible recovery instead of frame-by-frame damage.
Expected: Caves have a challenge without unreliable collision.
Check: Remove a floor beneath an enemy; check recovery, falling and despawn rules.

6. Save the dig and then expand
Store seed/base version, tile edits, inventory, equipment and position. Rebuild the base and apply validated edits. Add parallax, warm cabin light and ore contrast while keeping interactive tiles readable.
Expected: The cabin and mined route survive restart.
Check: Reload inside the cave, handle a malformed edit and profile a large digging burst.

## 2D — complete AI prompt

BINX Forge — How to Make a Terraria-Style Game With AI — Free 2D Sandbox Survival Code
Build Deepwild Hearth, my ORIGINAL 2D survival game. This is general-mechanics inspiration, not an exact copy of Terraria.
Guide: https://binxforge.com/guides/reimagine-terraria
Open selected Forge build: https://binxforge.com/build?v=2&guide=reimagine-terraria&dimension=2D&camera=Side-view&genre=Survival&theme=Pixel+art&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. The recommended approach: 2D TileMapLayer terrain, CharacterBody2D movement and chunked cave data.
Original world and art direction: Deepwild Hearth; Make an original side-view mining and base-building game. Keep tiles authoritative, crafting transactional and one cave biome playable before growing the world. 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: Side-view. Do not combine engine-specific code unchanged.
FIRST PLAYABLE: A small surface, one cave biome, four mineable materials, a workbench recipe, one enemy, a buildable cabin and saved tile changes.
CORE SYSTEMS:
- Side-view movement, jumping and reach-limited mining
- Destructible tiles and chunk updates
- Materials, inventory and transactional crafting
- Building with player/collision checks
- Surface/cave biomes and simple enemies
- Combat, base construction and persistent world edits

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 · cave tiles and simple enemies; extend with original pixel art.
Kenney Tiny Town — https://kenney.nl/assets/tiny-town — CC0 · a coherent surface/base starting set.
Existing Forge resources: https://binxforge.com/resources/godot, https://binxforge.com/resources/kenney-tiny-dungeon, https://binxforge.com/resources/kenney-ui-pack. 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. Author surface and cave data: Define air, soil, stone, timber and ore tile IDs. Make a bounded map with a starting ledge, surface trees and a cave entrance. Store tile data independently from the visible layers.
Expected: An original surface and cave with a safe spawn.
Check: Walk and jump across the surface; no spawn or cave exit can be buried.

2. Reuse movement and update collisions: Use Godot 2D platform movement and tile collisions. Tune jump height to your authored ledges. Mine through one coordinate API that changes data, visible tile and collision together.
Expected: Mining opens a real traversable tunnel.
Check: Mine beside the player, at a chunk boundary and below a ceiling.

3. Gather trees and ore consistently: Tree harvest and ore mining emit stable item IDs into inventory. Tool speed may vary but each tile can drop only once. Bound pickup lifetimes and merge nearby resource pickups.
Expected: Materials support a repeatable gather loop.
Check: Hold mining on one cell and reload immediately after harvest: no duplicate item.

4. Craft and build a first cabin: Validate a workbench recipe and material totals, then commit once. Let the player place background walls separately from solid blocks. Reject solid placement inside the player or beyond reach.
Expected: A compact base the player actually built.
Check: Try crafting with missing materials and placing a block over the character.

5. Add one cave enemy and combat: Use patrol, notice, attack and recovery states. Ground enemies read walkable terrain after mining changes it. Give the player one clear melee attack and a visible recovery instead of frame-by-frame damage.
Expected: Caves have a challenge without unreliable collision.
Check: Remove a floor beneath an enemy; check recovery, falling and despawn rules.

6. Save the dig and then expand: Store seed/base version, tile edits, inventory, equipment and position. Rebuild the base and apply validated edits. Add parallax, warm cabin light and ore contrast while keeping interactive tiles readable.
Expected: The cabin and mined route survive restart.
Check: Reload inside the cave, handle a malformed edit and profile a large digging burst.

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: Readable mining and crafting — Show a tile outline, ingredient counts and invalid-placement feedback.; Intermediate: Distinct underground biomes — Add two cave materials and one enemy per biome using the same tile/inventory APIs.; Advanced: Settlement and chunk simulation — Add bounded NPC jobs and active-region simulation, then test edited terrain and save migrations.. 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 Terraria-Style Game With AI — Free 2D Sandbox Survival Code
Build Deepwild Hearth, my ORIGINAL 2.5D survival game. This is general-mechanics inspiration, not an exact copy of Terraria.
Guide: https://binxforge.com/guides/reimagine-terraria
Open selected Forge build: https://binxforge.com/build?v=2&guide=reimagine-terraria&dimension=2.5D&camera=Side-view&genre=Survival&theme=Pixel+art&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. Keep the mining plane 2D and use layered backgrounds, lights or 3D props for depth. This is a visual adaptation, not automatic voxel conversion.
Original world and art direction: Deepwild Hearth; Make an original side-view mining and base-building game. Keep tiles authoritative, crafting transactional and one cave biome playable before growing the world. 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: Side-view. Do not combine engine-specific code unchanged.
FIRST PLAYABLE: A small surface, one cave biome, four mineable materials, a workbench recipe, one enemy, a buildable cabin and saved tile changes.
CORE SYSTEMS:
- Side-view movement, jumping and reach-limited mining
- Destructible tiles and chunk updates
- Materials, inventory and transactional crafting
- Building with player/collision checks
- Surface/cave biomes and simple enemies
- Combat, base construction and persistent world edits

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 · cave tiles and simple enemies; extend with original pixel art.
Kenney Tiny Town — https://kenney.nl/assets/tiny-town — CC0 · a coherent surface/base starting set.
Existing Forge resources: https://binxforge.com/resources/godot, https://binxforge.com/resources/kenney-tiny-dungeon, https://binxforge.com/resources/kenney-ui-pack. 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. Author surface and cave data: Define air, soil, stone, timber and ore tile IDs. Make a bounded map with a starting ledge, surface trees and a cave entrance. Store tile data independently from the visible layers.
Expected: An original surface and cave with a safe spawn.
Check: Walk and jump across the surface; no spawn or cave exit can be buried.

2. Reuse movement and update collisions: Use Godot 2D platform movement and tile collisions. Tune jump height to your authored ledges. Mine through one coordinate API that changes data, visible tile and collision together.
Expected: Mining opens a real traversable tunnel.
Check: Mine beside the player, at a chunk boundary and below a ceiling.

3. Gather trees and ore consistently: Tree harvest and ore mining emit stable item IDs into inventory. Tool speed may vary but each tile can drop only once. Bound pickup lifetimes and merge nearby resource pickups.
Expected: Materials support a repeatable gather loop.
Check: Hold mining on one cell and reload immediately after harvest: no duplicate item.

4. Craft and build a first cabin: Validate a workbench recipe and material totals, then commit once. Let the player place background walls separately from solid blocks. Reject solid placement inside the player or beyond reach.
Expected: A compact base the player actually built.
Check: Try crafting with missing materials and placing a block over the character.

5. Add one cave enemy and combat: Use patrol, notice, attack and recovery states. Ground enemies read walkable terrain after mining changes it. Give the player one clear melee attack and a visible recovery instead of frame-by-frame damage.
Expected: Caves have a challenge without unreliable collision.
Check: Remove a floor beneath an enemy; check recovery, falling and despawn rules.

6. Save the dig and then expand: Store seed/base version, tile edits, inventory, equipment and position. Rebuild the base and apply validated edits. Add parallax, warm cabin light and ore contrast while keeping interactive tiles readable.
Expected: The cabin and mined route survive restart.
Check: Reload inside the cave, handle a malformed edit and profile a large digging burst.

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: Readable mining and crafting — Show a tile outline, ingredient counts and invalid-placement feedback.; Intermediate: Distinct underground biomes — Add two cave materials and one enemy per biome using the same tile/inventory APIs.; Advanced: Settlement and chunk simulation — Add bounded NPC jobs and active-region simulation, then test edited terrain and save migrations.. 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 Terraria-Style Game With AI — Free 2D Sandbox Survival Code
Build Deepwild Hearth, my ORIGINAL 3D survival game. This is general-mechanics inspiration, not an exact copy of Terraria.
Guide: https://binxforge.com/guides/reimagine-terraria
Open selected Forge build: https://binxforge.com/build?v=2&guide=reimagine-terraria&dimension=3D&camera=Third-person&genre=Survival&theme=Pixel+art&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. A voxel mining game changes traversal and meshing substantially. Treat it as a separate design using the Minecraft-style guide rather than a drop-in upgrade.
Original world and art direction: Deepwild Hearth; Make an original side-view mining and base-building game. Keep tiles authoritative, crafting transactional and one cave biome playable before growing the world. 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: A small surface, one cave biome, four mineable materials, a workbench recipe, one enemy, a buildable cabin and saved tile changes.
CORE SYSTEMS:
- Side-view movement, jumping and reach-limited mining
- Destructible tiles and chunk updates
- Materials, inventory and transactional crafting
- Building with player/collision checks
- Surface/cave biomes and simple enemies
- Combat, base construction and persistent world edits

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 · cave tiles and simple enemies; extend with original pixel art.
Kenney Tiny Town — https://kenney.nl/assets/tiny-town — CC0 · a coherent surface/base starting set.
Existing Forge resources: https://binxforge.com/resources/godot, https://binxforge.com/resources/kenney-tiny-dungeon, https://binxforge.com/resources/kenney-ui-pack. 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. Author surface and cave data: Define air, soil, stone, timber and ore tile IDs. Make a bounded map with a starting ledge, surface trees and a cave entrance. Store tile data independently from the visible layers.
Expected: An original surface and cave with a safe spawn.
Check: Walk and jump across the surface; no spawn or cave exit can be buried.

2. Reuse movement and update collisions: Use Godot 2D platform movement and tile collisions. Tune jump height to your authored ledges. Mine through one coordinate API that changes data, visible tile and collision together.
Expected: Mining opens a real traversable tunnel.
Check: Mine beside the player, at a chunk boundary and below a ceiling.

3. Gather trees and ore consistently: Tree harvest and ore mining emit stable item IDs into inventory. Tool speed may vary but each tile can drop only once. Bound pickup lifetimes and merge nearby resource pickups.
Expected: Materials support a repeatable gather loop.
Check: Hold mining on one cell and reload immediately after harvest: no duplicate item.

4. Craft and build a first cabin: Validate a workbench recipe and material totals, then commit once. Let the player place background walls separately from solid blocks. Reject solid placement inside the player or beyond reach.
Expected: A compact base the player actually built.
Check: Try crafting with missing materials and placing a block over the character.

5. Add one cave enemy and combat: Use patrol, notice, attack and recovery states. Ground enemies read walkable terrain after mining changes it. Give the player one clear melee attack and a visible recovery instead of frame-by-frame damage.
Expected: Caves have a challenge without unreliable collision.
Check: Remove a floor beneath an enemy; check recovery, falling and despawn rules.

6. Save the dig and then expand: Store seed/base version, tile edits, inventory, equipment and position. Rebuild the base and apply validated edits. Add parallax, warm cabin light and ore contrast while keeping interactive tiles readable.
Expected: The cabin and mined route survive restart.
Check: Reload inside the cave, handle a malformed edit and profile a large digging burst.

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: Readable mining and crafting — Show a tile outline, ingredient counts and invalid-placement feedback.; Intermediate: Distinct underground biomes — Add two cave materials and one enemy per biome using the same tile/inventory APIs.; Advanced: Settlement and chunk simulation — Add bounded NPC jobs and active-region simulation, then test edited terrain and save migrations.. 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.