SCMDraft is awesome. After the new update, I like it even more. Trigedit is quite possibly the best way to handle triggers, and it still has room for improvement. I want to simply organize my triggers so that all of P1's triggers are first, then P2, etc..., then force 1, then all players. Is it possible to get a text editor that might have that type of capability? Or, is there a program that will reorganize the triggers based on who they belong to?
I might be able to throw together a program for you that can do that.
However, how would I handle triggers with multiple players?
I was thinking that multiple players would just come first, with just ascending order
P1, P2, P4, P5
P1, P4, P5, P7, P8
P2, P3, P4
Force1, Force2, Force4
Unless you can think of a better way, this would make at least my life a whole lot easier when making maps via the text editor.
You can use the classic trigedit and then modify the trigger the way you want.
he's talking about how triggers are organized in TrigEdit, not about how to make triggers.
It would make more sense (and probably be easier to code) to have all triggers that are owned by P1 at the top (includes triggers owned by P1 and P2 and ...), then all triggers by P2 that were not listed in the P1 triggers yet and so on...
Then force, then all players.
But actually it does make more sense to organize your triggers independant from the trigger owners, anyway. For example all the triggers that deal with some selection system in one block and so on. This does reqire you to save your triggers as text files, though. At least for TrigEdit.
Why not have it so the user can define the order...
(Like bookmarks in webbrowsers)
The reason I suggested using the multiple trigger owners at the top is because personally I don't like having two different people share triggers. Chances are, you can just make 2 identical triggers, and not dramatically increase the map size. Anyway, the ideal would definitely be to allow the user to choose.
Of course, alphabetizing the trigger owner might just be the simplest way, and would work for anyone's purposes.
Why not make it customizable...........
Why not keep the "source code"... And btw, Cole, customizability was already suggested...
And btw, Cole, customizability was already suggested...
Then what on earth is there an argument about?
lly I don't like having two different people share triggers. Chances are, you can just make 2 identical triggers, and not dramatically increase the map size. Anyway, the ideal would definitely be to allow the user to choose.
Each trigger will use up 2400 bytes. If your map has a ton of triggers that can add up. However I wouldn't worry so much about that... Simply it is more efficient in "mapping speed" to create one trigger for 6 players than 6 triggers for 6 players.
Most of the time, if you want a trigger to act for players 1-5, they happen to all be on the same force. Maybe that's just me though.