Report, edit, etc...Posted by Staredit.Net Essence on 2005-12-30 at 21:57:10
Does anyone know how to use TriggerCom? I'm trying to use it in conjunction with either vanilla Staredit or possibly SCXE. It works BEAUTIFULLY except that in the text file, all the location names are (no location), and if I put in a real location name then when I port it back, all the location names in Staredit/SCXE are (no location).
I can't find documentation for this tool ANYWHERE on the internet, but it seems like exactly what I need
.
Alternately, does anyone know the format of the .trg files? I can maybe make a similar program to TriggerCom.
TriggerCom, if it helps your memory, is the one with "trg2text" and "text2trg".
Thanks!
I can't find documentation for this tool ANYWHERE on the internet, but it seems like exactly what I need
.Alternately, does anyone know the format of the .trg files? I can maybe make a similar program to TriggerCom.
TriggerCom, if it helps your memory, is the one with "trg2text" and "text2trg".
Thanks!
Report, edit, etc...Posted by UED77 on 2005-12-31 at 03:13:45
Unfortunately, .trg files do not store location names, to avoid automatic association of the triggers with a different 'MRGN' (location) section. This way, by disabling references to locations entirely, the mapper will have to manually sift through them, ensuring accuracy.
To keep references to locations, you might wish to use SCMDraft's TrigEdit to handle triggers as plaintext.
The .trg file specs, courtesy of Heimdal:
See the CHK specs and the TRIG/MBRF specs for more information.
UED77
To keep references to locations, you might wish to use SCMDraft's TrigEdit to handle triggers as plaintext.
The .trg file specs, courtesy of Heimdal:
QUOTE
8-byte header: qw 0x98 6 0x00000018
For each trigger, the following:
{
2400-byte TRIG structure from CHK format
External data for preceding trigger, in order of actions:
For each action that uses a string, 2048 bytes of string data (null-terminated)
For each CUWP action, a unitproperties struct (see UPRP section of CHK)
}
For each trigger, the following:
{
2400-byte TRIG structure from CHK format
External data for preceding trigger, in order of actions:
For each action that uses a string, 2048 bytes of string data (null-terminated)
For each CUWP action, a unitproperties struct (see UPRP section of CHK)
}
See the CHK specs and the TRIG/MBRF specs for more information.
UED77