Rushable objs

[Duo]

Yes/no?

Kra thinks they ruin maps.

[Turky]

I used to enjoy the non-wooktrick 2nd obj cargo because you either cooperated in just the right way to rush it, or else you probably got held for 20. Obviously that's a bit extreme. You can really only rush it at the beginning.

Which brings us to a problem that cargo poses time and again: obligatory objective routes which pass directly through the defensive spawn. That seems kind of shitty.

But anyway. Something like codes on Hoth would be a good example of both rushable and holdable.

[Laser]

sometimes bad objectives need to be rushed, like 2nd on cargo

but I'd prefer all objectives to be good ones and not rushable.

[Wufei Chang]

basically what i told him earlier. Rushable objective helps attacking balance out with defense. If not, the objective goes in favor of defensive like cargo (Defense Spawns which are directly in the path of the offense team almost all objectives).

I would think the defensive team wouldn't have to make an effort to setup if it isn't rushable.

[Duo]

I wasn't really thinking of Cargo when I posted that. My map is a lot closer to base than cargo.

[Kerafym]

An objective shouldn't be so hard to attack that it needs to be rushed to be overcome.

[A nub is In Ur Forum]

Retracted.

[j3rk]

I too consider an objective that can be rushed to be a bad objective design.

[Turky]

well, hoth codes are an example of an objective that can be either rushed, or held indefiniteiy. And, it doesn't necessarily have to be rushed at the very beginning (which sets it apart from cargo!), which is also nice.

It does pass by the enemy spawn, but at a distance. So it requires luck and/or skill to peg someone who's about to get the objective. Not the same as having to run directly past them.

[Max Rambone]

Codes are definitely the best objective of any map.

~archi