TASEmulators / TASEmulators/BizHawk

Add read/write monitoring to RAMsearch/RAMwatch!

Open
#154 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Request: Feature/Enhancement Tool: Hex Editor Tool: RAM Watch Waiting on dev consensus
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

In the popular memory scanner utility Cheat Engine you can right click an entry 
in your address list and click on "Find out what accesses this address"/"Find 
out what write to this address" to have it track all reads/writes to the 
address.

Something similar to this would be very useful for TASing in bizhawk. For 
example it would allow one to quickly find whole structures of related values 
with some knowledge of assembly. Being able to replace the respective assembly 
code by code that does nothing (also something CE can do) would vastly help 
with reverse-engineering things in a game too.

Original issue reported on code.google.com by james.su...@yahoo.de on 11 Apr 2014 at 3:57

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 locating the RAMsearch and RAMwatch tools mentioned in the issue and read how their existing address-list workflows operate. Define the scope for tracking reads and writes, then determine how assembly can be replaced with no-op code. Done means both monitoring actions and the requested code-replacement workflow are implemented and validated.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools, reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.