Zorg

Ah I see, this is more the latter. Game Guardian allows there being a maximum defined gap between the numbers and possibly doesn't enforce them to be in-order. That is...

If you have the address and number of bytes to write to for the instruction, maybe this would help: ```python originalBytes = debug.readBytes(ADDRESS, SIZE) debug.writeBytes(ADDRESS, b'\x90' * SIZE) #nop instruction...

It's not possible. Currently you have to do everything from a script, figure out another way to dynamically locate the address (via editing the address's formula), do something in between...

Only badly implemented games force fullscreen and not allow command-tabbing out :(.

It's most likely the result of the game capturing the display. A remote version would be useful for this; maybe some day..

Sounds like a good idea in the future. You can simplify your current workflow if you just add a 8-bit string, and alter its address in []'s.

But this convenience doesn't help much if the pointer is not direct to what you want, so it may not be that much worth adding. Possibly an easier way to...

Rather than additional fields or columns, I think referencing another variable should just re-use the current address formula field when you edit a variable, which already supports pointers and basic...

I lied. Initial work is done on the [address-reference](https://github.com/zorgiepoo/Bit-Slicer/tree/address-reference) branch. Here's a [build (1.7.9a1)](https://zgcoder.net/software/bitslicer/dist/alpha/Bit_Slicer_1.7.9a1.zip) to play around with. Consider it alpha quality. When you try to edit an address of...

I'm not really sure (re)naming the tags is that important for the effort that may be involved.