Orbital Strike: Does it negate good team game play?

[StumpyTheOzzie]

I like the thought of a commander thinking "I *COULD* OS that F.O.B. or I could pay for half a dozen vanguards and a bunch of reavers to attack it instead"

But I doubt if you can gift resources to other players so he'll totally end up osing. Is there an option for an outfit tax like in Eve? That was a stroke of genius that.

[Graywolves]

If a team is bunched up on top of each other and spending 10 minutes figuring out what to do then I think that OS is more than deserving. I enjoy moving with a sense of urgency and specifically being aware of areas that look like a juicy OS target.

[Kezz]

Originally Posted by StumpyTheOzzie

I like the thought of a commander thinking "I *COULD* OS that F.O.B. or I could pay for half a dozen vanguards and a bunch of reavers to attack it instead"

But I doubt if you can gift resources to other players so he'll totally end up osing. Is there an option for an outfit tax like in Eve? That was a stroke of genius that.

Yeah, Higby (or someone from SOE; I think it was Matt) said you won't be able to give other people vehicles you've pulled, to stop a high cert player handing out tricked-out vehicles to low-cert buddies.

Whether there will be any way to transfer raw resources between players, I don't think I've seen any mention of.

It would be good if an Outfit could have a pool of resources that members were able to draw from to grab "stuff", with, I guess, rights to do so determined by the Outfit chief, probably using the Outfit ranks. If it did have that, the better way to do it would be a "bonus percentage" of everything the Outfit's members earn gets added to the Outfit's coffers, without being taken from the member's income. I think this is a better approach for an accessible game; the uninitiated tend to balk at paying taxes in-game for potentially nebulous benefits and that would be an unnecessary barrier to Outfit recruitment.

There seems to me (though I'm not entirely sure where I got the conclusion from) to be an assumption that collected resources will contribute to some sort of Empire pool, though I don't think it's clear quite what that might be used for.

[Pillar of Armor]

Originally Posted by GreatMazinkaise

Exactly... #1 rule of miniatures games is to avoid clumping your troops, and this applies in equally well in any game where there's lots of AoE insta-death weapons.

What it ultimately comes down to is gameplay: Do you think it's more fun to run shoulder to shoulder with your squad and be able to feel and see the effect of your teamwork without worrying about being OSed, or is it more fun to have an instakill weapon and at the cost of having the ability to fight side by side.

My problem with it is: OSes are fun for one moment every hour or so, but teamwork is fun for as long as you can keep it up. Fighting within close range of your squad or allies gives you a strong sense that you are working as a team and makes it apparent that the scale really is massive. Fighting when your scattered just feels like deathmatch.

That's how I feel about it anyway.

[Buggsy]

The OS is a game of Monopoly where every place is Boardwalk

The OS is a game of Chess where every piece is a queen

The OS is a game of Battleship where every peg has a ship in it

The OS is a game of cards where every card is an Ace of ******

See how lame the OS is? no probably not, gaming companies keep making the same stupid mistakes over and over again.

[Traak]

Are there any games out there that don't have OS's that have more players than PS does?

[NewSith]

Originally Posted by Traak

Are there any games out there that don't have OS's that have more players than PS does?

DEFCON

[Pyreal]

The abundance seems to me to be the larger problem, while having it a 1 man operation in a team based game the other.

For the first problem of OS spam:

1: Hard limit on OSs in an area by time and faction (TR dropping one doesn't lock out NC or VS OS)
2: Raise costs. It should be a high cost/reward

The second problem of the 1 man army:
1: Require OS targets to be lased or otherwise tagged
2: Require OS launcher to be SL
3: OS to be launched from console/base or field
3a: if launched from base minimal warning to target
2b: if launched from outside base target has greater warning