I accidentally built a tool to let you search a binary file in UTF-16, and the gimmick is that it searches in UTF-16 Big Endian and Little Endian at the same time.
-
I found a font through texture-dumping, but it's missing some characters that show up in the text, so... I think this is a different font.
-
mmm, nope found another piece of it. It's just a font engine that uses multiple font sources
-
I bet they've got some rich-text composing system where their text is saved as like (font1,'T'),(font2,'h'),(font2,'a'),(font2,'i'),... instead of 'Thailand'.
-
you know that "Oh god, he's going for the jukebox!" meme?
She's launched ghidra.
-
and I wrote a half-assed relative searcher. some possibilities show up in RAM
-
Graham Sutherland / Polynomialreplied to Foone🏳️⚧️ last edited by
@foone I should create a PR for that for Cheat Engine. like the pattern search but for value deltas.
-
Foone🏳️⚧️replied to Graham Sutherland / Polynomial last edited by
@gsuberland I've thought about it!
I haven't reinstalled Cheat Engine onto my new system yet, because the whole semi-free thing put me off, though
-
meh patching all of them in ram, before the line shows up? no change.
-
unless these fuckers are keeping text in texture ram, which I guess is possible
-
Graham Sutherland / Polynomialreplied to Foone🏳️⚧️ last edited by
@foone raster image, maybe?
-
Foone🏳️⚧️replied to Graham Sutherland / Polynomial last edited by
@gsuberland nah, I'd see it in the texture dump. There's definitely a font engine here, I just have no idea where any of its source text is
-
@foone or maybe they’re complete psychos and storing premade meshes with UVs pointing at the textures
-
@cinebox ewwwwwwwwwww
-
"v" is a python bytestring. Can you spot the typo in this code?
if v=='b?':
-
TGhGaGiGlGaGnGdG
read every other letter. I think I found it.
-
my code is now dynamically composing regexes so it can search multiple gigabytes of PS2 debris. It is slow and unknowable
-
@foone be careful you don't inadvertently summon any demons
-
@ashtardeza they are welcome to stay if they can help me hack PS2 games
-
I have found some parts of the script in memory, but it doesn't seem to do anything i I change them (I'm changing them while viewing the previous line).
So I'm guessing it's per-calculating texture coordinates early? it doesn't seem to revert my memory changes like it's overwriting them by reloading the source data
-
here's a handy trick for figure out what code writes the text in the game, if you can only find matches after it's been decoded:
save state before it appears. play forward until it does, search the text to find the memory address, then load state, set a memory watch on that address, then hit play
