Your working on say, your newest Bound map.
You reach a really badass problem in your trigger system.
What do you do?

I usually make a workaround.
If that fails, I rewrite the trigger(s) from scratch.
And if that fails too, I come crying to SEN for help.

I check the trigger and see what's wrong, then I fix it, I guess?

We're talking a major screwup that you can't understand.

Unless you're so good you can fix any trigger

Pretty much what you do.

I never work on the map again and cry myself to sleep for a couple months. Works for me. You guys are just crazy.

Stab myself in the eye, because I promised myself I would never make a bound map.

I try as many methods as I can think of to make it work the way I want to AND THEN when all else fails I improvise. If I cannot do what I want to or meet a satisfactory solution I usually end up scrapping the map altogether. This is why almost no one has seen any truly original maps out of me.

I wrote a trigger once that turned out doing something I DIDNT want, but turned out to be all the better! Strange how coincidences can happen.

Same here

I check the triggers, edit them for testing, run a few tests with all the other systems of the map active, then get a full understanding of what's happening and fix the problem.

If that fails I kill 13 christian babies and burn a church.

You know, you're right.
Who needs perseverance? xD



Haven't we all done that? My experimental rapid fire tank idea was an accident, the trigger was supposed to spawn a tank when someone brought an SCV to a certain spot. But I forgot to make the SCV disappear, then we got an uberfast firingt siege tank

badass problem in bound maps?
cant be a fatal one... I mean... it's only a bound map?!

To be exact, most parts of starcraft mapping is to "workaround" the problems in current times.
mobile grid = workaround
binary countoff = workaround
dropship menues = workaround
I'm presenting my teacher starcraft mapmaking and they already said while I'm building a map that everything is only a big workaround. and some people said me that I should map for wc3.

it depends on the system, if you should do a workaround for the workaround.

Well, first I check for stupid mistakes. (75% of the time).

After that I start putting in test variables. Since I oftenly use death counters I put in a number in the death counter that should make the next trigger go off. If it doesn't, that means the next trigger is not working, and if it does it means the first trigger is not working. After knowing that it's easy to go about fixing the problem. (20% of the time).

After that I'll typicaly check other triggers to make sure I have no conflicting triggers. (3% of the time).

If pretty much all those fails I just rewrite them. (2% of the time).

Not trying to be a dick, but yeah, pretty much.

Oh ya? What if the problem's that you somehow accidentaly stuck a Wait(90); into your 186 lines of hyper triggering ( assuming three commented, preserved triggers ) , and this disrupts some critical and extremely precision-intensive trigger in your map causing the whole thing to fail? D:
>.> <.<
Bound maps don't necesarily have to be nothing but, 'dodge the explosions/lurker spines/larvae,' y'know. ;o

------

Anyways, for myself...
Look my triggers over a few dozen times in frustration, whine to my friends about it, on rare occasion post a topic on SEN or Maplantis and end up not recieving any kind of solution, and then perform increasingly infrequent tests and random tweaks until I finally end up unofficially halting progress on the map because the exponential growth in delay between said tests/tweaks has grown to critical length.
Since these problems usually occur in really basic, but fundamental trigger systems of my maps, I usually don't have much I can do about working around them or rewriting my map, as any such solution I can come up with either has flaws of sorts that I simply won't abide, or will require far too many triggers for my short patience span.

I outsource the job to Chinese child workers.

Then you're a dipshit for not copy/pasting the waits and shouldn't be allowed to make maps or reproduce.

If I made a trigger mistake on something as simple as a bound map, the universe would collapse.
So I don't think I'd do anything.

What if it's an RPB (role-playing bound )?

The next topic should be "How do you plan on survivng when a Korean messes up a bound trigger?"

Post has been edited 1 time(s), last time on Feb 21 2008, 6:00 pm by FatalException. Reason: MOAR LULZ

Obviously, the person's using a rearranged keyboard in which the 'v' key is next to the number row, and he chose an odd place to break the copy/pasted string. >.> <.<

I love workarounds, they make me feel all microsoft. But how do you work around the fact that something, somewhere, somehow is making my map lag?

I guess i could just do it microsoft style and just leave it in...