Hi,

I am using leaderboards to show some deaths of units, e.g. "ID:366" (=Queen's Nest I believe).

But, if I try to compile these in Trigedit, it claims they are not units and therefore refuses to save. This means everytime I want to make a change to my triggers which requires a text macro, I have to delete the leaderboards and write them in Classic trigedit all over again.

Any way around this?

Wait until jjf finishes his editor. (that is a "no".)
Well, no for triggering with ScmDraft, that is. There's certain trigger editors that can integrate their generated triggers right into a map. Though I'm too out of touch to point you towards a specific one.

Alternatively never have the leaderboard triggers in your map and just add them for release candidates.

Is the source code open for SCMDraft? I don't know C or whatever language it is, but it's a simple matter of adding strings like "ID: x" where x is some integer. That'd be a few lines of code to add....

No, the author of ScmDraft has consistently declined the release of its source code to anyone for various (read: dubious) reasons.

It's still possible to edit by reverse engineering the binary, but trying to add code that way is a nightmare, even if you're competent with C. You'll just have to deal with its shortcomings and various bugs.

CHKDraft's text triggers are in complete working condition http://www.staredit.net/files/2741/, uses the same format as SCMDraft's, accepts numbers and ID notation for all fields.

Using the Classic editor in SCMDraft allows for the flawless use of Unit IDs and Memory, however Trigedit wasn't made to fully support both as they still cause issues now/then.

So either use jj's editor for triggers or use classic to handpunch them. In the event that you need them for mass triggering... sorry

Is there no flag I can set which says ignore compiler errors? I know this can be done in Warcraft 3 for JASS, because if you did have an actual error the map will refuse to load.

nope, not in either compiler, lotsa work for little-to-no end (ignoring some extranee punctuation might be useful but ignoring anything wrong with the actual triggers/conditions/actions/fields would be more confusing than helpful)