If SCMDraft is the only editor you use, all you need to do is give the strings the same name, and SCMDraft will recycle the string for you. A common tactic regarding trigger comments is to have a comment-trigger (a trigger that just holds a Comment action in it) that describes what a group of triggers is about (e.g., "Location Grid Scanning"), and all related triggers below it have a comment that's just a single space in it.

Or don't use comments at all. Especially with the ability to add notes to the text triggers, it's a really unnecessary and inefficient practice.

If SCMDraft is the only editor you use, all you need to do is give the strings the same name, and SCMDraft will recycle the string for you. A common tactic regarding trigger comments is to have a comment-trigger (a trigger that just holds a Comment action in it) that describes what a group of triggers is about (e.g., "Location Grid Scanning"), and all related triggers below it have a comment that's just a single space in it.

He just means adding comments into the text triggers. Which does work, but I use the classic trigedit as the primary point for editing triggers; I only use text triggers when I need to do tedious stuff or big editing sessions where I need to copy and paste a lot.

This was my biggest request for Scmdraft- for pseudo comments that weren't stored in the map itself and the ability to organize triggers in a tree structure.

But I don't use classic trigedit anymore.

"STR " section

Note: Required for Melee game type This section contains all the strings in the map. Note: This section can contain more then 1024 strings and will work in Starcraft

2 byte integer: Number of strings in the section
(# of strings) 2 byte integers: 1 integer for each string specifying the offset (the spot where the string starts in the section from the start of it).
Strings: After the offsets, this is where every string in the map goes, one after another. Each one is terminated by a null character.

Every trigger has 16 of the following format, even if only one condition is used. See the appendix for information on which items are used for what conditions.

4 byte long: Location number for the condition (1 based)
4 byte long: Group (0 based) that the condition applies to
4 byte long: Qualified number (how many/resource amount)
2 byte integer: Unit ID condition applies to
1 byte: Comparison type/switch state
1 byte: Condition byte (see the appendix)
1 byte: Resource type/score type/switch number
1 byte: Flags
Bit 0 - Unknown/unused
Bit 1 - Enabled flag. If on, the trigger action/condition is disabled/ignored
Bit 2 - Always display flag.
Bit 3 - Unit properties is used. Unnecessary (Note: This is uses in *.trg files).
Bit 4 - Unit type is used. May not be necessary?
Bit 5 - If on, the unit ID is used. Unnecessary.
Bit 6-7 - Unknown/unused
2 bytes: Used internally by starcraft (number of which condition to process next, and maybe more?)

Immediately following the 16 conditions, there are 64 actions. There will always be 64 of the following structure, even if some of them are unused.

4 byte long: 'Source' or only location (#1 based)
4 byte long: String number for trigger text
4 byte long: String number of. WAV file
4 byte long: Seconds/milliseconds of time
4 byte long: First, or only group/player affected.
4 byte long: Second group affected, destination location (1-based), CUWP #, number, AI script, switch
2 byte integer: Unit/score/resource type/alliance status
1 byte: Action byte. See appendix.
1 byte: Number of units/switch action/unit order/modify type. 0 specifies all units.
1 byte: Flags
Bit 0 - Unknown/unused
Bit 1 - Enabled flag. If on, the trigger action/condition is disabled
Bit 2 - Always display flag.
Bit 3 - Unit properties is used. Staredit uses this for *.trg files.
Bit 4 - Unit type is used
Bit 5 - If on, the unit ID is used. Unnecessary.
Bit 6-7 - Unknown/unused
3 bytes: Used internally by starcraft (number of which action to process next, and maybe more?)

Following the 16 conditions and 64 actions, every trigger also has this structure

4 bytes: Used internally by starcraft (unknown usage. may be used to check if the trigger is "finished", ie no preserve trigger and the trigger has already run)
28 bytes: 1 byte for each player in the players/groups list (except for the last one) (see appendix).
00 - Trigger is not executed for player
01 - Trigger is executed for player

There's a large number of unknown/unused bits in triggers which could easily be used by an editor in order to make custom trigger actions/conditions. This would be useful for EUDs with the Memory condition, so that it doesn't mess up when you use deaths of terran marine.