ASM Code in comparison

If copying DG0.SCN over DG2.SCN fixes the problem, then the issue isn't in the game's code at all. You should be looking at these files and comparing them to one another.

That's what I thought at first.
And believe me I tried but here is the issue:

DG0(UK) has a sice of 784 KB while DG2 (GERMAN) has a sice of 788 either way there is already this difference which I guess results in the fact that in the translating process the translation just takes more space (can't find another reason since they use the same font)

Now while browsing through differences I found 134487 differences. Obviously since one is english and the other is german that bytes are different.lol

Now see, without finding the pointer to that particular scene I can't find out why it is going wrong in the first place.
The Table File helps to differenciate between text and what is believed to be pointers and such but still there are too many differences.
I tried replacing data before and after the scene but the issue seems to be stored somewhere different.

I believe that a reference is just missing because the text is there but the part where text is parsed to NPC (or something l ike that) isn't happening in the PAl Version.

That's why I thought browsing through the code at that scene and finding the differences might help to understand why it's working in NTSC and even UK and not in the PAL.

That was my plan but according to your post I should try a different approach?

Well, yeah, they won't be the same size. I think you'll find the Japanese version of the SCN file will take up much less space, in fact.

Do the files actually contain script pointers? I suspect you'll find that they do, if you look closely. They'll probably be relative to the start of the file, or the address it gets loaded to in memory.

What I'm saying here is this: your first priority should be to work out the pointer block, then use a tool like Cartographer (preferably Cartographer) to extract the script from both. As long as the pointers are in the same order, you'll end up with two script files you can compare pointer-by-pointer. If there's non-text data (i.e. event code) in there, it'll dump that to the files, too. This is a good thing.

Also, I'd like a bit more clarification. You say you figured out a (kludgy) way to fix the PAL bug; does copying DG0.SCN over DG2.SCN fix it, or was it something else?

Well, yeah, they won't be the same size. I think you'll find the Japanese version of the SCN file will take up much less space, in fact.

Do the files actually contain script pointers? I suspect you'll find that they do, if you look closely. They'll probably be relative to the start of the file, or the address it gets loaded to in memory.

What I'm saying here is this: your first priority should be to work out the pointer block, then use a tool like Cartographer (preferably Cartographer) to extract the script from both. As long as the pointers are in the same order, you'll end up with two script files you can compare pointer-by-pointer. If there's non-text data (i.e. event code) in there, it'll dump that to the files, too. This is a good thing.

Also, I'd like a bit more clarification. You say you figured out a (kludgy) way to fix the PAL bug; does copying DG0.SCN over DG2.SCN fix it, or was it something else?

I just don't know how to figure out the pointers. Every time I try to set breakpoints in PsX the game just freezes but nothing else happens.
Can you give me a small instruction how I would figure out the pointers? I tried according to a doccumentary here but it didn't work out.

Also: Yeah copying DG0.SCN over DG2.SCN does fix the bug.
Since DG0 is a bit smaller you end up with 4 KB 0s but other than that the game seems to work just fine and also the bug is gone then. So yes.

You shouldn't be worried about the file size so much as the contents.

Now, I'm assuming you've opened the file in a hex editor and can see the text, but there's a lot of stuff mixed in that's not text, right? Those are control codes, event codes and such. They are something completely different from ASM code. The short version is, they should be identical between the English and German versions, except for the messed-up event code responsible for the PAL bug.

There should also be pointers in there. Odds are they're file-relative, and the start or end of the file should be pretty much dedicated to them. A sequence of 32-bit little-endian numbers, I imagine.

Random idea: can you provide me the file and let me have a look? (Does the game use non-ASCII encoding, BTW? 'Cause if it doesn't use ASCII, then I'm gonna need your table, too.)

Here as requested the files and the table.
http://www.sendspace.com/file/l5z4hf

Oh and I see I didn't know that they are completely different from ASM code.
For the pointers as I said I'm pretty sure they must be in there too (If they weren't replacing the file would mess things upp wouldn't it?)
But no clue how to find them.

Thanks in advance.