Staredit Network

The Never condition... If you can find a logical use for it, I'll give a prize.
There has to be some sort of use for this trigger (other than making it a pointless comment -.-)
Yeah, call this a contest if you must, find a good use for the Never condition.

PS: Prize is non-existant.

This thread... If you can find a logical use for it, I'll give a prize.
There has to be some sort of use for this thread (other than making it a pointless comment -.-)
Yeah, call this a contest if you must, find a good use for this thread.
PS: Prize is non-existent.

I fixed some spelling errors.

All joking aside, I use Never for disabling a trigger during testing rather than unchecking each action. So there you have it.

Before patch 1.04 there wasn't a comment trigger. Never + Display Text = Comment.

You can use never to separate your triggers and organize them.

So you have a trigger with conditions as never and comment it. Then you separate different types of triggers so it is more organized.

Can't you use the first trigger in each "category" as the comment trigger?

I like to comment everything so I can see more triggers in one screen. It lets me look through and edit them at a much faster rate because I can read each comment and immediately understand the basic conditions and actions in each trigger.

[center]I think Never was included for map testing purpses (Killed the spelling, but meh.) You can only use it for disabling triggers. Plus, even a trigger that's just Always(); Comment(); Wont mess with the gameplay, so why even use Never(); Comment();? As long as the onyl action is a comment, you can use any condition. Never was really just put to make map testing easier, so you don't have to disable 15 conditions, if you max out on conditions.[/center]

I always assumed that it was for something like this:

Trigger

Conditions:

¤ Player 1 brings 1 any unit to location "Poison Gas"

Actions:

¤ Kill all any unit at location "Poision Gas"

Trigger

Conditions:

¤ Never

Actions:

¤ Kill all Jim Raynor at location "Poision Gas"

Something like that would be useful, but I doubt it works because then someone else would be using it...

[center]Yea, I used to think it did that, until my triggers kept not working. If there were a Don't(); trigger, that'd be really helpful.[/center]

It's meant to confuse would-be map stealers.

That is obviously more organized but sadly every comment uses a string

I've never used the limit on strings in any map.

I did, when I had a really long-winded explanation of how to play when someone brought a unit to a beacon. I hit the character limit actually i think.

Heres a good one

Never;
Preserve Trigger;

ha ha ha damn.

The amount of strings in a trig should be nothing to a mapmaker. There are many ways to make long lists of actions extend over many triggers. Disagree anyone?

Edit : My bad, I was thinking about the amount of actions

----------------------------------------------------------------------------------------------------------------
I cant remember where i read it but apparently the neever trigger is for map making. If a map maker wnts to temperrarly disable a trigger but not kill all the conditions that are already there they can just stick a never trigger in there. I think that they later came up with the option to disable/ enable the triggers. Theories on this A) the disable trigger option wasn;t in starcraft original. B) they left the never in to help organize and so that it is easier to see then the diasable. other then that i would have no idea.
----------------------------------------------------------------------------------------------------------------

And of course you can make the never trigger happen in a game. In fact, you can make a trigger in a game! And no one on here makes maps, no siree.

YOU HAVE TO MAKE TRIGGERS IN A MAP, THEREFORE YOUR MAPMAKING.

"Never" does exactly what it does. It never executes the actions for the trigger. It is the only condition, that exists, that will have the actions not fire. And I know you can do a condition for deaths, and an unreal high value, but the Never is still more secure. Still, it has no practical use. Triggers are meant to be used anyway.

Actions don't use up strings

----------------------------------------------------------------------------------------------------------------
when i was talking about the map maker i meant that it really doesnt effect the player of the map too much. ie. it's so the map maker can see what things would be like without the trigger. so the trigger isnt for a effect that the player would see, like say create a unit that the player can use. this map trigger would be for the player, when i said it was for the map maker i meant this in a similair way. I thought it was implied but if a someone like you doesnt get it then i guese i'll just have to spell it out for ya.
----------------------------------------------------------------------------------------------------------------

[center]Never is one of thos back-stage, behind the scenes conditions. It's not meant to affect gameplay, only map making.[/center]

This is absolutely correct. Look at some of the Blizzard maps (Defenders of the Galaxy, in the scenario folder). This is one of their triggers:

Trigger

Conditions:

¤ Never

Actions:

¤ DisplayText("Triggers P4 = Level Changing P5 = Randomizers P6 = Attack Patterns 00-0F (Ramped) P7 = Attack Patterns 10-1F (Mean) P8 = Spawn Patterns and Bonuses Galactic Defenders = Messages and Invaders "); DisplayText("Variables P1-3 Custom = Scores P1-3 Minerals = Current game level P4 Custom = Number of players the game started with "); DisplayText("Switches S01 = P1 alive S02 = P2 alive S03 = P3 alive S04 = Message - P1 just died S05 = Message - P2 just died S06 = Message - P3 just died S07 = Reset P1's units and nexus S08 = Reset P2's units and nexus S09 = Reset P3's units and nexus S10 = Reset all players and setup next level S11 = Attack - Mutalisks S12 = Attack - Wraiths S13 = Attack - Scouts S14 = Attack - Guardians S15 = Attack - Battlecruiser S16 = Attack - Carrier S17 = Attack - Arbiter S18 = Bonus - Shuttle / Tassadar S19 = Bonus - Shuttle / Mojo S20 = Bonus - Dropship / Kerrigan S21 = Bonus - Dropship / Magellan S22 = Bonus - Overlord / Kill Invaders S23 = State - Attack pattern (MSB) S24 = State - Attack pattern S25 = State - Attack pattern S26 = State - Attack pattern S27 = State - Attack pattern (LSB) S28 = Attack Pattern Mutex S29 = State - Spawn point randomizer (MSB) S30 = State - Spawn point randomizer (LSB) S31 = Message - Guard your Nexus S32 = Message - Congrats, next round "); DisplayText("Locations Rand ## - Regions for randomizer. Air A# - Spawn points for enemy air forces. (Actual) Air V# - Spawn points for enemy air forces. (Virtual) The virtual locations are mapped to actual locations based on a preset cycle and certain random elements. P# Arb - Follows P#'s arbiter around, and is used to detect if a powerup is within range of the arbiter. ");