[Physics] Ladder the run-off landing check where it refuses run-speed drops

Open
  • Is something wrong?
#784 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Domain
game-dev

Research direction

The run-off check is Argus_DropLandHazard, introduced in #773, and the refused drop links are on e1m8, e1m6, e1m1 and dm4. Start by reading how that check uses the bot's speed and the drop height, then reproduce the offline refusal counts for those maps. Done means stall_parity holds on each map, or each regressed stall cell near a refused link's seat is named with a follow-up issue.

Written by the indexing model from the issue text.

Description

maps physics research

Problem

Argus_DropLandHazard (#773) refuses a heading when a bot running at its current speed would land in lava, slime or a void. Offline, for a bot at 320 u/s leaving each one-way drop link's seat toward its target, it newly refuses 23 e1m8 links (gravity 100, where a 112u drop flies about 480u), 9 dm4 drops into the pit, 3 e1m6 and 2 e1m1 links, and none on dm2, dm3, dm6, e1m5, e1m7 or lqdm2. A slow approach keeps its old verdict, but routed bots usually reach a lip at run speed, so those drops now depend on deflecting and slowing, which can cost stalls.

Only e1m7 and dm4 were laddered. dm4 held stall parity over six tapes.

Proposal

Ladder e1m8, e1m6 and e1m1 against the pre-#773 build with stall_parity registered, and look at stall cells near the refused links' seats. e1m8's low gravity makes it the likeliest to need a speed-aware approach to its drops.

Acceptance

  • Stall parity on each map, or a named cell with a follow-up.
Dominant language
Rust
Stars
4
Forks
0
Avg merge
30m
Merged PRs (30d)
130

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from saworbit/argus

All issues in saworbit/argus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.