Author
Quote from: Ryusui on January 29, 2008, 02:44:16 pm
It's not out of left field. Data corruption is a useful tool for figuring out the workings of a game. Just change bytes at random and see if the game breaks in any interesting ways. ^_^
I think you might want to change the 2-byte value at 08 instead: i.e. "13 E3" (E313). 0C77 seems to be a control code: all of the other strings have an 0A77 in between them.
I think you might want to change the 2-byte value at 08 instead: i.e. "13 E3" (E313). 0C77 seems to be a control code: all of the other strings have an 0A77 in between them.
That 13 is prevalent in all the script files. 0A signifies a line break. The 77 I believe signifies the beginning of a new block of text.
The E3 0C seems to be the key to the whole problem. When I zeroed it out, the text played without doing the confirmation of auto-skip or the intro movie. When I played it all the way through and it got to the end of the script file's dialogue, it did the confirmation, and the intro movie, then crashed where it usually does. So I'm almost certain it's a pointer. The name of the intro movie is listed in the script file as well. I've tried adding the difference in size to the E3 0C value, but no dice there with about 10 different combinations.
Earlier, I had an idea to completely zero out the text and leave the headers and other data intact, while rewriting the dialogue. That didn't work either. 