TASEmulators / TASEmulators/BizHawk

[F.Rq.] Memory copy/mirror finder

Open
#3,739 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Ext. tool: Future tool Request: Feature/Enhancement Tool: Hex Editor Tool: RAM Search
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

Not to be confused with #3738. This is about "manual" copies of structs that a game might use for various reasons. It may happen that one copy is the "real" one and all pokes/freezes should be directed at it, and I'm suggesting that we add a way to search for apparent copies of a known area in memory.
As it stands, you can use RAM Search for this, but only up to the selected word size, and you can't reference the known copy by address, you need to copy its value(s). You can also "Find" in the Hex Editor, but again can't reference a byte string whose location is known (see also #1653).

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading the RAM Search and Hex Editor functionality described in the issue, including the related issue #1653. Define how a known address and memory range should be used to find apparent copies beyond the selected word size, and confirm that the result can identify the copy to target. Done means the proposed search is usable for manual struct mirrors without requiring copied values.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.