Make @CDT unable to command

Andon · Post by **Andon** » Thu Jun 19, 2008 7:59 pm

I don't know how hard this would be, but I remember that there is a thing in the code that allows @allegs and some special tokens into locked games, ignores the rank restriction, etc. I was wondering it it would be possible to make it so that someone in Cadet I (With the @CDT tag) could not be designated commander and could not launch a game if they manage to get the commander spot in lobby?

This, I think, would help a lot with the issues of Cadet I's thinking they know enough to command and just making idiots of themselves

beeman · Post by **beeman** » Fri Jun 20, 2008 12:42 am

Andon, if this were in 'Rants', i'd let it go - but besides the obvious reasons of why it's bad to prevent any group from having the same opportunity to play as another group there are 2 other points

1) CDTs were REQUIRED to comm at least 1 game (at least when I took it a year ago).
2) That's what mutiny is for. *sings* In good times, bad times, I'll be on your side forever more....that's what mutiny's for...

Wohh keep smilin', keep shinin' knowing you can always count on me...for sure
that's what mutiny's for
In good times, in bad times I'll be on your side forever more....
that's what mutiny's for...

Stingrae · Post by **Stingrae** » Fri Jun 20, 2008 12:53 am

Andon wrote:QUOTE (Andon @ Jun 19 2008, 09:59 PM) I don't know how hard this would be, but I remember that there is a thing in the code that allows @allegs and some special tokens into locked games, ignores the rank restriction, etc. I was wondering it it would be possible to make it so that someone in Cadet I (With the @CDT tag) could not be designated commander and could not launch a game if they manage to get the commander spot in lobby?

This, I think, would help a lot with the issues of Cadet I's thinking they know enough to command and just making idiots of themselves

As some-one noteworthy once said to me, we all have our bad nights.

ShadowMoses · Post by **ShadowMoses** » Fri Jun 20, 2008 1:51 am

We would probably get less people willing to take cdt cause of further restrictions on play

TurkeyXIII · Post by **TurkeyXIII** » Fri Jun 20, 2008 2:14 am

fishbone wrote:QUOTE (fishbone @ Jun 20 2008, 10:42 AM) 1) CDTs were REQUIRED to comm at least 1 game (at least when I took it a year ago).

That's now cadet-2. Cadet-1 is the newbie course, and doesn't require any commanding.

EdDaalleg · Post by **EdDaalleg** » Fri Jun 20, 2008 5:10 am

Isn't the post saying "don't command" in CDT-I enough? In my class a person was removed for constantly commanding and being warned not to. I think leaving cadets the ability to command is a fine tool for seeing who is actually interested in learning something from CDT and who is just going to frak around as usual.

Clay_Pigeon · Post by **Clay_Pigeon** » Fri Jun 20, 2008 6:20 am

Any complaints about specific CDTs should go to BV. He tends to have a short fuse with this sort of thing. We had one user get booted out of cadet the first day.

Andon · Post by **Andon** » Fri Jun 20, 2008 6:55 am

A) It would not prevent the Cadet I students from commanding, it would only prevent them from commanding with their tag. BV says, in the Cadet forum, that if a Cadet in Cadet I wishes to command, then they should do so without their tag.

Cadet I is the 'newbie course' that only spans a few weeks as opposed to the two months. They are forbidden from commanding in the first place with their tag on - So why not make it easier on everyone by coding it in?

juckto · Post by **juckto** » Fri Jun 20, 2008 7:44 am

QUOTE So why not make it easier on everyone except the coders by coding it in?[/quote]

Dogbones · Post by **Dogbones** » Fri Jun 20, 2008 5:55 pm

I think it is a bad idea to hard code in 'policies' which may change.

I am a huge fan of 'personal accountability' and 'personal responsibility'.

If BV asks the Cadet's not to command with their tag then they should follow his direction.

True, somethings are hard coded, like the newbie server bans, but that only happened after repeated abuse and other 'corrective' measures failed. Although to be technical about it, even that is not hard coded in the client.