Actually I just changed "greater than or equal to" to "greater than" (in "stop processing possible mission filenames when number is greater than or equal to 99"). Your "so much work" was simply changing 2 bytes (one for GDI, one for Nod) which I had found and identified ages ago.
I could upgrade the actual number to 127, but I think that's kinda messy. I can't go beyond that because the mission number in C&C is stored in a single byte, which is apparently seen as signed.
And yes, it always annoyed me that the last 2-character number wasn't available, so I fixed it

As for the b and c, not sure. It uses the standard mission name function. It looks really interesting... from the looks of it, if I can figure out exactly which parameters that function gets, I could probably make it allow 10 missions for every mission number. That's (eg. SCG70) EA EB EC ED EL WA WB WC WD WL

if Hyper happens to read this... the address is 00452300
This post has been edited by Nyerguds: Sep 19 2008, 12:35 AM