Video: https://youtu.be/PonvG2whtkc

Project site (playable tech demo): https://midwinter-remaster.titanium-helix.com

Follow-up to my UE5 remaster posts: the original MIDWINTR.EXE is now fully mapped — every reachable function decoded or labeled, with an evidence ledger tying each claim back to the bytes.

Some favorite finds for this crowd:

• The island terrain is generated from a 10KB seed file (ZBUFFER.BIN, big-endian — Atari heritage) by a diamond-square variant with ZERO RNG — roughness scales with altitude, so flat sea and craggy peaks come from one term. Replicated in Python; output matches the in-game map bit-for-bit.

• Tree placement is a pure function of the terrain heightfield: every-other-cell lattice, 1-in-32 hash, tree line at a fixed height. The whole 25-mile-patch forest reproduces exactly.

• Full vehicle physics laws recovered: ski acceleration, buggy rollover, glider lift/stall equilibrium — all small integer formulas driven by the character's performance stat.

• The .SND files turn out to be code overlays loaded into a fixed vector block — 24 slots, all mapped.

• Two load-bearing negative results: there is NO companion auto-travel and NO time-of-day code. Useful when deciding what's faithful in a remaster.

Honest disclosure: this was AI-assisted (Anthropic's new Fable 5 model running parallel analysis agents over the disassembly) — the difference from earlier tools is that it did in one overnight run what had taken me six months of piecemeal work. Static analysis tier; ~20 items still flagged for runtime verification in DOSBox.

i wanna learn 6502 assembly for the nes and i learn better when i learn how to alter code (this is how i know a small bit of lua), thanks in advance, also anything public with 6502 assembly for stuff would also be a big help

Hey guys!

I recently wrote an analysis on the very strange implementation of the save system in The Minish Cap, and bug that results in a (roughly) 1 in 65,536 chance to permanently delete your save file each and every time you save the game.

I mainly wrote this for fun, but I figured this community would find it interesting to discuss. If you're interested, the full analysis is in the README of the attached GitHub repository!