I can't run the commands; /kill, or /say on my server.
I'me in LOCAL.ADMIN so I should be able to.
But it says, [SAY] command not known. (or whatever it says)
Are they in 2.0.0 or just 2.0.2???
(I'm running bzfs that came with the Mac os X 2.0.0 download)
Thanks,
BinarySpike
Server Commands on v 2.0.0
- BinarySpike
- Corporal
- Posts: 735
- Joined: Mon Mar 28, 2005 11:58 pm
- Contact:
- RPG
- Lieutenant, Junior Grade
- Posts: 2015
- Joined: Fri Sep 17, 2004 2:37 am
- Location: Chicago, Illinois
- Contact:
/kill is useful if you just want to kill a camper who is clearly dominating and people are leaving because of him. It also allows for another tool for admins to abuse, though.
/say is kind of pointless, but it's fun to trick newbies into thinking the server is "smart" and can carry out logical conversations
/say is kind of pointless, but it's fun to trick newbies into thinking the server is "smart" and can carry out logical conversations
- BinarySpike
- Corporal
- Posts: 735
- Joined: Mon Mar 28, 2005 11:58 pm
- Contact:
/kill has lots of value to me... I use it as a pre-kick warning to folks. Lots of people (especially newer ones) don't always read messages. But if you /kill them they will often read the reason. I've seen it work quite well.
Also, if you have a situation with very uneven teams (numerically) and a flag-carrier won't stop after being warned, you can use /kill to stop them from running the flag without having to kick them. It's a nice small stick to have in the arsenal.
I don't use /kill if at all possible unless I'm observer.
/kill was made as a pre-cursor to a more powerful "administrative freeze" function which would allow an admin to put a player in "timeout". Ideally such a command would blank their screen except for the chat window, which would only show messages from administrators. And anything the user sent to anyone would just go to the admin channel. That one is way beyond my coding skills, but some devs have expressed mild interest in it.
Also, if you have a situation with very uneven teams (numerically) and a flag-carrier won't stop after being warned, you can use /kill to stop them from running the flag without having to kick them. It's a nice small stick to have in the arsenal.
I don't use /kill if at all possible unless I'm observer.
/kill was made as a pre-cursor to a more powerful "administrative freeze" function which would allow an admin to put a player in "timeout". Ideally such a command would blank their screen except for the chat window, which would only show messages from administrators. And anything the user sent to anyone would just go to the admin channel. That one is way beyond my coding skills, but some devs have expressed mild interest in it.
- Spazzy McGee
- Sergeant Major
- Posts: 1405
- Joined: Mon Mar 21, 2005 4:59 pm
- Location: Planet MoFo, Sheffield Division; United Kingdom
administrative freeze
wouldn't that work like pause, but with a few script changes?
it would be like forcing someone to pause, heh.
it would be like forcing someone to pause, heh.
"Life is what happens to you while you're busy making other plans." - John Lennon
hmm
force... mmmmm.... must force pause....
still, it would be fairly complicated to code, because to black out the radar would either mean code that removes the radar, code that puts you in a place where there is nothing on the radar... code that draws an object on the screen in place of the radar... code that sets the radar and panel opacity... this is getting complicated...
still, it would be fairly complicated to code, because to black out the radar would either mean code that removes the radar, code that puts you in a place where there is nothing on the radar... code that draws an object on the screen in place of the radar... code that sets the radar and panel opacity... this is getting complicated...
- BinarySpike
- Corporal
- Posts: 735
- Joined: Mon Mar 28, 2005 11:58 pm
- Contact: