- 0
Bug Report: "Copy as group search" assumes values are consecutive when used with utf-8 text and utf-16 text options
-
Similar Content
-
- 1 answer
- 1,312 views
-
- 2 answers
- 1,114 views
-
How to 'os.exit' it, while someone peek at searching value, when gg are searching values? 1 2
By nio04,
- 23 answers
- 8,291 views
-
- 4 answers
- 683 views
-
- 2 answers
- 644 views
-
Question
HorridModz
@EnybyHello, I am reporting a behavior that appears to be a bug in gameguardian.
It seems that the "Copy as group search", when used with "UTF-8" and "UTF-16", assumes that the values are consecutive, i.e. one byte apart. However, this is not always the case, causing group searches to sometimes fail.
This is best illustrated by examples: Let's search the string "abc" in UTF-8 and save the first 3 results, but leave out the second one:
Now, we have two results: 97 byte, representing the character "a", and 99, representing the character "c". These results are a byte apart - so they do not directly form the string "ac" and would not be searchable as ":ac"; rather, they would be searchable by a group search that accounts for the byte in between: 97B;0~~0B;99B::3. However, the Copy as Group Search function, when I select UTF-8, gives ":ac". This is not the right group search and seems to be a bug.
In order to show why this is wrong, here is the situation where I discovered the bug. I had a script that writes a string to memory, like this:
If I run this script, I get the string written in consecutive byte values. I use Copy as Group Search for UTF-8, and it gives me the correct search: ":Here is my special string!".
But now let's revert what we just did by refreshing the game, change the address spacing to every 2 bytes, so the string is no longer consecutive, and copy it as a group search again:
We copy it as group search again, and get the exact same thing: ":Here is my special string!". However, now that the addresses are 2 bytes apart, this is wrong and will not work. If we try to search it, nothing comes up.
Edited by HorridModzSo, this is definitely not working right. I'm pretty sure that it's a bug. My suggestion for fixing this would simply be displaying an error message if the addresses were not consecutive, like this: "UTF-8 [or UTF-16] group search only works for consecutive addresses. Please use a different type of group search."
If there's any other information anyone would like, feel free to ask.
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now