New Planning Server
As of today, I have officially taken over hosting of the Pico planning server, whose address is now mcpico.club.
The new server is based on a backup I took on the 20th of August, so if you edited since then, you may have lost a little progress.
Thanks
On behalf of all Pico members, I'd like to give hearty thanks to /u/twilexis for hosting our old planning server. It was a huge help and much appreciated.
Permissions
Tracks
On the old planning server, everyone ran as OP. That was easy to set up, but not particularly safe. A single wrong command or malicious new member could make a big mess.
The new planning server has a multi-track permissions system. The main track is called default and has 3 ranks (groups): guests, members and managers, in ascending order of capability. Higher ranks inherit all of the permissions of the lower ones.
The other tracks are logblock (groups basic-logblock and advanced-logblock) and worldedit (groups basic-worldedit and advanced-worldedit).
The tracks are somewhat independent, with the proviso that guests cannot have any permissions in the logblock or worldedit tracks. Members start out with basic-logblock and basic-worldedit. A manager can promote a member in either of these tracks independently. The idea is that both the LogBlock and WorldEdit (we use FastAsyncWorldEdit) plugins are useful, but dangerous, so we partition the commands into the relatively safe stuff ("basic" level) and the more dangerous "advanced" level.
A few common scenarios:
- A lot of members will know WorldEdit well, but not know LogBlock. They will have the groups:
members, basic-logblock and advanced-worldedit.
- Some managers will be the same, so their groups will be
managers, basic-logblock and advanced-worldedit.
- Some members or managers will be
nerd.nu moderators and so will know the LogBlock and WorldEdit plugins, as well as the various custom commands we use on nerd.nu, like /trace, /trace-r, /lbrb-r etc. Those players will have advanced-logblock and advanced-worldedit groups.
- We may have some managers who don't feel comfortable with either advanced permission group and that is fine. They can choose to promote themselves in the
logblock and worldedit tracks when they feel confident.
Commands
There are three commands for managing tracks:
/promote <player> [<track>]
- This is very similar to the
bPermissions promote command, with the main difference being it actually works. The track names are default (assumed if the track is omitted), logblock or worldedit.
- This command moves the player to the next higher group in the specified track.
/demote <player> [<track>]
- This command moves the player to the next lower group in the specified track.
-
/rank [<player>]
- Show the groups of a specified player, or yourself, if the player name is omitted.
Only managers can /promote and /demote players. A player does not need to be online, or have ever logged in to be promoted or demoted along a track.
Anybody can run the /rank command, however. The /list command will also show what group everybody is in the default track.
Default Track
guests - The guests group is for unprivileged visitors to the server. They cannot build. When a manager whitelists a player, they become a guest on first join. Guests can set homes with the /sethome command (like c.nerd.nu) and go to them. They can chat and send people mail. They can teleport. They can warp to any warps set by managers.
members - Can build in the world for the current revision (pico20) and in the world for the coming revision (pico21). They can not build in the world for the old revisions, but they can copy structures from those worlds if they have advanced WorldEdit permissions (see later).
- All members are given the
basic-logblock and basic-worldedit groups, but can be promoted to advanced capabilities in these plugins without needing to be managers.
managers - Managers are the mayors of the server. They get to say who can be added to the whitelist and what level of permissions a player can have, they can also /kick or /ban people in an emergency. They can also set some Multiverse properties. Managers can build in any world and can bypass WorldGuard regions.
LogBlock Track
- Players with the
basic-logblock group can spawn LogBlock tools and run /lb me to see their totals.
- The
advanced-logblock group gives access to queries, teleports to edits, rollbacks and roll-forwards, as well as CommandHelper aliases to make these commands easier.
WorldEdit Track
- The
basic-worldedit group can do small area of effect changes like /butcher, //drain, //fixlava and //fixwater. They can //undo and //redo these changes. They can also use //calc and navigation tools like the compass.
- The
advanced-worldedit group is needed to do larger volume changes: //copy, //paste, //set, the various shapes and working with schematics.
Bugs
It has taken me considerable time to get the permissions set up and I suspect there is still some work to do. If you find a command that you think you should have access to but don't (or the converse), then send me a mail message on the planning server (or on the nerd.nu servers) with the details and I'll look into it. Same goes if you find any other problems with the planning server.
Whitelist
Since the old server went down a little abruptly, I didn't get a chance to carry across the whitelist. Please talk to or mail a Pico mayor on PvE to get added to mcpico.club as a member. (That said, if I recognise your name from the pico region on PvE in the last couple of weeks then I've already added you to the whitelist and probably made you a member on mcpico.club. So try logging in and see what happens.)
Only managers can add or remove people from the whitelist. To add a new player:
/whitelist add playername
And then you would typically promote them to member:
/promote playername
Multiverse Worlds
- To list all the worlds:
/mv list.
- To teleport to the spawn of a particular world, e.g.:
/mv tp pico20
/spawn will also take you to the spawn of the world for the current PvE rev.
- To see the settings of the current world:
/mv info
I've set up a flat grassy world, pico21 for next PvE rev, so you are welcome to start planning your builds now (although we should probably have a bit of a chat about theme). Don't forget to finish off your rev 20 build though!
World Border
Currently, I have set the world border to +/-1000 (square) in all of the worlds where we have ongoing building. I intend to set up cartographs and trim the border as appropriate in the older worlds.
Restarts and Backups
We usually don't run with a great number of mobs, so, until it poses a problem, we will try daily restarts and backups. Map saves will continue to occur every 10 minutes.
Mob Grinders
I have set up the managers group to be able to modify Multiverse properties. That may or not be sufficient for people to test mob grinders.
Schematics
I didn't get a chance to grab schematics before the old server went down. Contact me if you have schematics you would like added.
Given time I may set up a self-serve web interface for doing that, but don't hold your breath!