okay, here is something i should have told you before since the beginning: i tested the script with quickbms_4gb_files.exe
i tried to investigate your problem by executing the one and only
quickbms.exe executable, and guess what the problem is actually much worse than anticipated.
simply put, the script will simply spazz out in there to the point it triggers unexpected bugs like these...
. 000003e0 get OFFSET 0x001165ef 4
. 000003e4 get SIZE 0x019e0004 4
. 000003e8 get NAME_OFF 0x000005a4 4
. 00000000 putarr OFFSET 0xe032f800 0:0
. 00000000 putarr TBL_ARCNUM 0x00000004 0:0
. 00000000 putarr STBL_DRAFT1 0xe1d0f804 0:0
. 00000000 putarr STBL_DRAFT2 0x00000008 0:0
. 00001e78 get NAME "movie\data22.pss" -1
. 019e0004 putvarc 0x00000000 1
i used my publicly-available siren.bms script as a reference for this kind of error.
as for *how* i'm going to fix this one... well, what i'm confident in saying is that i'm starting to get a clear idea of this now.