Scenes: dezo_endgame.rs misses or approximates retail waits (tower tops, Re-Faze, the guardians, Profound Darkness)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- game-dev, testing-qa
Research direction
Start with the wait census rows in rust/psiv-core/src/scenes/wait_census.rs and the scene script in dezo_endgame.rs, matching the offsets listed for each event against the census. Run cargo test -p psiv-core --lib wait_census with the US image to see which rows still read Missing, Recorded or defect. Done means each listed wait is a native Wait of the right length and loop kind, or its omission is justified in docs/source-notes/README.md, and a scene test drives the repaired timing.
Written by the indexing model from the issue text.
Description
Found by the #470 wait census of dezo_endgame.rs (#519). Each wait below is a row in rust/psiv-core/src/scenes/wait_census.rs naming this issue, checked against the US image. Offsets are US retail; counts are the dbf passes (n + 1).
Event_StrengthTowerTop ($070E4E)
17 DoMainUpdatesLoop calls and 2 Event_StepObject calls against 5 native Waits.
$070E7C,$070E9E,$070EC0,$070EE2(15 frames each): ops 2-5 (ObjectAnimation,frames: 15) record the count, but the runner does not block onObjectAnimation.- No native wait:
$070F16(4),$070F28(60),$070F30(30),$070F60(20),$07100C(6),$0710B2(30). - No op: the two
Event_StepObjectcalls at$070F44and$070F58(8 passes each: map updates, no field-object update). - Op 12's
Wait 60is$0710DE. Retail runs it after the speed-8 pan ($071074), theSFXID_EnemyKilledand the 30-frame wait. The transcription runs it before the pan. The pan back toCharacter_1is #565.
Event_CourageTowerTop ($071102)
$071152,$07118A,$0711BA,$0711F2(2 frames each): ops 3-6 (ObjectAnimation,frames: 2) record the count but don't block.- The second round of four
$2BCspawns and their twoSFXID_Foi($0711FE..$0712CF) has no ops. Neither do its waits at$07122A,$071262,$071292and$0712CA(2 each), or$0712D2(10). - No native wait:
$07139E(2),$0713F0(20). The final$071426(30) is #565's.
Event_ReFaze ($07157A)
$07160C(DoMainUpdatesLoop, 63): op 10 (ObjectAnimation,frames: 63) records the count but doesn't block.- Op 13's
Wait 64stands for the 64-frameloc_58666restore at$071636, which runs no map updates. It is transcribed after theSFXID_FireBreath, where retail runs the 136-frameDoMainUpdatesLoopat$071652, which has no wait. - The Megid branch: the two 40-frame
Pal_IncreaseToneloops ($071688,$0716B8), the 10-frame wait at$0716E8, the 40-frame restore at$071708andPal_VariableFadeToPal2have no ops.
Event_DeVarsDefeated ($07175A) and Event_SaLewsDefeated ($071822)
- Op 2's
Wait 40, after aFadeOut, stands for the first 40-framePal_IncreaseToneloop ($071772/$07183A). That loop brightens rather than fades and runs no map updates. - The second 40-frame tone loop (
$0717A8/$071870) and the 40-frame restore after the barrier sound ($071808/$0718CC) have no ops. - The 10-frame
DoMainUpdatesLoop($0717F8/$0718BC) is recorded by op 3'sObjectAnimation(frames: 10) but doesn't block.
Cutscene_ProfoundDarkness ($078D30)
- Op 12's
Wait 600stands forloc_78ECE's 600 passes ($078ED4). Each pass runsMapUpdate_TheEdgePart2_PalLine2,loc_55D78and the random palette-line-2 white flashes withSFXID_Tandle, with noRunMapUpdates. No op records the flashes.
Not a wait, found on the way
Cutscene_Reunion:Event_MoveObjectStatic($078AAA) blocks until object$FFFFC340reaches($1F0,$1B0), updating objects and the map. Op 2'sSetObjectDestinationdoesn't block. This is #470's motion-loop clause.
Acceptance
- Each listed retail wait is a native wait of the right length and loop kind, or its omission is recorded in
docs/source-notes/README.mdwith a reason. - Its census row moves from
Missing/Recorded/defect to a plainWaitorWithinclaim.cargo test -p psiv-core --lib wait_censuspasses with the US image. - A scene test drives each repaired scene's timing.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 43m
- Merged PRs (30d)
- 288
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TusanHomichi/PSIV
-
priority: medium ready
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TusanHomichi/PSIV#646 ·
Maintainers usually reply within 1 day
-
later
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TusanHomichi/PSIV#504 ·
Maintainers usually reply within 1 day
-
later priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TusanHomichi/PSIV#462 ·
Maintainers usually reply within 1 day
-
later priority: medium
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TusanHomichi/PSIV#446 ·
Maintainers usually reply within 1 day
-
good first issue ready tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TusanHomichi/PSIV#146 ·
Maintainers usually reply within 1 day
All issues in TusanHomichi/PSIV
Similar issues
-
ライブラリを追加Openpriority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#13015 ·
Maintainers usually reply within 1 day
-
needs-review
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UCS-Care-Group/mailcraft#1429 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
area:tui bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
agent-of-empires/agent-of-empires#5705 · 1 comment ·
Maintainers usually reply within 1 day
-
bug lab rust-mcp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day