TASEmulators / TASEmulators/BizHawk

TAStudio must clear state cache after a hex edit / poke / freeze

Open
#4,570 12 comments 2 reactions 0 assignees View on GitHub

@YoshiRulz is already working on this.

Since Apr 24, 2026.

  • #4709 by @YoshiRulz — open
Tool: TAStudio Waiting on dev consensus
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

Mix between feature request and a bug report. The video here explains it better than a lengthy report:

https://www.youtube.com/watch?v=UjnguAbnapQ

Basically, modifying a value in memory should invalidate all cached states that have been stored ahead, just like changing an input would. This ensures the modification is properly stored if a re-record is made thereafter.

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 with the linked pull request #4709 and the issue's video to understand the existing TAStudio behavior around hex edits, pokes, freezes, and rerecording. Done means confirming that a memory modification invalidates cached future states so a subsequent rerecord preserves the modification.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.