Ohhh SCMDraft uses hexadecimal in the TBL formatting but I had used decimal (<13> and <10> should be <0D> and <0A>)! Since we have to change this we'll make it SCMDraft's preferred way with rn. Here is a fix for that and also includes the fix for the slash problem you are having. Go to line 258 which should be:

Also, SubtitleDisplay (Don't Always Display in SCMDraft) only shows the text when the user has the option "Show Subtitles" selected from the options menu. And then AlwaysDisplay is pretty straight forwards

but those double slashes in "rn" while seem to compile fine in SCMDraft, they aren't displaying correctly. Looks like we just need "rn" to compile as "rn". Can this be changed, but still keep the double slashes in the "" and "" formatting?[/quote]Ah my mistake again, didn't think about the rn when doing the slashes part. Go to line 258 which should be:

[quote name='bajadulce' post='9497' date='Mar 11 2010, 03:19 AM']Sorry I haven't been able to use this program to its fullest with all the macros etc, but it has been a huge help making the trigs for my mod as I don't like the way SCMDraft's trig editor is formated. And that MacroTrig program that I've read about seems really odd. Thnx so much for putting up with all of this.[/quote]I agree. And no problem, my pleasure.

Ah, its hard getting all the names correct since SCMDraft has weird names for some things and no reference list, so I generated my list with a little script and a few problems slipped through. Open Globals.py and go to lines 292-300 which should be:

[quote name='bajadulce' post='9500' date='Mar 11 2010, 01:14 PM']Not sure If I screwed up my version of global.py as this seems to have come up before in an earlier post, but Unit#26 Eduke Turret (Siege Mode) is compiling as "Duke Turret type 1" which seems to be Unit24 in SCMDraft or the (Tank Mode type1). SCMDraft isn't too helpful spotting this either as a lot of units share the same string! wtf?

Changes:* Updated readme* Fixed LeaderboardComputerPlayers (changed parameter from SETSWITCHSTATE to SETOTHERSTATE)* Fixed the default trigger file from "triggers.txt" to "triggers.protrg"* Fixed the convenience global ACTIONS so it's set to True* Fixed some TUNIT vs UNIT inconsistancies, and the definitions for conditions/actions with the PERCENT parameter type* Fixed multilines and slashes in string conversion* Fixed potential problem with script filenames starting with "protrg" (without quotes)* Fixed switches to be numbered the same as SCMDraft switches (1-256 instead of 0-255)* Fixed many unit names* Added support for compiling straight to .trg's, including GOT compatible .trg's (Note: StarEdit has problems loading recycled strings)* Added an optional mechanism to have stronger typed values for parameters (Explained more in the Coding section)* Added support for Extended Unit Deaths (EUD's) using the new stronger type mechanism (using EXTENDEDUNIT type)* Added DefaultString, which is set to an empty string (""), and all default AI scripts as Globals* Added @include preprocessor to iclude ProTRG files in others* Added better command line support* Added better support for Properties* Added the keyword argument "disabled" for conditions/actions* Added the possibility to collapse code in Notepad++ using #> and #< for the start and end* Added a list of the Globals and their values to reference.txt* All conditions and actions now inherit from the Condition and Action classes instead of directly from Raw* LOCATION id's are now 0 to 254 instead of 1 to 255 to conform with map editors default location names* If an error happens in your script it will now print all the current triggers in the Trigger list (if any) after printing the error traceback

I was wondering if you could add in the memory condition, which is a newer condition for Scmdraft used to make EUD conditions.

Here is a memory condition in standard scmdraft text format:

Memory(x, Comparison, y);

x needs to be able to be negative, and I don't think y will ever need to be. Of course, you don't really do too much low level data manipulation in Python anyways, so I guess it doesn't matter. x and y need to both be integers as well. The comparison is the usual At Least, At Most, Exactly.

The next paragraph goes into explaining the differences between the old EUD conditions and the new ones -- you can probably just not read it and still add in the memory condition to ProTrg just fine.

The traditional EUD condition, done in StarForge, had a general formula of: Address = Offset + (4*(player )) + (48*(unit:id)). The memory condition uses deaths of Terran Marine, which has a unit:id of 0, so the formula becomes a bit simpler where the only variable to solve for becomes player; here is the memory condition formula: Address = Offset + 4*Player + 48*0. So to solve for player, you pretty much just subtract your address from the death table minimum value (which is 5808996) then divide by (4*player#).

If you need anymore info let me know, though, I can't see why you would need anything other than the standard scmdraft text format for the condition