OUTPOST BUG and Issues (updated for build 126)

Outposts are bugged. If you take an opposing team outpost, both teams start respawning on it!

OUTPOSTS get destroyed by 1 (one) miserable bomb. Suicide knights are a pain in the ass!

Just ONE unit can seize an outpost in 6.5 seconds. Does it seem right to you? It's too fast!

 

I only see the first one as an issue.

 

I had a rather quirky big in which I was building an outpost in a tunnel underneath the map. Once completed, the outpost literally flew up out of the tunnel and rose up to a huge cavern that the opposing team had dug out, where it landed and stayed.

 

Basically the way to fix that is, Make sure that you dont just build a 4x3 room, Make it a bit taller. Cause what it is, is when the top of the outpost touches anything above it when its getting built, It will shoot to the next open spot upwards. so makes the room like 5x4 or more.

 

I love, love, love suicide bombing an enemy outpost and pressing 4 with the ignited bomb :D

 

You can change class on an opposing team's outpost. I think it should remain non-interactive until seized by your team.

 

Grabbing a bomb that was thrown at an outpost will result on you changing class, as you change class with the grab/use button. This can be extremely annoying in tight situations where you need to get rid of that bomb (remember, one bomb destroys an outpost) and you change to builder, getting killed shortly after.

 

Any class can throw a bomb back.

 

True, but that was not my point. Look at this scenario: you are fiercely defending an outpost as a knight. Your shield is up, fending off rabid attacks of the opposing force. Someone throws a bomb at you. You grab it and prepare to toss it back... but suddenly you are not a honorable knight anymore! Your shield transforms into a bow and your helmet into a funny-looking hat. The *splint* *splint* sounds the swords made against your old shield now go as *splorch* *splorch* as the sharp things slash through your unarmored skin. You die with the bomb in your hands, which soon after explodes, sending your outpost to the sky.

Solution: find a new way to change class. I think we need more keys.

 

As of build 126 (22/08/2011), the issue with the team re-spawning on an OP they lost to the opposing team persists. I'm guessing that the bug might be triggered in multiple scenarios, as now it seems to be partially fixed.

This is what happened on my last game:
We (blues) seized an OP originally built by reds. It worked fine for about 3/5 minutes, when suddenly reds started spawning on it in mass bulk.
Theory: reds had another OP closer to their base. I'm not sure, but maybe our team took it and the game changed their spawn to the OP I first talked about?

P.S. I'm happy that now OPs can resist a bomb blast. Thanks for the change.