GTAMP

@T.M. // commands that are known in some degree but not implemented yet: START_EXEC // not sure what these are. STOP_EXEC FOR_LOOP // AFAIK this cannot be compiled. DO_WHILE // probably same as above, never seen do-while loops. WHILE WHILE_EXEC AND OR IF // have no idea what this is, only IF_JUMP se...

T.M. wrote:Jaksaisitko vastata kysymykseeni? o.o (sen minkä laitoin suomeks...)

Oon, en.

@T.M. About the smaller .scr files: Mission scripts? Looking at bil_end.scr, the commands seem to start at 0x0C00 and continue to EOF. Last command is 0x0111 MISSIONEND. However, the pointer table doesn't fit in like in a main script though. Maybe requires some extra math due to how a mission is lin...

I noticed weird things: the first command (first pointer) is always something totally random. i noticed this when i added more support for OBJ_DATA, when i outputted the decompiled script, the first line was OBJ_DATA (with invalid parameter values) even when i didnt have any objects. so i looked wh...

Please see my code few pages before. It shows that there is 2 bytes of (unknown) header in the script data, maybe thats why you thought the offsets wrong. No, I think you are reading/interpreting the commandlines with an offset error of two bytes because you showed data starting with the command id...

I see I wasn't clear in my message. I did not mean only the MAP_ZONE_SET command, I meant all the way from file offset 2EE0 onwards. No, they are fine. 6600 = MAP_ZONE_SET, why would it change the next line anyways. The first two variables seem to be always the same: first is 16bit function command ...

MAP_ZONE gng1map = ( 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 ) MAP_ZONE gng2map = ( 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21 ) 6600 2900 0000 0A00 0B00 0C00 0D00 0E00 0F00 1000 1100 1200 1300 1400 0000 2900 6600 2A00 0000 0B00 0C00 0D00 0E00 0F00 1000 1100 1200 1300 1400 1500 0000 2A00 [/code]...