Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Players named "all" #5

Open
madprof opened this issue Jul 16, 2010 · 4 comments
Open

Players named "all" #5

madprof opened this issue Jul 16, 2010 · 4 comments

Comments

@madprof
Copy link
Owner

madprof commented Jul 16, 2010

Some of the server commands use "all" or "allbots" for certain wildcard expansions, for example the "kick" command. If there's a player named "all" you can't kick that guy using his name without kicking everybody else too. You can of course use the slot number instead to work around the problem. But it should probably be fixed somehow.

@madprof
Copy link
Owner Author

madprof commented Jul 16, 2010

Woops, no, that's not right. You can't kick everybody anymore if there's a player named "all" because "kick all" will kick only that one player. In any case, still needs a fix of some sort.

@mission
Copy link
Contributor

mission commented Nov 22, 2010

i say we make a "kickall" command that takes 0 arguments, and make it cycle through all the players kicking them.. hmm.. maybe let it take an optional reason?

@gmorenz
Copy link

gmorenz commented Feb 2, 2011

if possible wouldn't it make more sense to make all always mean all players and if you have that as your name make it auto-kick you with reason "may not name yourself all", that way there wouldn't have to be a separate command each time you wanted to do something to everyone.

@madprof
Copy link
Owner Author

madprof commented Feb 3, 2011

Thanks for the input znerom. That would be a way to handle it. Another would be to auto-rename a player connecting with "all" as their name, to "all_1" or something. In the end I realized that you can simply do "kick all" twice, first to kick the one player, then to kick the rest, so I didn't give this high priority anymore. But yes, it would be nicer to have a fix for it. :-D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants