Free Allegiance Forums

So I don't have to look at the banlist being filled with "AFK with GC"

Deathrender wrote:QUOTE (Deathrender @ Jul 24 2010, 10:04 PM) So I don't have to look at the banlist being filled with "AFK with GC"

It's possible to change this (one liner), but you will loose the current ban documentation of @Allegs.

So don't look.

Besides, if I'm not mistaken, that code and status is an FAO thing and has nothing to do with the Alleg client or server (which is what this forum is about). "Feedback" would be the more appropriate place.

Deathrender wrote:QUOTE (Deathrender @ Jul 24 2010, 09:04 PM) So I don't have to look at the banlist being filled with "AFK with GC"

?

You don't have to look at the banlist at all if it bothers you.....

It wouldn't solve AFK with GC anyways, since you can't lobby ban somebody on a team.

Xeretov wrote:QUOTE (Xeretov @ Jul 24 2010, 04:39 PM) It wouldn't solve AFK with GC anyways, since you can't lobby ban somebody on a team.

this, someone clearly doesn't understand how #ban works

However much his reasoning sucks, and it does, and however much the implementation is impossible, which it is, it isn't that bad of an idea.

Allowing @Allegs to, via an in-game thing, remove commander status from a player, would not be that bad. No need to kick them from the team - Whoever ends up as the new commander can deal with that if they so wish.

What I would suggest is something that would remove the commander of a team and give a warning to all players on that team that their commander was going to have his status revoked - And whoever the next commander would be would be given notice that they would be an commander in 10 seconds or so. Not only would this be useful for server hostaging/idiots who refuse to start the game/AFK with GC/whatever, but it would be useful in-game, where the commander can go AFK and completely screw the pilots over. Granted, most situations in-game can be resolved via #mutiny, but in events or large games where it is virtually impossible for a mutiny to pass, a way to get rid of the commander via a third party would be useful.

To prevent issues, and while any @Alleg that did this would certainly lose whatever status they had, removing a commander should only be capable of being done from inside the lobby. No forcing a mutiny for your team because the guy's just new, and no forcing an enemy commander to go AWOL.

Xeretov wrote:QUOTE (Xeretov @ Jul 24 2010, 10:39 PM) It wouldn't solve AFK with GC anyways, since you can't lobby ban somebody on a team.

You miss the point of code changes, let me modify the suggestion for you:
Allow people with @alleg tag to #ban any player on any team.

Hmm.

I'm not really seeing the point of this.

Removing GC from someone in the lobby might be nice as an alleg. And just put them in NOAT, rather than booting them.


In-game there is already methodology for a team to remove a commander, And methodology to boot a commander if you are an Alleg.

I don't really see the point of it as an in game option, in most cases in-game it's dealt with by a hasty #mutiny (where a new player gets comm, or a commander is failing terribly).

I can solve it by removing the game ban listing.