Oracle: fixture tape 10's three encounters

Open Beginner friendly
  • Is something wrong?
#124 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
godot, rust
Domain
game-dev, testing-qa

Research direction

Read docs/oracle/BATTLE_ORACLE_REPLAY.md and its “Open follow-ups” section, then run python3 -m oracle.fixture with --tape 10, --battle-first, and --battle-last plus the two logs to generate the three ROM-free battle fixtures. Commit those fixtures and run the replay test; done means all three fixtures are present and the replay test passes.

Written by the indexing model from the issue text.

Description

ready tooling

From docs/oracle/BATTLE_ORACLE_REPLAY.md, "Open follow-ups" 1. python3 -m oracle.fixture takes a new tape with --tape, --battle-first, --battle-last and the two logs, and needs no code change.

Tape 10's three encounters in a row add three battles on their own seed paths. They are also a chance at a second case like tape 07's: a battle whose first ability draw is zero, against the word the load left.

Acceptance:

  • Fixtures for tape 10's three battles are committed (ROM-free form).
  • The replay test passes over them.
Dominant language
Rust
Stars
1
Forks
0
Avg merge
8h 43m
Merged PRs (30d)
288

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 TusanHomichi/PSIV

All issues in TusanHomichi/PSIV

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.