hmm. I need to either start building documentation about which of my 13 current Ghidra installs have which extensions installed, or I need to set up a ghidra build environment and commit to maintaining a One True Ghidra environment with all the extensions
I keep having the problem of "now which one of these has that PSX loader installed in it?"
(the answer was ghidra 10.2.3 if you even care)
ugh. I'm gonna have to find the font for this game, not for the usual reasons (death generators), but because I'm trying to find the code powering a specific screen (The character viewer) but the text from it doesn't show up in a strings search.
because it's not ASCII. ;_;

it might be full-width latin characters. possibly encoded in shift-jis.

sadly ghidra doesn't know how to find that

maybe I can write a program to search for full-width characters in common encodings

Turns out the text IS in ascii, it's just in a datafile and not the executable.

so that doesn't help me

it was a good idea of them to put all the strings in a datafile instead of the executable! really handy for localization.

oh, this game was only ever released in japan? huh

oh I think this game is doing tricksy shit.
I think it's dynamically loading code out of datafiles and launching them. So the main executable is just the loader and archive-parser

why the heck does the PS1 have a "NoFunction" syscall?

I know about NOPs, by why a NOP syscall?

it has been zero days since I crashed an emulator

@foone Tired: Crashing an emulator by overpowering it

Wired: Crashing an emulator like you crash a party

@textfiles @foone my favourite was crashing an emulator by doing absolutely nothing!

(gameboy emulator, i turned halt on with vblanks turned off, instead relying on the keypad interrupt. this crashed several badly programmed emulators which relied on the vblank interrupt apparantly to refresh the host event loop. i crashed the emulator by putting it in the deep freezer)