ServerUtil

Description

A rather simple command utility mod, adds a few commands I felt could be useful on their own. Can be, but doesn’t need to be installed on client if playing in a client-server scenario.

Commands:

1. “tpx” for inter-dimensional teleportation

   /tpx (target entity) (destination entity) OR /tpx (target entity) (dimensionId) [ <x> <y> <z> ]

2. “dimensionlist” to list registered dimensions with id, name and subfolder name in save directory

   /dimensionlist

   Example output:

    overworld, id: 0
    the_nether, id: -1, subfolder: "DIM-1"
    the_end, id: 1, subfolder: "DIM1"

3. “regioncoord” to determine region file and chunk coordinates containing specified x and z

   /regioncoord <x> <z>

   Example output:

    Region file name: r.3.4.mca, chunk coord: 112, 132

4. “motd” - enables simplistic server MOTD functionality, which by default shows the configured message to players on login. File (MINECRAFTDIR/serverutil-motd.txt) is generated on startup automatically, or can be created manually. Has to be UTF-8, but additionally supports standard Minecraft format codes. Players can opt out from receiving motd, ops can opt out others.

   /motd [reload]

   /motd ( enable | disable ) [ username | uuid ]

   Example output:

   

   Example file contents:

    §nWelcome to the server!
    This is an §aexample§r greeting message
    §nMinecraft Formatting
   
    §r§00 §11 §22 §33
    §44 §55 §66 §77
    §88 §99 §aa §bb
    §cc §dd §ee §ff
   
    §r§0k §kMinecraft
    §rl §lMinecraft
    §rm §mMinecraft
    §rn §nMinecraft
    §ro §oMinecraft
    §rr §rMinecraft

5. “playerid” - get either a player’s current username and their unique id (Only works properly with online-mode=true in server.properties), caches results.

   /playerid ( username | uuid )

   Example output:

    Notch, 069a79f4-44e9-4726-a5be-fca90e38aaf5

6. “mod_bugs” - utility to store known bugs in a json file for players to be aware of, using a generalized chat command. Configurable permissions on command functions, by default anyone can view bugs with /mod_bugs, but only ops can do manipulations.

   /mod_bugs add (name) (who discovered/associated player) [description]

   /mod_bugs person <name>

   /mod_bugs reload

   /mod_bugs remove <name>

   /mod_bugs update <name> < description | status >

   status can be one of: “relevant”, “fixed”

   Example output:

   

P.S. This is my first mod release, please don’t yell if something’s wrong :P

This mod is okay to be used in modpacks, but please drop me a message if you do. Thanks!

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install