Y U NO GO ENEMY BASE? D:

Yeah, I don't know what's up with that. It seems like it started happening sometime in the 2.40's and I have no idea why or what to do to fix it. Sometimes you'll have stuck reavers sitting there and have other reavers walking past them, with no clear reason why the stuck ones won't move. I tried putting in a trigger for 2.60 that adds 1 scarab to all reavers (after spawning complete) before moving them to the field, just incase they weren't taking the attack order because they didn't have scarabs, but that didn't fix it.

I'm curious as to how you have 21 reavers in that screenshot, as the battlefield should be capped to 14 in total. Looks like it's just after a spawn, with 1:05 on the timer and the enemy spawn box still full, so maybe the trigger to remove excess hasn't fired yet.

Can you look over my replay too while you have the time?

Actually I had more than 14 most of the game, I'll get a replay of it.

Are immortals being used much?

I question myself why the Reavers get stuck. For me, I think they tend to stop moving once you get the Shuttle Hero out for Protoss. It seems like if they try to move and try to get into the shuttle at the same time, maybe causing them to get stuck? That's my opinion anyways since it happens to me once I build the Protoss heroes into play.

Hey I found something interesting - the shuttle and the dropship tend to load units Look at 11:40 for the shuttle and around 15 for the dropship. The shuttle loads a reaver and a goon and the dropship loads a siege tank.
Anyway, it's not a big deal.

Attachments:

That's a very good theory, actually. Not a lot I can do about it except remove the shuttle and/or dropship.

Yeah, nothing I can do about it. I think the Infestor can also pick things up, even though I've disabled overlord transport upgrade.

If it is a hero ovey then yes.

Not sure if this has been covered or not yet. But why are my own probes killing my own structures in my base? Randomly every once in a while a building will just explode next to my probe. This has happened to me multiple times, mostly with protoss.

That happened to me too. There's no way I could've typed the ESC key or move the mouse on the bottom right corner.

This is almost certainly due to the new spawning system. I didn't end up working on the map over the weekend due to the Diablo 3 open beta. Luckily for you guys I have tomorrow off work so I intend to have a look at this then.

Played a PvZ and lost primarily b/c the opponent was spawning over 400 hydras and lings and prevented my spawn of units. (somewhere around 435 units by 2/3 of the game)
Where's the trigger that prevents spawning over 400 units?

Attachments:

Well that's not supposed to happen.

Watched your replay. Just checked the triggers: stupid mistake. The 400 spawn limit applies to the bottom team only, evidently I only tested with them and forgot to test the top team. So the top team can spawn up to 511 units while bottom is capped at 400. The diffused spawning still kicks in though so that helps at least.

Also in that replay is an example of the enemy larva bug, where the red player ends up having a green larva even though green isn't in the game, so that's useful. Also see that the 14 battlefield limit on reavers is not enforced. Haven't looked at the other replays yet.

Edit: also fixed the reaver battlefield limit bug: stupid mistake again. The reavers are moved to a different location on the battlefield than regular units, and I changed the trigger action to remove one from the correct location, but the condition is checking Bring against the normal location, so of course it never fires.

Watched the replay to see the larva bug: it happens when a larva is created during the 0:00 window when the buildings are given to the CPU/P9-11. Not entirely sure why red ends up with an (apparently) P1 green larva though, would have thought it'd be owned by the CPU but that's what it's doing.

Post has been edited 1 time(s), last time on Apr 24 2012, 9:19 pm by Lanthanide.

Thanks Lanthanide! Now, why don't you have a custom smilie yet?

The reason why the reavers just sit there is cause when someone gets shuttle hero(from making a cannon in their base)the reavers will freeze cause the freeze will think that the shuttle will pick them up an they'll keep waiting for it to pick them up the reavers will never freeze until you get shuttle, thats why I tell teammates not to get cannon hero which makes the shuttle come out an causes the reavers to freeze, thats how the AI usually is

Thanks IF, that pretty much confirms Leon's theory.

I'll have a look at what I can do with this knowledge: giving orders to the shuttle pre-emptorily may prevent the reavers from attempting to load into it. I'll also play around with giving the reavers between players periodically (at most once at spawn and once at 30s) to clear any 'stuck' orders that they have, hopefully that'll help.

As for the map, yesterday didn't quite go as planned. I did a little bit of work on the map in the morning, but didn't get anything done in the afternoon/evening at all as my boyfriend changed his plans and I also ended up playing with my new phone instead. I'll try and get the next version out this weekend.

Another thing I noticed is that whatever is picked up gets lost to the shuttle's pre-programmed drops... Like if it picks up a reaver it then puts down 2 zealots, dragoons, more zealots, an archon, zealots... no reaver!

It's not 'putting' those units down, it's creating them. And yes, it'll pick reavers up and generally never drop them. Not a lot I can do about that.