|
|
| (4 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| Welcome to the DemocracyCraft Administrator Staff Guide! This guide contains all the relevant information for doing your job as Administrator in day-to-day operations.
| | {{delete|unneeded}} |
| | |
| === How to manage Billboards ===
| |
| We use a plugin called ImageMaps to allow us to implement images in-game via item frames. This plugin is currently how we’re able to make billboards!
| |
| [[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]
| |
| | |
| ==== Steps ====
| |
| | |
| # Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]
| |
| # Download the image in-game by running <code>/imagemap download <filename> <sourceURL></code>
| |
| #* Replace <code><filename></code> with an easy to identify name, without any file extensions such as <code>.png</code>.
| |
| #* Replace <code><sourceurl></code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.
| |
| # Place the image in-game by running <code>/imagemap place <filename> [frameInvisible] [frameFixed] [frameGlowing] [size]</code>
| |
| #* Replace <code><filename></code> with the file name you selected in Step 2. Please add the file extension featured in the <code><sourceurl></code> you used earlier.
| |
| #* Replace <code>[frameInvisible]</code> with “true”, no quotation marks. This ensures that players do not see the default item frame texture in empty spaces of the image.
| |
| #* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.
| |
| #* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.
| |
| #* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB
| |
| #** i.e. for a 2 by 2 image, it would be: <code>2x2</code>
| |
| # Admire your work!
| |
| | |
| === How to conduct Rollbacks ===
| |
| We use the industry standard plugin CoreProtect to log all of our in-game interactions. This allows us to rollback, inspect, and review any player changes or interactions as they happen.
| |
| | |
| ==== Commands ====
| |
| | |
| * <code>/co help</code> - help command; displays all commands.
| |
| * <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.
| |
| ** '''Usage:''' <code>/co rb u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude></code>
| |
| * <code>/co undo</code> - revert a rollback.
| |
| | |
| You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].
| |
| | |
| ==== Additional Information ====
| |
| Here is a [https://www.youtube.com/watch?v=JwijCiueZ3Y video tutorial] that goes other aspects of CoreProtect that are not covered within this guide.
| |
| | |
| === How to manage VPN Bypasses ===
| |
| Players will commonly open tickets suffering connection issues. There are multiple ways we can attempt to solve this, but before anything else get them to turn their router off '''for at least a minute''', and then turn it back on. This is often the simplest solution. See [[Screening Players For VPNs]]
| |
| | |
| ==== VPN ====
| |
| If all fails, this could be a routing issue that cannot be solved through conventional means. Asking the player to use a free Virtual Private Network (VPN) such as [https://cloudflarewarp.com/ Cloudflare Warp].
| |
| | |
| If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.
| |
| | |
| === Administrative Commands ===
| |
| These are useful commands to know with your position.
| |
| | |
| ==== LuckPerms ====
| |
| | |
| * <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.
| |
| * <code>/lp editor [type]</code> - Opens a website interface to edit permissions data. After changes are saved, a command will be given that you need to run for the changes to take effect.
| |
| ** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.
| |
| | |
| ===== User Commands =====
| |
| | |
| * <code>/lp user <user> info</code>
| |
| * <code>/lp user <user> permission</code>
| |
| * <code>/lp user <user> parent</code>
| |
| * <code>/lp user <user> meta</code>
| |
| * <code>/lp user <user> editor</code>
| |
| * <code>/lp user <user> promote <track> [context...]</code>
| |
| * <code>/lp user <user> demote <track> [context...]</code>
| |
| * <code>/lp user <user> showtracks</code>
| |
| * <code>/lp user <user> clear [context...]</code>
| |
| * <code>/lp user <user> clone <user></code>
| |
| {{Note|type=reminder|text=<b>Tip</b><br> | |
| Add in-game roles via <code>/lp user <user> parent add <job></code>}}
| |
| | |
| ===== Group Commands =====
| |
|
| |
| * <code>/lp group <group> info</code>
| |
| * <code>/lp group <group> permission</code>
| |
| * <code>/lp group <group> parent</code>
| |
| * <code>/lp group <group> meta</code>
| |
| * <code>/lp group <group> editor</code>
| |
| * <code>/lp group <group> listmembers [page]</code>
| |
| * <code>/lp group <group> setweight <weight></code>
| |
| * <code>/lp group <group> setdisplayname <name></code>
| |
| * <code>/lp group <group> showtracks</code>
| |
| * <code>/lp group <group> clear [context...]</code>
| |
| * <code>/lp group <group> rename <new name></code>
| |
| * <code>/lp group <group> clone <name of clone></code>
| |
| | |
| ===== General =====
| |
| | |
| * <code>/tps</code>- check the ticks-per-second (tps). The go to command to check for server lag. <code>/whois</code> - useful for finding a players IP if you wish to ban their IP.
| |
| * <code>/socialspy</code> - able to see players private messages.
| |
| | |
| ===== Crates =====
| |
| | |
| * You can replace players' crate keys by running <code>/crate key give <user> <crate></code> .
| |
