I requested this over a year ago, and as it seems to have faded through the cracks, I will ask again.
Commander's need to be able to toggle ships availability to their team via the F4 Menu. In that way, a commander can further macromanage certain functions of a team.
Commander Ship Toggle
-
Malicious Wraith
- Posts: 3170
- Joined: Sun Jul 16, 2006 12:51 am
That seems true! (Not that my opinion matters on stuff like this, but that won't keep me from sharing it. 
). The more power the commander has to directly limit what their team can and cannot do, the less they need to actually communicate with their team. That does seem like against the "spirit" of Allegiance or some such; the team needs to communicate, and if a team doesn't communicate, you shouldn't be able to just flip a switch to make up for it; no matter how good a comm you are, if you have a bad team, you *should* still lose. Or boot some people so they start paying attention to the chat. But the chat is what should tell people what ship to take, not an artificially created lack of options.
On the other hand, there's almost never a good reason to be in a basic fighter when your team has hvy ints. Maybe some limited version of this could be implemented -- for example, such code written that IF the team has basic ships in one tech-path, AND the team has advanced ships in the other tech-path, THEN the commander has the option of turning the less advanced ships "off." But in all other circumstances, it's up to the team to pick the right ship, and if they don't, it's up to the commander to tell them, or if that fails, to boot them. But this all sounds really complicated and there's probably more important-like stuff that the coding volunteer peoples have got to do.
). The more power the commander has to directly limit what their team can and cannot do, the less they need to actually communicate with their team. That does seem like against the "spirit" of Allegiance or some such; the team needs to communicate, and if a team doesn't communicate, you shouldn't be able to just flip a switch to make up for it; no matter how good a comm you are, if you have a bad team, you *should* still lose. Or boot some people so they start paying attention to the chat. But the chat is what should tell people what ship to take, not an artificially created lack of options.On the other hand, there's almost never a good reason to be in a basic fighter when your team has hvy ints. Maybe some limited version of this could be implemented -- for example, such code written that IF the team has basic ships in one tech-path, AND the team has advanced ships in the other tech-path, THEN the commander has the option of turning the less advanced ships "off." But in all other circumstances, it's up to the team to pick the right ship, and if they don't, it's up to the commander to tell them, or if that fails, to boot them. But this all sounds really complicated and there's probably more important-like stuff that the coding volunteer peoples have got to do.
-
TheCorsair
- Posts: 2203
- Joined: Thu Dec 04, 2008 12:32 pm
- Location: Сою́з Сове́тски
+1KGJV wrote:QUOTE (KGJV @ Sep 14 2009, 07:56 AM) no. never. more tools for comms to enforce/micromanage = against Alleg 'raison d'etre'. This isn't SC or any random RTS. It's Alleg ffs.
If you wanted to prevent newbies using a Lt Int when there's Adv Figs available then just tell them to use an Adv Fig or Scout etc OR if they don't listen I guess they will have to learn the hard way.
Last edited by TheCorsair on Sun Sep 13, 2009 11:27 pm, edited 1 time in total.
"Neither east nor west" 
UNITED FOREVER IN FRIENDSHIP AND LABOUR
"The clouds are fleeting over every country, we stand fast, for no kind of rain will take away our smiles."
UNITED FOREVER IN FRIENDSHIP AND LABOUR
"The clouds are fleeting over every country, we stand fast, for no kind of rain will take away our smiles."
