Could someone tell me more about the famous "Never" condition which I've, so far, only seen used to use a trigger as a label?

Actually, each trigger with a "never" condition will never run ingame.
It use is kinda useless for normal mapping, but somene started an anti-unprotect map... just a trigger like this
Conditions:
-Always
-Never
Actions:
-End scenraio in Defeat

some map unprotector also compresses the map, and some compressors delete each "never" condition, which means if the map has been unprotected/compressed that it will be over just right after the start.

I use "never" only for in-triggers comments

I use Never for testing reasons... Like if one of my triggers is glitching, I throw might throw a Never condition in to shut it down and see what happens.

That is interesting... Are you sure? Isn't protectors compress the map? Also I always thought compressors delete whole triggers with enabled trigger condition "Never". It is really strange if they were selectively deleteing "Never" conditions changeing semantics of the map... You must have mixed up something.

He did. Unprotectors delete the whole trigger.

Never just returns false, as already said, it isn't useful otherwise, since unprotectors just delete the entire trigger, since it just wastes space, as it always returns false, so the trigger never runs.

But you could also use it protecting a map so if the trigger is deleted the map will not run.

Hey guys, why do you say unprotectors delete triggers with "Never" condition? It is protectors (compressors) which delete them! Unprotectors just read the map without the trigger...
And how can you use this? Since the trigger has "Never" conditions it never runs and it does not matter if it is deleted or not!.. Please say I am misunderstanding

Always
Never

Set Switch "Important"

You leave the Never condition unchecked.

Using "never" for protection purposes won't really be effective, because the person unprotecting the map can simply uncheck their unprotector's "Delete Never triggers" option. I use "Never" for a few different purposes:
1) Testing: allows you to quickly disable a whole trigger without deleting it.
2) Making it easy for others to perform predetermined changes to a map: you can have extra triggers ready to go but just blocked with Never, making changing the map around simply a matter of deleting a few conditions and maybe adding "Never" to a few other triggers.
3) Preserving triggers from older versions for historical purposes (or so that they could be restored in cases where future editors don't like the changes), or just because you think they're clever, even if you don't need them any more.

If the condition is unchecked, then the protector simply ignores it, or deletes that condition.

thats a very interesting concept people can use "always never end game", maybe even throw in some text "STOP STEALING MY MAP BITCHES" lolol

These.

Is the condition disabled? If yes, delete it. (It wouldn't run in SC anyway.)
Is the condition Never? If yes, delete the entire block. (It wouldn't run in SC anyway.)
Is the action disabled? If yes, delete it. (It wouldn't run in SC anyway.)
Playing with Never and disabled flags anywhere wont do you anything.

Right! I am fully agree with Farty and Flakoner!

DeVouReR, Pigy_G, ForTheSwarm, FoxWolf1, please stop seeding rumors! You can never use "Never" for protection against map-stealers and that's all.

I merely pointed out that it wouldn't work for protection no matter how unprotectors specifically deal with Never triggers; how's that the same as seeding rumors that it does work?

Never was used by Blizzard campaign script writers before they added the comment action.
So to write a comment for Staredit, they had to use "Never" and "Display Text Message".

At least, that's how I remember it anyway.

Dont be offended. You've said:
Which implies "Never" could somehow be used for protection purposes, supporting the previous discussion... Thats all

Map compression:

All triggers that will never run are to be deleted.
All conditions and actions that will never run are to be deleted.
Duplicate "Preserve Trigger" actions are to be deleted. You only need one.
Comments are to be deleted. They don't do anything.
The Always condition is to be deleted. It's merely a placeholder for "No condition".

Ooh. I should rework TinyMap to do stuff like that. Comments strings are deleted, but I just ignored the actual triggers. This is much simpler than all that WAV editing you were telling me I should do. It should also remove any holes in the conditions/actions created from removing things. >.>
Though I do remember making it delete never trigger blocks.

Post has been edited 2 time(s), last time on Jan 18 2009, 6:56 pm by FaRTy1billion.

I thought that removing conditions/actions doesn't help the compression, since SC keeps the trigger the same size, no matter the amount of actions/conditions.