In fictional Ember March, each 10-second expedition starts after the player chooses two items from four: orbit module, guard, magnet, and medkit. The loadout locks at launch. A base auto-attack deals 2 damage every two seconds; orbit raises it to 6. Guard blocks one 5-damage hit. Magnet doubles pickup radius from 2 to 4, and medkit restores 5 health once. Fixed attacks arrive at seconds 3 and 6. Expedition A uses orbit and guard to defeat a 24-health target by second 10. Expedition B uses magnet and medkit to collect a 2-XP orb four units away and survive. Report loadout, hits, damage, pickup, health, and outcome.
Limit gear choices before the expedition begins
Offer four items and two slots. Orbit adds 4 damage to the automatic 2-damage attack that fires every two seconds, for 6 total. Guard blocks one 5-damage incoming hit. Magnet doubles the pickup radius from 2 to 4 units. Medkit restores 5 health once. Show each item’s effect before launch, then lock the chosen pair for the full ten-second expedition.
Keep combat and pickup rules deterministic. The target has 24 health; enemy attacks land at seconds 3 and 6. The XP orb is four units from the player and awards 2 XP. Starting health is 20. No reroll or mid-run swap is allowed. This makes the pre-expedition decision the tested mechanic rather than a menu choice with no consequence.

Use automatic attacks and defense to hunt a target
For Expedition A, select orbit and guard. Automatic attacks fire at seconds 2, 4, 6, and 8, dealing 6 damage each. The target falls at second 8 after exactly 24 damage. Guard blocks the first attack at second 3; the second hit at second 6 deals 5, leaving the player at 15 health. The expedition succeeds because the target is defeated by the ten-second limit and the player survives.
Record each attack tick, damage dealt, blocked hit, remaining target health, and player health. The base attack cadence stays at two seconds; only the chosen orbit module changes damage. This keeps the build choice visible in the combat result without turning the run into a manual-fire test.

Trade attack power for a pickup and recovery tool
For Expedition B, select magnet and medkit. The pickup radius becomes 4, so the orb at distance 4 is collected for 2 XP. Without magnet, the default radius of 2 would miss it. The player takes 5 damage at second 3 and another 5 at second 6, then uses the medkit to restore 5 health, ending at 15. The player survives, collects the objective, and completes a different task than the orbit-and-guard build.
Report the two loadouts side by side: target defeat and health for the combat build; XP collected and health for the pickup build. Include the locked loadout state so no gear changes after launch can explain the result. Ember March and the item values are fictional; this local test checks the stated choices, timings, and outcomes only.

Give the AI a fixed pre-expedition loadout test
Create a survivors-like game in fictional Ember March. Each 10-second run locks two items from orbit, guard, magnet, and medkit. Base auto-attack deals 2 every 2 seconds; orbit raises it to 6. Guard blocks one 5-damage hit. Magnet doubles pickup radius from 2 to 4; medkit heals 5 once. Attacks land at seconds 3 and 6. Run A with orbit+guard against a 24-health target. Run B with magnet+medkit to collect a 2-XP orb at distance 4. Start at 20 health. Report gear, hits, damage, pickup, health, and outcome.
Verify run A: orbit attacks at seconds 2, 4, 6, and 8 for 24 total damage; guard blocks the second-3 hit and the second-6 hit leaves 15 health. Verify run B: magnet reaches the orb at distance 4; two 5-damage hits reduce health to 10 and medkit restores it to 15. Both loadouts stay locked for ten seconds.
FAQ
How can a limited loadout change a survivors-like run?
Restrict the number of items players can bring and make each item affect a different system, such as automatic damage, defense, pickups, or recovery. Lock the selection when the run starts. Then compare how each build handles a fixed objective rather than allowing swaps to erase the choice.
How do I test automatic attacks in a survivors-like game?
Set an attack cadence, damage per hit, enemy health, and run duration. Calculate the attack ticks that occur before the deadline and compare their total damage with the target’s health. Include incoming hits so a defensive item has a measurable effect alongside the attack upgrade.
What should an expedition prototype record?
Record the chosen items, whether the loadout stayed locked, automatic attack ticks, damage blocked and dealt, pickups, player health, and the objective result. Use a second objective that favors different gear. This shows whether pre-run choices create distinct outcomes. across repeated attempts.


