Posted: Wed Jul 19, 2006 7:05 pm
Yep. Unfortunately it kinda sucks, but commanders can boot for almost any reason. Bored's right when he says 90%+ of boots are actually initiated by the user being booted anyways.
If you move a comm's con, he may boot you. If you sarcastically say "Someone shoot the commander" after he does something you deem "dumb", he may boot you.
The Rules of Conduct only forbit booting in few circumstances:Booting a (4) or lower who was not actively working against his team or otherwise disrupting the entire teamBooting someone in retaliation for a boot they received earlier in that play session/dayBooting multiple people from your team in order to increase the chances of a #resign to passThese are the only real "bad" reasons to boot. But that being said, commanders *SHOULD* have some valid gameplay reason to boot the user before they do.
Perhaps that user sent a miner/con/carrier/drone to their death by ordering them?
Perhaps that user defied the commander's orders to defend which led to the death of a station?
Perhaps that user's chat is demoralizing his team?
Perhaps that user is trying to incite a mutiny? Even just by discrediting the comm?
All are gameplay reasons.
Luckily it's very easy to come back. You can have 3 callsigns at a time, and can change those 3 callsigns about twice a year whenever Pook resets the callsign links. This last happened about a month and a half ago, so it likely won't happen until the end of this year or early next year.
Enjoy,
--TE
If you move a comm's con, he may boot you. If you sarcastically say "Someone shoot the commander" after he does something you deem "dumb", he may boot you.
The Rules of Conduct only forbit booting in few circumstances:Booting a (4) or lower who was not actively working against his team or otherwise disrupting the entire teamBooting someone in retaliation for a boot they received earlier in that play session/dayBooting multiple people from your team in order to increase the chances of a #resign to passThese are the only real "bad" reasons to boot. But that being said, commanders *SHOULD* have some valid gameplay reason to boot the user before they do.
Perhaps that user sent a miner/con/carrier/drone to their death by ordering them?
Perhaps that user defied the commander's orders to defend which led to the death of a station?
Perhaps that user's chat is demoralizing his team?
Perhaps that user is trying to incite a mutiny? Even just by discrediting the comm?
All are gameplay reasons.
Luckily it's very easy to come back. You can have 3 callsigns at a time, and can change those 3 callsigns about twice a year whenever Pook resets the callsign links. This last happened about a month and a half ago, so it likely won't happen until the end of this year or early next year.
Enjoy,
--TE