For list key, referencing these two threads: Public Key for Server - Request page broken
and in Obtaining a key
Zehra wrote: ↑Sat Oct 14, 2017 6:25 pm
You might want to try contacting blast
for a list key.
As for global groups.
You can load global groups with
(It should work fine with a '.txt' or '.conf' extension and I believe path to directory works as well.)
Here's a sample group file from the BZFlagWiki:
Code: Select all
# In this example everyone in the SAMPLE.ADMIN group also gets the permissions
# of SAMPLE.COP, because of the *SAMPLE.COP entry which adds the permissions
# of SAMPLE.COP to SAMPLE.ADMIN, and everyone in the SAMPLE.OWNER
# group gets the permissions of SAMPLE.ADMIN (including the SAMPLE.COP) permissions
# because of the *SAMPLE.ADMIN entry.
# Must all be on one line
SAMPLE.COP:+FLAGHISTORY +KICK +KILL +BANLIST +PLAYERLIST +POLL +VETO +PRIVATEMESSAGE +ACTIONMESSAGE +ADMINMESSAGESEND +ADMINMESSAGERECEIVE +IDLESTATS +SPAWN +TALK +SAY +MUTE +UNMUTE +ANTIBAN +ANTIPOLL +ANTIPOLLBAN +ANTIPOLLKICK +REJOIN +SAY +FLAGMASTER
SAMPLE.ADMIN: *SAMPLE.COP +BAN +UNBAN
SAMPLE.OWNER: *SAMPLE.ADMIN +SETVAR +SHUTDOWNSERVER
# There are 2 "default" groups which are on every server they are
# EVERYONE and VERIFIED. EVERYONE is, well, everyone, including
# those in other groups. VERIFIED are users who have Globally Identified,
# also including those in other groups. You may include them in
# your group file. Permissions can be prefixed by one of 3 symbols +, -, or !
# +PERM adds a permission
# -PERM removes a permission
# !PERM denies a permission, even if it is inherited from another group.
# If the permission has no symbol + is assumed. If there is a conflict in perms
# between groups a person belongs to the order of precedence (from lowest to highest)
# is -, +, !. This means if there is a -PERM and +PERM, the permissions that the
# user gets is +PERM. On the other hand if there is a +PERM and a !PERM the user
# is denied that PERM. The order in which the permissions are in the group file
# is not important.
# The line below removes all of the default permissions from the EVERYONE group and then
# gives them back TALK and SPAWN.
# EVERYONE: -ALL +SPAWN +TALK
I wouldn't recommend using it, but it should give an idea on how a group file works.
There also has been some changes which should be noted from 2.x to 2.4.x
They are documented here: BZFS 2.4 Upgrade
Here's a short summary from it:
Code: Select all
-public changed to -publictitle
-publickey specifies your server key for including your server on the server list
-utc logs server timestamps in UTC instead of localtime
-offa selects teamless free-for-all game style
-time can specify end time for timed games
-noTeamKills can remove teamkilling possibilities from the map
Groups can now be referenced in the groupdb before they are defined
If you have your old group files and configurations, it should be possible to update them to the newest format.
Be sure to read through the current permissions, as there is a few of them which are no longer needed.(antideregister
is one of them.)
Some plug-ins might also require custom permissions, so be sure to check out for that as well.
If there is any extra details/help is needed, feel free to contact me by private message.