Hex editor and search function issues

[iSharingan]

Hex editor fails to update the currently viewed values when re-opened (the 1.0 plg format plugin did so)

also 'cancel' during a search doesn't abort the search.

Also all of your Discord invites trigger a paygate to Nitro. Not sure why that's occurring - other than possibly because I'm already in the server it links to or maybe its an issue on Discord's end.

[Nanquitas]

Indeed, those issues are being addressed. I updated the invite link in the release page with a valid one, should help ^^'.

[iSharingan]

If you mean the link in #2, that also hits a Nitro paywall on PC. A second check on mobile seems to work.

On the specific issues: would it perchance be as simple of a fix as using some of the old code to restore functionality? Or has everthing been rewritten to the scale thats not feasable?

[Nanquitas]

I rewrote the HexEditor from scratch but I already fixed this particular issue. The current version use a cache to increase performances (it's more responsive) and I forgot to update the cache at menu open/close event.

[iSharingan]

other minor notes on codes/code types:

1. There's a painful lack of bitwise logical operations between 'data' and an offset, such as storing one value and performing an XOR with a non-static value (specific use: generating TSV in Pokemon games). My current XOR between two 16 bit values is about 250 lines long and breaks the two values into 32 total 8 bit values (having to abuse bitwise shifts to intentionally lose data, isolating specific bits), manually XOR pairs of results via If statements, then re-assembled into a new 16 bit value. It would be about 50% shorter but the below is also an issue.

2. Nested loops just break codes. They literally will not function when you nest two or more loops. Not sure if this was always the case or a slight error on the re-code. example of non-functioning code:

C0000000 0000004 // loop over 4 characters
C0000000 0000006 // change 6 stats on each character
[stat change]
[slot offset change]
D1000000 00000000 //start inner loop
[character offset change]
D1000000 00000000 //start outer loop

[ghost]

3gx ctrpf can't acccess locked .cro memory region, luma built-in cheat engine can't locate those addr either. those regions are accessable with old v0.4 plg+ntr. does luma have anny workaround on those mem regions? I saw some ppl in your playground discord channel said both ctrpf and luma have a workaround for those locked regions, but it doesn't seem to be the case..