SA SCM: Difference between revisions

8 bytes removed ,  21 September 2010
why should this be deleted?
(Removed speedy deletion template [Reason: The reason for speedy deletion is not obvious to me.])
(why should this be deleted?)
Line 1: Line 1:
{{Prod}}
A scm file is a binary file with certain structure. The common information about what this file is for can be found [[Mission Scripting (Overview)|here]]. The scm file structure looks like the following:
A scm file is a binary file with certain structure. The common information about what this file is for can be found [[Mission_Scripting_(Overview)|here]]. The scm file structure looks like the following:
 
====(02 00 01)h + 32 bit int Jump to second segment
====(02 00 01)h + 32 bit int Jump to second segment====
byte Padding
byte Padding
  (Global vars)              Space for variable saving
  (Global vars)              Space for variable saving
Line 13: Line 13:
   32 bit int                Largest mission size
   32 bit int                Largest mission size
   32 bit int                Number of missions
   32 bit int                Number of missions
   32 bit int                Highest number of locals used in mission/exernal
   32 bit int                Highest number of locals used in mission/external
   (mission addresses)        32 bit addresses * number of missions
   (mission addresses)        32 bit addresses * number of missions
(02 00 01)h + 32 bit int Jump to fifth segment
(02 00 01)h + 32 bit int Jump to fifth segment
Line 31: Line 31:
   32 bit int                (Unused)
   32 bit int                (Unused)
(MAIN code) MAIN section, equal to size defined earlier
(MAIN code) MAIN section, equal to size defined earlier
(mission code) The mission data, missions stored at offsets defined earlier====
(mission code) The mission data, missions stored at offsets defined earlier


{{stub}}
{{stub}}


{{fdl}}
{{fdl}}
[[Category:Mission Script]]
[[Category:Mission Script]]
[[Category:File Formats]]
[[Category:File Formats]]
Members, Alumni
24,921

edits