Staredit Network

I think I did when I used to map...

It sort of depended on the project, I guess. If I was making a simple melee style map with the only triggers being ones for AI scripts, there's really no point to comment those.

I usually comment only whole triggers blocks making headers from top triggers and set rest of block's triggers(except of the ones where optional "sub block" starts ) as null string so that they look more clear. I also want to have headers easy visible. That is example what I do:


-----------------------------
<--- Messages index --->
-----------------------------
wraith messages:
null
null
...
battlecruiser messages:
null
null
...
special messages:
null
null
...

It makes life a lot easier! However I usually work in SCXE that unlike SCM don't spoil text and I make in SCM only thinhgs that I can't achieve in SCXE.

I've never used comments in my life. I find I can usually understand what I meant a given trigger to do within a couple seconds just by looking at it, without need for comments. If I was going to use them, it would only be to make the triggers shorter, rather than actually describe the triggers. It makes it harder for other people to understand my maps if they want to edit them, but I suppose that's just a necessary evil. Besides, at least I tend to group triggers according to function, so anyone familiar with triggers should be able to decipher my maps pretty quickly.

Yeah Comments Are the best They Are Really Better Then Even Having To Protect Your Map.Cause Lets Say You Use SF And SCM Draft You Can Have Tons Of Comments Then SF Protect So If Some Idoit Unprotects For A Reason Like Trying To Steal Your Map They Might Be Able to Hack It But The Comments Confuse Them Thats Y I use Comments.But Dont Get Me Wrong Osmap is usful if you protect your map to early or u need to see a certain trigger and just see one trigger.Thats Only Thing I Like About It But I Hate It Cause People Steal Maps With It

i guess you've never made a 2k trigger map before...

I thought triggers maxed out at something like 256. o.O And no, the largest maps I've made would have had maybe something like 100 triggers.

triggers max out at 1 million something i believe.

Considering the max (map-)file size of 4 Gigs and the size of a trigger (2400 bytes), you can have more than 1.5 million triggers...

If you combine TrigEdit with Notepad or any other text editor, you can comment similar to the way you do it in programming. You have to keep a text file with the triggers+comments, though, and it's pretty uncomfortable to combine this with other trigger editing methods.

On topic: I usually don't comment in SCMD2, because I mostly use SCMD2 for mass triggering in TrigEdit. Comments (the action) are almost completely invisible there.
I add comments if I want others to be able to understand my triggers, though.

I dont comment because I never make mistakes so I never need to fix anything

j/k I use comments just for organization

Heh, screw comments. I've switched over almost completely to text-based triggers, so comments (at least as the trigger actions) aren't useful to me anymore.

What I do instead is physically break up my triggers into multiple text files based on function; not simply who owns them, like with normal editors. To get them back into the map I use a macro with my text program to "compile" them into a single file so I can copy it back. It's a bit crude, but my old programs for doing custom triggers that I used to have stopped working right so I just go with that method. Beats the hell out of wasting strings and scrolling through huge trigger lists.

do you mean your own style of staredit or you mean starforge trigger edit if so comments are still more helpful on starforge i no this because i use starforge trigger edit for tune ups

No I don't use comments at all... at least not the trigger kinds. I actually physically break up each group of triggers into seperate files, and treat them like I would source code for programming. I can add in non-trigger comments in the text usually, like with trigedit by using // before each comment line.

I tend to avoid starforge for non-terrain stuff as it's given me problems in the past, however I'm going to try experimenting some more with its trigger editor more than just superficially soon. Originally I used GUEdit for text-based triggers, but now I use SCMDraft 2's trigedit and it seems to work fine (except for a few bugs with the way triggers are compiled back into the map and of course the string recycling preventing backwards compatability).

I bet you'll like my editor once it's done, Tux You won't have to work with different files anymore; they are packed into the .mpq, and thus a lot easier to access Gets a little closer to the compiler-style

The only problem that I can think of for original TrigEdit is null strings get referred to string 1 instead of 0.

Now I almost always use comments in mu triggers. Much more easy to find what to edit later on

true it does make it easier plus as tux says Scm draft makes triggers alot easier 2 execpt a few bugs so now i just use SCM Draft 2 and xtra editor SF is not really useful to me