Decreased, increased, increased by and decreased by search types are innacurate / broken about ntrremotedebugger HOT 4 CLOSED

These were functional for 4 byte last I checked, I'm not sure when they broke. Not sure when I'd be able to investigate but I'd probably just try searching for character X/Y/Z position in FFEX as I have a good way to determine where the character struct is in memory for it. That'll let me knock out both float/double and increased/decreased at the same time.

from ntrremotedebugger.

Well, actually, I was trying to search coordinates from Sticker Star and this is how I had doubts with increased/decreased because the scans didn't made sense until I tried different/same which did worked (and luckily, it narrowed it down enough so that I had an idea of the Z position when I was hugging a wall in a certain map so I could narrow it down further).

If it helps, I got that doubt on 8.5.

from ntrremotedebugger.

Increased/Decreased are reversed in the code (whoops). Increased By/Decreased By only work for Integers currently at a glance at the code, I'm not sure if they're working properly yet, testing now.

from ntrremotedebugger.

Increased By/Decreased By were also reversed in the code and I have fixed all 4 options locally as far as being reversed. I'm still investigating how to fix the By options to work with other data types. May be a difficult problem to fix due to the nature of floating point numbers.
To clarify, the By options work for 1/2/4/8 bytes currently. Technically they should also work for Float/Double but they round the difference to the nearest whole number before checking against the input value (which is also rounded to the nearest whole number).

from ntrremotedebugger.