Files
aeternalis/docs/CONTENT-PROJECTILE-FEEDBACK.md
T

4.4 KiB
Raw Blame History

Control and projectile feedback slice

September 9 follow-up to milestone 4, before milestone 4.5 presentation work.

Readable Control and versioned biomes

Content definitions and publication previews use labeled fields, nested lists, and resolved reference names. Stat formula previews no longer display JSON.

Create a biome by selecting existing resources, including resources first made for other biomes. Edit biome publishes the next numbered revision with the same server-created permanent ID. Previous revisions remain readable in the biome's history. Replays cannot create extra revisions; stale catalog edits are rejected. Empty selections are supported. Resources are referenced, never duplicated.

The resource editor also updates the selected biomes when creating a new resource, archiving their previous assignments and incrementing their revisions. Legacy biomes derive initial assignments from existing resource definitions. Explicit biome resource lists govern new terrain generation afterward. The history is bounded to 1,024 archived revisions across the catalog; no automatic deletion.

Explored chunks keep saved resources, biome name/color, geometry, and depletion. Changes apply to unexplored chunks of the current generator. Legacy generator-1 worlds retain their legacy node generation. Mob biome references keep their stable IDs; new biome revisions do not break those references. Other content types continue to use the existing immutable-definition workflow.

Visible projectile launches and outcomes

The server retains a bounded two-second history of launches and impacts, so a flight that completes between snapshots can still be presented. The browser animates a bright projectile toward the last selected target position and displays an orange hit flash or gray miss/terrain flash from the server's outcome. No client prediction awards damage. For extremely short flights, animation has a 100ms minimum so it can be seen; this does not delay authoritative combat resolution.

Attack authoring now has weapon base speed, Dexterity contribution, and Strength contribution. Player flight speed is sampled when fired:

clamp(base speed + final Dexterity × dexterity coefficient + final Strength × strength coefficient, 1, 100) m/s

New default profiles use provisional coefficients 0.1 and 0.05. Existing acquired weapons and published profiles retain their copied settings; missing coefficients mean zero. Create a new attack profile and weapon to use the new coefficients. Changing stats or equipment after firing cannot change that projectile's speed. Mob projectiles currently use the attack's base speed; mob primary stats are not implemented. All damage, swept collision, terrain collision, and misses remain Go-owned.

The launch/impact event lifecycle and presentation module are foundations for curved and seeking trajectories. Those path types, turn limits, target-loss rules, and their authoring controls remain future work; current shots stay straight and can be avoided by moving out of their path.

Manual playtest

  1. Browse Gathering, Resources, Biomes, Attacks, Mobs, Loot, and Spawns. Definitions and previews should read as labeled values with names, including in dark mode.
  2. Create a biome selecting an existing Young tree and ore. Check that Resources still has one copy of each. Edit the biome, deselect ore, and publish. Confirm the same biome identity, next revision, and original assignment in history.
  3. Visit unexplored regions in a current-generation world. New assignments apply; revisiting previously explored regions after restart keeps existing nodes.
  4. Create an attack with slow base speed and nonzero Dexterity/Strength coefficients. Create and equip a weapon using it. Shoot a moving mob: watch travel, a confirmed hit flash or miss flash, and corresponding HP. Test a close target as well.
  5. Change the character's stats before firing again. New shots use the new speed; a shot already traveling keeps the sampled speed. Opening a menu stops auto-fire.

Server checks cover revision preview/publication/replay/conflict, resource reuse, empty selections, unknown references, saved explored layouts, speed sampling, and launch/impact events for a flight shorter than a snapshot interval. Routine Playwright runs remain deferred; the user manually tests this build.

The environment reference and meaningful obstacle jumping are recorded in the environment backlog.