Tutorial for new staff

[Klaranth]

Hedgehog ; SX Make tutorial for new staff for specific tasks, like how to deal with nodes in minigames hub

Telemosaic tutorial might be bit outdated... would be nice to update that a bit. For the rest there is Tutorials island at spawn.

[S-S-X]

Telemosaic tutorial is not something that would be staff only tutorial, it is generic stuff used by all players who do use telemosaic.

Is this issue about telemosaic tutorial or about staff tutorial?

[OgelGames]

I think it means some kind of tutorial to explain stuff like what all the things in /control are, how and when to kick/ban/chat-jail, and other stuff new staff should know.

I think there used to be a book with something like this in it, not sure if that exists or maybe should be updated/extended.

[Klaranth]

I think it means some kind of tutorial to explain stuff like what all the things in /control are, how and when to kick/ban/chat-jail, and other stuff new staff should know.

I think there used to be a book with something like this in it, not sure if that exists or maybe should be updated/extended.

This.
If it could be added to the new staff member's inventory when they hit the kick/ban mission button .... ?

[Klaranth]

Also, being pointed to https://pandorabox.io/index.php/Moderator_manual can help. :)

[S-S-X]

If it could be added to the new staff member's inventory when they hit the kick/ban mission button .... ?

Mission could do this but books would anyway be in nearby chest where other moderation / administration / staff related stuff is stored. I'd expect new staff member to at least be able to find those mithril chests in control room and understand contents...

I think there used to be a book with something like this in it, not sure if that exists or maybe should be updated/extended.

Previous book had very little content, it was basically something like "take a look at main chat every now and then, kick or ban bad guys". Short and simple, I think rest of it was mostly "thank you"-letter 😄

Possible contents for staff book

Generic moderation duties and most important tools:

For basic moderation duties there could be instructions how to use xban and beerchat commands. Also information about blocking account creation, Discord and IRC bans. How and when these should be used. Maybe some information about other less important commands and #mod channel message like geoip and what df detect messages actually mean.

Chat moderation:

Basic guide for chat moderation, how to tell when to act and what to do like when to use chat jailing or moving player to different channel and how to communicate actions taken to player. Important chat channels are #main, all major language channels, #fun, #grounded, #mod, #offtopic, #lag, #nsfw, (#reports if it gets connect in game, and good to remember that there's #spam channel too...). Sometimes #kids channel is still mentioned but recommending it or moving players there should be avoided, #fun replaced this channel.

Privileges:

Possibly information about privileges and privilege protections as those are used mostly by staff members, protect_streets being in bit wider use and it should be mentioned especially as many players without moderation privileges can use protect_streets.

Potentially "dangerous" stuff:

Probably also information about things that can be very easily used in a way that is not acceptable like teleport privileges, world anchors and sharetool. Few other things too but maybe not worth mentioning would be penalty controller, global memory controllers, particle fountains and admin vendors. Information how and when to use those things, what can be given out to other players and how to handle requests like for example if someone wants to install particle fountains or world anchor somewhere.

What else?

[Klaranth]

Which buttons in /control NOT to use, not even in jest ?

[S-S-X]

Which buttons in /control NOT to use, not even in jest ?

You should not use anything that you do not fully understand, at least not without asking first. But no reason to have any controls that should not be used ever...

Everything is there for reason, added because it is needed in some specific situation. For some controls it is not possible to simply tell conditions when to use it because it gets complex and might require deeper understanding of engine and mod internals.

But basically if you do not know what some control exactly does then do not touch it, instead ask first and prepare for answer that requires reading code and learning how you connect running code with monitoring data to make decision about what controls are needed and how they should be used.

All controls can be described somehow and for some it is possible to add information when to use those. There should be big red all caps warning for all controls because every button in control room can cause big problems. Actually /server-announce command (to ping everyone and bypass muting) was originally added to communicate control room button pushing events for select buttons...

[Klaranth]

Which buttons in /control NOT to use, not even in jest ?

You should not use anything that you do not fully understand, at least not without asking first.

.....

tries again

Why do you think I ask for a book with helpful hints?

[S-S-X]

Which buttons in /control NOT to use, not even in jest ?

You should not use anything that you do not fully understand, at least not without asking first.

.....

tries again

Why do you think I ask for a book with helpful hints?

Like I said in previous reply, some of those controls cannot be explained in usable book because that book would basically contain: https://monitoring.minetest.land/d/YUpouLmWk/lua-server-monitoring-mod?orgId=1 https://gitlab.com/VanessaE/pipeworks/-/tree/master https://github.com/mt-mods/technic/tree/master/technic https://github.com/minetest-mods/mesecons Along with digtron and advtrains references and some of https://github.com/minetest/minetest/tree/master/src

All controls can be described somehow and for some it is possible to add information when to use those. For some it is not possible to add list of conditions when to use those when to stay away but most of time answer is stay away unless you know excatly what combination of information found from above sources causes something and how using that control affects it.

Usually those situations are discussed between staff in #mod chat room, players are informed before touching controls, possibly server announcement added and then moving towards actual controls.

[Klaranth]

Please add at the bottom of said 'book', by now it might be better to be in the wiki.

"When in doubt, contact [name two people who don't mind helping out new staff members]. Better to ask than to fumble around. "