[4ian]

Adds expanded versions of four first-person starters: the same game, on a map made with the 3D terrain extension, modeled on the 3D GTA Expanded. The original starters are unchanged.

The expanded starters are named starting-expanded-<starter> and " Expanded": they are more than starters (a map for now, maybe more later), and their slug tells them apart from the starters.

The FPS variant is built from the 3D FPS game with enemies of #1076 (with its enemies walking with navmesh pathfinding, done there). It is a project of its own: this PR doesn't need #1076 to be merged first.

Uses the theme support for custom objects, the terrain.* slots and the model slots for scattered models of #1082 (merged). Based on the latest main (the skyboxes in the standard cube orientation of #1069 included). Same approach as #1086.

The starters

Starter	Map
starting-expanded-first-person-farming — "3D First Person Farming Expanded"	6144 px: a farm (barn, silo, windmill, coop) with flat fields of dirt plots, a pond, paths and hills around.
starting-expanded-first-person-horror — "3D First-Person Horror Game Expanded"	4096 px: a dark, foggy forest of dead trees and pines on mounds and hollows, a cabin in a clearing. The lighting of the starter (fog, flashlight) is kept.
starting-expanded-first-person-shooter-horror — "3D FPS Horror game with Gun Expanded"	4096 px: a graveyard with crypts on top of a hill, a dead forest on rolling hills. Fog and lighting kept.
starting-expanded-first-person-shooter-enemies — "3D FPS with enemies Expanded"	4096 px: a canyon with cover on uneven ground, crates, a container, a ramp up to a plateau, and six enemies looking for the player.

Each variant is built from the starter as it is on main. What changed in the events is only what the map needs:

• the terrain (3D physics) replaces the ground box and is added to the groups the starters raycast against (RaycastSurface of the farming starter, the obstacles the monsters see through, what bullets hit), so seeds are placed and bullets hit on the terrain;
• the monsters walk with navmesh pathfinding (NavMeshPathfinding), instead of the grid pathfinding of the starters with an invisible obstacle at each tree. The terrain, the trunks of the scattered trees, rocks, logs and stumps (their trunk collisions give a surface to the navmesh), the cabin, the crypts, the walls and the graves have the navmesh obstacle behavior: the navmesh follows the forest if it is painted again. The monsters keep their state machine, and the chase also follows the navmesh (the path to the player is updated twice per second) instead of pushing the monster with forces. Their 3D physics body is kinematic in the horror starter (moved by the navmesh, it still collides with the player). In the FPS horror, the walking monsters are kinematic too (the player bumps into them without pushing them), and a shot monster is still thrown back by the impulse at the impact of the starter: the "Body type" action of the 3D physics (Add an action to change the body type of 3D physics objects 4ian/GDevelop#9270) makes its body dynamic right before the impulse;
• no Ground box under the terrain: the patrol of the monsters (and the monsters appearing in the FPS horror) picked random points inside the ground box of the starter. They now pick them on the terrain, away from the mountains around it: inside the terrain, without an eighth of it on each side (Terrain.BoundingBoxLeft() + Terrain.Width() / 8…, with a comment in the events). The ground box and its textures are removed;
• the monsters of the FPS horror starter are put on the ground when they appear (PutOnGround action of the terrain);
• FPS with enemies: the enemies already walk with navmesh pathfinding in the starter. On the map, the navmesh is built from the terrain (slopes over 40° can't be walked on), the rocks and the cacti (scattered models with trunk collisions) and the cover (obstacles only): the enemies walk around the cover and up the ramp to the plateau. The random destinations of the patrol are picked on the terrain like in the horror starters, and put on it (Terrain.GroundZ). The terrain and the cover hide the player from the enemies and stop the bullets. As in the starter, the walking enemies are kinematic and a shot enemy becomes dynamic, to be thrown back by the impulse at the impact.

The "Body type" action needs GDevelop 5.6.285 (released on October 21): an older GDevelop doesn't know it and would skip it, and a shot enemy or monster wouldn't be thrown. So the database asks for GDevelop 5.6.285 or later for the examples using it (scripts/lib/ExampleGDevelopVersion.js, also in #1097; an older GDevelop shows "Download the latest version of GDevelop to check out this example!").

Each variant has its forests, bushes, rocks and plants as scattered models (Terrain3D::ScatteredModels, GPU instancing, their Model mapped to the nature.* model slots), mountains around the playable area and invisible walls at the limits, its shape in the Edits property of the terrain (generated by a script running the terrain and scatter code of the extension), ambientCG ground textures with normal maps, grass on the whole terrain (one Grass instance: it only grows where its layer is painted and on gentle slopes, drawn in chunks of 500 px, the far ones hidden), CC0 asset-store models credited in its README, a new project UUID, a preview.png from a 1280×720 screenshot, the latest version of every extension it uses (including GDevelopApp/GDevelop-extensions#2310), and its objects mapped to theme slots.

The pond of the farming starter is a Water3D with an opacity of 120, wave crests 231;248;255, foam 0.05, ripples from assets/WaterNormalMap with a size of 600, wave height 2, wave length 150 and wave speed 1.8.

The events of these starters are unfolded, except the groups (which can stay folded).

The objects are in folders: World (terrain, limits, grass, water), Nature (the scattered trees, rocks and plants), and a folder for the objects of the map around the player, with PushableBox in it: Decoration (horror), Graveyard (FPS horror), Training ground (FPS with enemies).

Tests

The tests of the starters are kept and run on the map, with tests added for the gameplay the map changes (in bold):

• Farming: walking and strafing; harvesting a seed patch; a seed can be placed on the terrain.
• Horror: walking and strafing; the monster comes after the player.
• FPS horror: walking and strafing; shooting leaves an impact; a shot monster is thrown back and tumbles.
• FPS with enemies: the two tests of the submission (moving and shooting, killing an enemy); a shot enemy is thrown back and tumbles; a patrolling enemy walks toward the player; an enemy that sees the player catches them.

Removed, because they check how the map is made, which a game made from the starter will change (they would break as soon as the map is edited):

• Farming: "The player and the plots start on the ground", "The player walks up a hill", "The scattered trees and plants grow on the ground".
• Horror: "The player and the monster start on the ground", "The monster goes around the cabin to catch the player", "The player walks up a mound of the forest", "The scattered trees and plants grow on the ground".
• FPS horror: "The player walks up the hill of the graveyard", "Monsters appear on the ground" (the monsters appear at random places, and one appearing on a grave stood above the terrain: it failed once on CircleCI), "The scattered trees and plants grow on the ground".
• FPS with enemies: "The player and the enemies start on the ground", "An enemy goes up the ramp to catch the player on the plateau", "The player walks up the ramp to the plateau", "The scattered trees and plants grow on the ground".
• In the tests kept, the checks of how the physics body is set (kinematic while walking, dynamic when shot) and of the height of an enemy above the ground: the tests check that a shot monster is thrown back, and that an enemy walks to the player.

The tests render at 160×90 without shadows, with the grass and the scattered models hidden, and with a 60 s timeout (120 s for the two tests of the FPS submission, as in the starter: one took 58 s of its 60 s). For the tests of the starters, which act at the center of the screen, the 2D layers (mobile controls, UI, crosshair) are zoomed out to show what they show at 1280×720. All 13 tests pass with node scripts/run-gameplay-tests.js and the latest build of GDevelop's master (the one the CI uses). ExampleGDevelopVersion.spec.js checks the GDevelop version asked for the examples; jest, tsc and prettier pass.

Events compared to the starters

What changed in the events of each starter, compared to the starter it expands:

Starter	Instructions (starter → expanded)	Changes in the events
Farming	171 → 171	None. The terrain replaces the ground in the RaycastSurface group.
Horror	60 → 66 (+14, −8)	The monster walks with navmesh pathfinding: the actions of the grid pathfinding become MoveTo of the navmesh (patrol, chase), the chase re-paths every 0.5 s instead of pushing the monster with forces, and the random places of the patrol are on the terrain (without an eighth of it on each side) instead of the ground box.
FPS horror	98 → 106 (+19, −11)	The same as the horror for the monsters, and: the monsters appear on the terrain and are put on the ground (PutOnGround); a shot monster becomes dynamic (Body type action) before the impulse.
FPS with enemies	99 → 99 (3 changed)	The random destinations of the patrol are on the terrain (Terrain.GroundZ), instead of the ground box.

Screenshots

Views of the maps (1280×720, scaled down):

3D First Person Farming Expanded

3D First-Person Horror Game Expanded

3D FPS Horror game with Gun Expanded

3D FPS with enemies Expanded

The horror maps are dark, as in the starters (fog, flashlight).

The horror maps lit up (without the fog, with a bright light), to show the grass covering them:

3D First-Person Horror Game Expanded, lit up

3D FPS Horror game with Gun Expanded, lit up

With themes applied (built from GDevelopApp/GDevelop-assets#704), first view and overview. These were taken before the grass covered the whole terrain and before the new water settings:

Farming: farm, winter	Horror: halloween, winter

FPS horror: zombie, graveyard	FPS with enemies: military, space

Not done / to check

• The chase re-paths twice per second, and each new path puts the monster back on the navmesh, which resets its speed: the monsters run at about 150 px/s on average (the max speed is 200 for the horror monster, 150 for the FPS ones).
• On slopes, the navmesh is up to ~4 px above the terrain, so a walking monster can float that much.
• The starters are not added to the AI prompts (GDevelop-ai-prompts).
• npm run build (database) stops in this sandbox when fetching the deployed themes (proxy), after the examples are read. The theme slots were checked with checkStarterThemeSlots, and every theme was applied to every new starter with applyThemeToStarter.
• Performance was not measured on a phone.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Wa8uKpYuQrYqGYnqGCsquj

[github-actions]

Preview the game(s) changed or added in this Pull Request

• https://editor.gdevelop.io?project=https://raw.githubusercontent.com/GDevelopApp/GDevelop-examples/claude/awesome-knuth-vaoj1s-first-person-maps/examples/starting-expanded-first-person-farming/starting-expanded-first-person-farming.json
• https://editor.gdevelop.io?project=https://raw.githubusercontent.com/GDevelopApp/GDevelop-examples/claude/awesome-knuth-vaoj1s-first-person-maps/examples/starting-expanded-first-person-horror/starting-expanded-first-person-horror.json
• https://editor.gdevelop.io?project=https://raw.githubusercontent.com/GDevelopApp/GDevelop-examples/claude/awesome-knuth-vaoj1s-first-person-maps/examples/starting-expanded-first-person-shooter-enemies/starting-expanded-first-person-shooter-enemies.json
• https://editor.gdevelop.io?project=https://raw.githubusercontent.com/GDevelopApp/GDevelop-examples/claude/awesome-knuth-vaoj1s-first-person-maps/examples/starting-expanded-first-person-shooter-horror/starting-expanded-first-person-shooter-horror.json

---

This is an automatic message displaying links to the games in this PR - double check the JSON in case of doubt.

[4ian]

ci/circleci: install failed (job 10014). The failure isn't in this PR: the job died in cd GDevelop/newIDE/app && npm install with npm ERR! code ECONNRESET / network aborted, a network error while downloading packages, before any test ran. The same job is running normally on #1086 and #1088, whose heads have the same base.

No code fix applies. Re-running the workflow from CircleCI should clear it. I can't re-run CircleCI jobs from here, and I won't push an empty commit to retrigger it. I'm keeping this PR watched until it's green.

---

Generated by Claude Code