Rust pack retirement: preserve overworld and map-patch checks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 12/100
Research direction
Start with the existing Python tests test_overworld.py and test_map_patches.py, which define the checks to carry over into the owning Rust modules. The issue requires the palette pause to be lifted first and a local Phantasy Star IV ROM, so confirm both before starting. Done means the focused overworld and patch tests pass against the ROM, with Python and full-pack parity retained and failures shown for bad page addressing and patch application.
Written by the indexing model from the issue text.
Description
Child of https://github.com/TusanHomichi/PSIV/issues/115. Finish only this task in one fresh session and one PR. The parent's original authorization boundaries still apply; this child grants no additional authority. Do not read earlier sessions' transcripts.
After the palette pause is lifted, preserve checks from test_overworld.py and test_map_patches.py in the owning Rust modules. Reuse the patch tests already present. Keep this PR to extraction, paged layouts and patch output, without adding scene fidelity work. List every coverage disposition. Retain Python and parity; keep ROM-derived evidence local.
Verification: Run focused overworld and patch tests with the local ROM and full-pack parity. Demonstrate failures for incorrect page addressing and patch application.
If this is too big, publish any progress, split it with proj split FILE (a JSON array of title/body/check tasks), then end the session. Wait for the PR to land before declaring this task done.
- 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
-
bug lab rust-mcp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:cli good first issue help wanted needs translation priority:P2 type:documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
SpecterAoD/pqkeep#226 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
haowjy/mars-agents#381 ·
Maintainers usually reply within 1 day
-
[Bug]: opencode_go chat route drops reasoning_effort (even 'none'), while the same endpoint honors it via custom_llm_provider=openaiPossibly taken @arvindkumar-ship-it claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
BerriAI/litellm#51871 · 1 comment ·
Maintainers usually reply within 1 day
-
comp-formats
Difficulty 2/5 Half a day Newbie friendliness 64/100
ClickHouse/ClickHouse#131694 ·
Maintainers usually reply within 1 day