SPAWN permission required in CVS and will be in 2.0.2
- Tim Riker
- Maintainer
- Posts: 21
- Joined: Thu Dec 02, 2004 5:33 pm
- Location: USA, Utah, Salt Lake City
- Contact:
SPAWN permission required in CVS and will be in 2.0.2
There is a new permission called SPAWN.
It will be set on the EVERYONE group by default.
You can override the EVERYONE group and set SPAWN on something like VERIFIED instead.
For league servers you would likely remove SPAWN from EVERYONE and set it on the appropriate league groups.
Also the -requireindentify option has been removed. The new SPAWN permission replaces this feature.
This is the case in CVS at present. It is expected to be true for the upcoming (likely 2.0.2) stable update as well.
IMPORTANT: You should add the SPAWN permission to the correct groups in your groupdb now. This will be ignored by 2.0.0 servers. (ie: not break them)
It will be set on the EVERYONE group by default.
You can override the EVERYONE group and set SPAWN on something like VERIFIED instead.
For league servers you would likely remove SPAWN from EVERYONE and set it on the appropriate league groups.
Also the -requireindentify option has been removed. The new SPAWN permission replaces this feature.
This is the case in CVS at present. It is expected to be true for the upcoming (likely 2.0.2) stable update as well.
IMPORTANT: You should add the SPAWN permission to the correct groups in your groupdb now. This will be ignored by 2.0.0 servers. (ie: not break them)
Simply love
Thanks for all your work, Tim !
Now, just add the KILL permission
Now, just add the KILL permission
Christophe HENRY - France
Re: Simply love
haha if they ever do that that'll be funnysbgodin wrote:Thanks for all your work, Tim !
Now, just add the KILL permission
- Memnarch
- Sergeant First Class
- Posts: 273
- Joined: Mon Jul 05, 2004 10:42 pm
- Location: Sorry, I'm a Nowhere Man
- Contact:
Re: SPAWN permission required in CVS and will be in 2.0.2
Ok, so basically, this is a feature that asks the server if a non-registered player can play? Ok, here's the deal: I don't see how a server can make decisions by itself, wouldn't there have to be an admin to allow such person to enetr the game? The only immediate thing to do would be to register here, or to register at the server, but what if said player does not really want to? How would this feature work exactly?Tim Riker wrote:There is a new permission called SPAWN.
It will be set on the EVERYONE group by default.
You can override the EVERYONE group and set SPAWN on something like VERIFIED instead.
For league servers you would likely remove SPAWN from EVERYONE and set it on the appropriate league groups.
Also the -requireindentify option has been removed. The new SPAWN permission replaces this feature.
This is the case in CVS at present. It is expected to be true for the upcoming (likely 2.0.2) stable update as well.
IMPORTANT: You should add the SPAWN permission to the correct groups in your groupdb now. This will be ignored by 2.0.0 servers. (ie: not break them)
some servers require registration. right now that's done with -requireidentify in the command line.
This moves that behavor into a permision, so it can be consitent with the other permisions.
If you want to require identification, you move the spawn perm to the registerd group. Then however your server does registration ( local or global ) will then have to happen before somone can spawn. This just makes it a bit more flexable, since you could move the spawn perm to a group other then registerd for someting like a leauge game, so that only team members can spawn.
If your server does global reg, then yes, it will have to contact the list server and bzbb to work. If your server does local registration then the player has to do a /identify, like 1.10.x did.
If the SPAWN perm is in the EVERYONE group, then nothing has to happen, and you play as a normal open server.
By default the SPAWN permision is added to the EVERYONE group. What Tim is saying is that if for any reason you have overiden your EVERYONE group by puting an entry for it in your groups file, you will need to add the SPAWN permision to it, if you want your server to behave the way it used to work in 2.0.0 when you upgrade to 2.0.2. 2.0.0 will ignore the permision right now, so he's saying go ahead and put that in NOW so you'll be ready when the time coes. .
This moves that behavor into a permision, so it can be consitent with the other permisions.
If you want to require identification, you move the spawn perm to the registerd group. Then however your server does registration ( local or global ) will then have to happen before somone can spawn. This just makes it a bit more flexable, since you could move the spawn perm to a group other then registerd for someting like a leauge game, so that only team members can spawn.
If your server does global reg, then yes, it will have to contact the list server and bzbb to work. If your server does local registration then the player has to do a /identify, like 1.10.x did.
If the SPAWN perm is in the EVERYONE group, then nothing has to happen, and you play as a normal open server.
By default the SPAWN permision is added to the EVERYONE group. What Tim is saying is that if for any reason you have overiden your EVERYONE group by puting an entry for it in your groups file, you will need to add the SPAWN permision to it, if you want your server to behave the way it used to work in 2.0.0 when you upgrade to 2.0.2. 2.0.0 will ignore the permision right now, so he's saying go ahead and put that in NOW so you'll be ready when the time coes. .
JeffM
REQUIREIDENTIFY is to force players to identify : have a global or local account. Once they have one, this permission has no effect except if they don't want to "/identify".
SPAWN allows players to play. To have the rights, they must identify to be recognized in the group which can spawn.
SPAWN allows players to play. To have the rights, they must identify to be recognized in the group which can spawn.
Christophe HENRY - France