Logging game events to text file

[seanmcnally]

The issue I think you're having is assuming this r23 + 0x0020 address is some sort of constant. It's not. The address number itself varies.

Yes, this was absolutely a misconception on my part.  I get it now, the address is always different but the equation to find the address stays the same.

You should see this instruction:
lwz r31, 0x008C (r3) # This is loading some value from dynamic memory into r3.

Is it loading from dynamic memory into r3 or into r31?  I'm still new to this but I thought the destination register came first, which would mean it's loading from dynamic memory into r31.

Since the original instruction loads the Item Value from r3 + 0x008C, we can conclude that....
Item Value is located at r3 + 0x008C
Item Number is located at r3 + 0x0090

So, if I'm understanding you correctly, we need to write ASM code that will figure out what value is at r3 + 0x008C, and store it in a register.  I'm guessing this will look something like the default instruction: 
lwz r31, 0x008C (r3)
Unless...that part is already happening, because it's the default instruction?  But it doesn't seem to be, since r31 doesn't seem to ever contain anything that looks like the item codes listed on that page. 

Anyway, after we figure out how to store it in a register, we have to write from that register to static memory using a stw command.  That's where the exception vector area you mentioned will come in, because we can safely store values in that portion of memory.  Am I right so far?

---

In regards to the question at the end, it doesn't seem that breakpoint has any consistent numerical values stored in registers when the breakpoint is hit.  27 and 29 seem to be consistently changing when we hit that breakpoint, but the values look something like 81247ebc, and do not repeat each time P1 uses an item.

I've just gotten out of the hospital so my mind may not be 100%.

I'm very sorry to hear this.  I wish you all the best and a swift recovery!