Assistant Captainship

[PaulOakenfold]

I like the idea of the Owner and/or Captain having the ability to check off certain permissions each individual has. Much like other internet managing systems, it'd give you certain default permissions for a player when he/she joins, and an assistant and captain has their own set as well. The Captains or Owner himself however has a little check list that may entail... I don't know, just off the top of my head:

Ability to accept a join request
Ability to accept a challenge
Ability to challenge a squadron
Ability to remove a player from the roster
Ability to promote/demote a player

I'm sure you could think of other specifics, but I'm not the creative type, so the possibilities are almost endless for you dreamers. It'd be pretty easy to program, as I'm sure promoting and demoting through the TWD site already does this to some extent; although like I said, it just gives them default permissions at this point.

[Spikester]

sure,why the fuck not

[Shadowmere]

Became a lot better (but more coding needed) with Zer's, Airship's and Paul's idea (they're pretty much all the same). <- Thanks guys.

To the original argument with Kim and Reaver and others, you made valid points and got me to pretty much drop the original idea, but it definitely wouldn't hurt to have a system similar to suggested by ZerZera etc. As said, it would increase the stability of squads and keep them alive. Especially newer once.

From the start, this idea was to help new squads to come up and manage, instead of keeping the old squads or new TWL squads from dissolving, even though even those TWL squad dissolvements will reduce with this kind of system.

Waiting to hear Reaver's response.

[Ignominy]

why didn't you use TWPS? hahhahaha

[duel pasta]

I would like to see a system implemented where you can choose what or what not the assistants/captains can do. If you know how to code.. it's not that much work.

[Reaver]

The idea of checking off what a player can do is a good one. I'm not a code guru, I'll need to speak with AnZu/Mmaverick on the details, I think these are feasible options:

• accept people to a roster
• remove people from a roster
• accept and decline challenges

Dividing it up so that some players can only challenge for matches or some players can only accept might be significantly more difficult to do and possibly not worth the time invested. On a side note, it might be a good idea that a squad only has these options if they've been around a certain amount of time (a month, two, three, etc), to promote squad longevity and to reward good squad captains.

[Ward]

A captain could have the option of selecting if a assistant could challenge and accept a game, to add players, remove players from a game, sub players, accept, remove and demote other players

But isn't it all a part of an overall TWD value? Why would you want to have an assistant who can accept the game but unable to add or sub, or vise versa..

If this idea is implemented it should be something like this:

- TWD powers
- accept/axe/promote/demote powers (excluding the captain of squad)

There shouldn't be any option such as squad dissolution, because it should be entirely up to the captain. Assistants powers' must have a constraint to the extent of being unable possess powers equivalent to the captain.

Thus there wouldn't be a need for 3 captain slots, given the ability to edit your assistants with various powers..

And btw Sertifi, the idea you initially proposed with the "AC" bullshit is too primitive. Should this be implemented, the module must be a lot more sophisticated if you want a positive response from the players.

[Vue]

If you're worried about dissolving can't you make it so that each Captain has to agree before the squad is dissolved, and if Captains are inactive a TWD Op can be contacted to sort it out.

[Lizard Fuel]

The idea of checking off what a player can do is a good one. I'm not a code guru, I'll need to speak with AnZu/Mmaverick on the details, I think these are feasible options:

• accept people to a roster
• remove people from a roster
• accept and decline challenges

Dividing it up so that some players can only challenge for matches or some players can only accept might be significantly more difficult to do and possibly not worth the time invested. On a side note, it might be a good idea that a squad only has these options if they've been around a certain amount of time (a month, two, three, etc), to promote squad longevity and to reward good squad captains.

I can do that man. Just let me know what you decide to do.

[Barton]

I can do that man. Just let me know what you decide to do.

I doubt that u can pull that off liz.

[Ignominy]

no but he can make foreign do it

[Airship]

I like the idea of the Owner and/or Captain having the ability to check off certain permissions each individual has. Much like other internet managing systems, it'd give you certain default permissions for a player when he/she joins, and an assistant and captain has their own set as well. The Captains or Owner himself however has a little check list that may entail... I don't know, just off the top of my head:

Ability to accept a join request
Ability to accept a challenge
Ability to challenge a squadron
Ability to remove a player from the roster
Ability to promote/demote a player

I'm sure you could think of other specifics, but I'm not the creative type, so the possibilities are almost endless for you dreamers. It'd be pretty easy to program, as I'm sure promoting and demoting through the TWD site already does this to some extent; although like I said, it just gives them default permissions at this point.

hmmm thats pretty much what i said but not a check list for players just assistants and captains

[Airship]

But isn't it all a part of an overall TWD value? Why would you want to have an assistant who can accept the game but unable to add or sub, or vise versa..

If this idea is implemented it should be something like this:

- TWD powers
- accept/axe/promote/demote powers (excluding the captain of squad)

There shouldn't be any option such as squad dissolution, because it should be entirely up to the captain. Assistants powers' must have a constraint to the extent of being unable possess powers equivalent to the captain.

Thus there wouldn't be a need for 3 captain slots, given the ability to edit your assistants with various powers..

And btw Sertifi, the idea you initially proposed with the "AC" bullshit is too primitive. Should this be implemented, the module must be a lot more sophisticated if you want a positive response from the players.

I purposely made it one sentence to show that its a all together option...i do understand wut your saying but thats not wut i was applying....i was simply saying that we should have options....

[Airship]

I doubt that u can pull that off liz.

Barton I can code myself....with detail of how it would look like.....

[Cryp Wings]

Why not just have it under the same rank, but the captain chooses the amount of powere the Assistant gets

IE when he promotes a player to Assistant Captain it will ask "High Power or Low Power" or some crap like that

High power gives the Asscap powers it already has but on top may recruit players

Low Power just gives the Asscap powers it already has


bazinggggggg

I'm pretty sure that just involves doing something with the website, just making a new button I believe... then again I hated doing Database last year in my computer course =P

EDIT:I guess I had a bunch of other loserssssssss like Pauloakenfold steal my thunder .. DAMN U PAUL, DAMN U :P
What I said is the exact same shit they all did, but I think in alittle less text