Alright,
Hmm, it still seems like line breaks inside of a string should be converted to the linebreak character SCM Draft uses.
I personally don't hold adhere to the opinion. Most general programming languages don't allow linebreaks inside of strings, neither does MT. I believe the code formatting and it's essence must not influence each other in any way.
Wormer, within 2 weeks I'll finish up doing small test maps and I'm going to begin work on my actual map, so I'd really appreciate it if you fixed up any bugs, or inconveniences, I don't mind doing workarounds, but if you're going to fix it, I'd rather you did it now, instead of me learning it one way then having it get fixed.
Okay Falk, there are no crucial bugs I know of. I'll try to fix any revealed essential bugs as fast as I can, though at the moment I don't mind fixing something which has admissible workarounds, namely 1) @AllPlayers not being acceptable as trigger owner (defining "FORCE AllPlayers = @F('All Players')" works perfect) and 2) defining local variables in loops (workaround is to introduce "IF @True THEN ... ENDIF" for the local scope).
Further, I am sorry Falky, but I really don't know when I am going to implement such new features as the customizable conditions and LOOP/IF-statements inside of triggers. Such changes will have extremely spontaneous nature, it might be done during the next month, during the next year or not be done ever, with all variants being equally feasible.
That way, my personal suggestion for you is to start the map and don't rely on the fickle circumstances. Look, if you accomplish the map with the features available and then a new feature will appear don't be upset - your map would be done at least, but if you'll wait for the new features you're very risking not to accomplish the map ever.
Well poiuy_qwert, this nifty thing with the defining the trigger before it's usage might sound nice and funny and everything, but what is it's real use in real triggering? I can't think
when and
why one would want to define some trigger before it's usage? As a side note, you can achieve the same effect defining a macros in MT.
Then, I personally don't like saving up a couple of words omitting keywords "Actions" and "Conditions". This makes triggers less visual which matters a lot in large projects.
So since Wormer has said he doesn't plan to fully support MacroTriggers anymore, is anyone interested in this?
I want to be clearly understood. I do support MT but I don't develop it at the moment.
Is there somewhere I can find the keywords etc. of SCMDraft triggers? Thats all i would really need to finish the project.
There is a list of actions and conditions coming with the SCMD distribution (the file "trigedit help.txt"). What else do you need?
Some.