SC2Mapster

I agree with everyone else that the beginning was great and that past the beginning it was very hard. Edits: Having played this map another 10 times, I think what I said before isn't very valid, so here's new feedback. Using jump start definitely gives an early game advantage. First off, the player gets all of those terran units which are, with the toss units at full strength, enough to kill a hatchery or two early on (whether that slows the enemy attack idk). Secondly, there are no zerg guarding the expansions like there normally are. The seige tank is also huge for the early waves. I think to make the map a little more doable, there should be something in the transmissions suggesting expanding to the base southeast first. Maybe if a certain terran unit is saved it suggests the resources there immediately while the player is warned that the rich nodes exist but are very close to enemy territory at the normal time. Also, waiting for the nexus is kinda lame. Maybe have more terran units but have them be neutral owned and have them make a suicide run into an enemy base after being rescued which the player can opt to assist with to gain some breathing room early game from one of the enemies. I liked having the bunker explode to reveal infested terrans. If there were a couple more encounters like that around the map, both with infested terrans and some human survivors, it would keep the midgame more in the style of the early game.

The first part of the game, in which you move through the map with only a small force, was brilliant. Class Blizzard. I felt like a pro when I pushed the banelings away with force fields on my first try. The reinforcements right before you get into the terran area were well timed as well.

But after that things got a bit rougher. Even if I carefully conserved all my units and rushed to help the terrans nothing but the tank in the back ever survived.

Maybe use a bit of scripting to autobuild the nexus quickly? I felt a bit silly just sitting there, waiting for it to finish warping in. Maybe I'm missing something.

Also, I think the zerg attack waves would challenge even a higher level player (especially with the fast upgrades). Maybe take a look at the timing of actual blizzard levels? They're usually pretty good about starting out slow and scaling up. In my own personal experience I ha only been able to crank out a few lots before the first two waves of lings and hydras blew threw my standing forces and left me fairly defenseless for the third wave. I tried to mass colossi and only made it a few waves further than that.

Maybe it would help players to know a bit more about the map. You could ping the zerg areas (and so where the forces would come from), or you could alert the player when a wave was coming and from where. It was personally frustrating having huge zerg armies show up out of the blue and wipe out my base while my army was defending my expo.

Apart from balance, this is a very professional map! Good work!

If the problem persists Chewable, you might consider writing your own attack wave triggers. Instead of using the the AI-Attack Wave, make a region in the base and write a trigger that's basically:

Event: None (i.e. activate from another trigger)
Condition: Hive / Other Building / Computer Base Still Alive
Actions:
-Create 10 zerglings (or 4 roaches / 2 ultras / whatever) at Region-In-Base
-Pick each unit in Region-In-Base and issue order: attack a point in player's base.
-Wait X time
-Run Next Attack Wave Trigger

That's your basic attack wave; you can make it a lot more complex, though. Could require the computer to have vision of any player expansions and therefore have them send out periodic scouts (which players could eliminate early to keep their expansions safe) or you could simply put in a random chance that the attack wave goes to the expansion spot first.

Or, for harder difficulties, you could customize attack waves to send antithesis units (i.e. vikings against colossi) which would require players to either manipulate the AI or run a balanced force, which is rather more difficult than players going oh look I have colossi I win or oh look I have broodlords I win.

Curses! It was worth a shot; I've been working on other triggering projects, so I haven't had much time to test out the AI ones they've provided.

Also, yeah, if you don't have conditions, I definitely wouldn't tell it to check conditions. I didn't notice you had any of those.

Chewable I took a look at your triggers and found nothing that stood out as the cause of that bug. I then attempted various strategies but could not reproduce it either.

I can make the following suggestions, however:

-Put brown/green initialize and wave triggers as initially off. The editor's newly released, and I wouldn't want to make a wager on the behavior of an activated event-less trigger just sitting there. (actually I would but when you can't find the cause of a bug then sometimes you just have to clean up code and hope for the best!)

-The probable choke-point/break-point of the bug is that if any attack wave never gets sent (for whatever reason), then the execution of that particular trigger will be forever stalled, and no new waves will follow. I'd suggest divorcing the wait...

AI - Set the target for player 6 attack waves to (Player group(1))
AI - Add (14 / 16 / 18 / 20) Zergling to the attack wave
AI - Send the attack wave from player 6 to attack in 300 seconds and Wait
Trigger - Run Brown Wave 2 (Check Conditions, Don't Wait until it finishes)

is how you have it now, I would alter it to:

AI - Set the target for player 6 attack waves to (Player group(1))
AI - Add (14 / 16 / 18 / 20) Zergling to the attack wave
General - Wait 300.0 Game Time seconds
AI - Send the attack wave from player 6 to attack in 0 seconds and Don't Wait
Trigger - Run Brown Wave 2 (Check Conditions, Don't Wait until it finishes)