The game tracks your position (x & y) each frame, so yeah you could technically do it with debug mode or watching certain addresses in the game's RAM. I never really did that in Melee though, I believe standardtoaster and Magus have. And potentially Kadano. For most general physics things, I am capable of calculating change in position per frame if I want to. I usually do not unless I'm investigating something specific, though.
I attempted it recently, but I ran into a problem I could make no sense of. Here’s what I did:
1. Dolphin debug mode, get one character on FD and search for codes.
2. Go to the right (hoping that x is stored as 0=left and 65535/whatever=right) for 1 frame and search for “greater than”
3. Repeat step 2 until I’m near the ledge
4. Turn left and keep walking for a few frames, then search for “less than”.
5. Repeat step 4 several times
6. Repeat 3 and 5 until only one adress remains
7. Repeat some more to eliminate false positives
The remaining adress only went away if I made an error (eg “greater than” when I went left), otherwise it always stayed there. So I induced that it had to be correct.
Now the problem was that when I looked at that adress at certain character positions and refreshed (I could not find a “constantly refresh” option, is there one?), the changes didn’t seem proportionate to each other at all. Also, when I clicked on what I understood as “force this value to this adress”, nothing happened in-game at all.
Got any idea what I need to do differently?
Also, @all: count me out of here for some time as I want to get started with some projects and I feel giving well-researched answers here draws from the same motivation pool within me as going meta. (The projects are mostly Melee-related, yes.)