Bukkit

Convenience Commands

Keeping LumenTech up-to-date

Quote from Disclaimer:

This feature is disabled on the Bukkit release build!

Often times an update to Craftbukkit will break certain plugins because they rely on Craftbukkit or NetMinecraftServer code. These APIs change on every release, thus throwing errors into your server log if not handled correctly. For LumenTech, all methods which use Craftbukkit/NMS code are safeguarded. If your current server version is inconsistent with the version used to create the plugin, the plugin features utilizing CB/NMS will be disabled to prevent throwing needless errors. Use '/lt update' to check for new updates to LumenTech. You can select dev builds in your config if you want to live on the cutting edge (dev builds are unstable).

Setting the MOTD

What is a MOTD, MOTDX or MOTDZ?

MOTD stands for "Message of the Day". Server MOTDs are those server messages that appear in your server list. They can be colored, or plain text. To change a server MOTD you would normally change it in the server.properties file. LumenTech listens to the ServerListPingEvent, and alters the MOTD when told to do so. Because the ServerListPingEvent also requires an IP to be sent to the server, it is possible to match a player name to the connecting IP if they have been to your server before. A MOTDX takes advantage of this and includes a connecting player's NAME in the MOTDX. MOTDX takes higher priority over MOTD, and MOTDZ takes higher priority over MOTDX. MOTDZ is a motd that only shows itself to a single player of your choosing.''' Below is an example of a MOTD, MOTDX, and MOTDZ (respectively).

Defaults Via Config

By editing the configuration you decide if LumenTech's MOTD should take the place of the default MOTD. When enable-by-default-this-motd is set to true, LumenTech will override the default MOTD upon loading the plugin. When ''enable-by-default-this-motdx'' is set to true, LumenTech will override the default motd if a player has been to the server before. You can also configure some of the lockdown messages as well.

In-Game Via Commands

Quote from Commands for setting the MOTD in-game:

1. do the motd commands without a message of the day to set the value back to the default.
2. /lt motd <message>
3. /lt motdx <message containing %name%>
4. /lt motdz <player name or IP address> <message>

Capslock Control

/capsoff <name> and /capson <name> can both be used to control whether or not certain users are allowed to use caps.

PolySend

Perms

I don't like having to visit a wiki to figure out which permission nodes are needed to do something. Use /lt perms to get a print-out of all permissions used by the plugin. Additionally, if a user is ever forbidden from doing something, the plugin will tell them exactly which permission node they lack.

Chat As

/ca <name> <message> Force someone to chat or execute a command.

Help Pages

/lt <#> shows the different commands available in LumenTech.

Offline Teleport

/otp <name>

About

/lt about shows info about the plugin and a link back to this wiki.

Command Shortcuts

You can create customized command shortcuts using the command shortcut configuration section.

The key in the config becomes the command, and %vars% is replaced by your command arguments. So if I wanted to roll back a griefer using core protect, normally I would use /co rollback u:Griefer t:99d. Using a command shortcut, I would be able to do /corollback Griefer instead. A bit faster, and it will save you some trouble on commands lacking autocomplete. /rollback griefer becomes : /lb rollback player %vars% time 99d , or /co rollback u:%vars% t 99d - depending on what you have written in your config file.

SSH Command

/ssh <ssh command> so /ssh dh -h,

or /ssh ./somefile.c

or /ssh du max-depth=2 -ha ./

Offline mode Toggle

/omode <true/false> This command will set your online mode without the need for a server reboot. Useful for when the minecraft login servers are down and not functioning properly. However, you must take extreme caution when putting your server into offline mode, as it leaves your server open to security vulnerabilities. Lockdown commands can help close some of those security holes. Also, be careful about a reload, because a reload would cause the lockdown mode to reset to zero. I will probably change the code around so that lock-downs persist through reloads later.

Quote from DISCLAIMER:

This is not available in the Bukkit release build.

In compliance with the submission guidelines, it should be known that the ability to toggle the online mode of a server is not an attempt to aid cracked servers. Cracked servers would have no use for online mode, and any IP based lockdown ability provided by LumenTech would only limit their own community sizes. /omode is to be used in combination with /lockdown -1 or /lockdown -2 in times of emergency, or when the minecraft login servers are malfunctioning. The intent is to level the playing field so that usually "online" servers can still function in the midst of a login-server failure.