Necrify is a punishment plugin designed for currently
Velocity (and
maybe Paper/BungeeCord in the future).
- Download the latest version of the plugin or download dev builds here (may be unstable or not working)
- Put the downloaded file into the
plugins
folder of your server. - (Re-)Start the server.
With the 1.19.1, Minecraft's chat system got
changed (detailed explanation).
Since then, it is no longer possible to block chat messages in the ChatEvent of Velocity due to the signed chat
messages.
This is why the chat listener does not block any messages anymore which means mutes are effectively useless. A solution
to this problem is developing an extension plugin for the actual game servers where cancelling these messages is still
possible. Downloads for this paper plugin are found in
the releases and also
as dev builds on Jenkins.
For further information about 1.19.1, please refer to
the official release notes
All commands are registered with the prefix /necrify
. Moreover, it is possible to register top-level commands too by
setting allow-top-level-commands
to true (which is per default)
legend:
- <arg> means the argument is required
- [arg] means the argument is optional
- player as argument name means the a player name OR uuid is required
- reason means a reason that supports MiniMessage
- duration as argument name means a duration
- /ban <player> [reason] bans a player permanently for the given or the default reason
- /mute <player> [reason] mutes a player permanently for the given or the default reason
- /tempban [reason] bans a player for the given duration for the given or the default reason
- /tempmute [reason] mutes a player for the given duration for the given or the default reason
- /unban unbans the given player
- /unmute unmutes the given player
- /necrify user <player> <info|delete|whitelist> shows either information about a player's punishments and his whitelist status, deletes this user including all punishments or inverts his whitelist status (from whitelisted to blacklisted or vice versa)
- /necrify punishment <punishment id> <cancel|change|info|remove> cancels/removes, changes or shows information about the given punishment(must be a uuid)
To be parsed by PunishmentDuration#parse(String)
, a string must follow this scheme:
[0-9][s, m, h, d]
s - second(s)
m - minute(s)
h - hour(s)
d - day(s)
These value can be composed, all of them can be omitted.
Example: 1d12h15m30s means a duration of 1 day, 12 hours, 15 minutes and 30 seconds.
Replace {version}
with the current version, e.g. 1.0.0. The latest version can be found here.
Note that you only want to use the string after necrify-{platform}- and without the version build number.
repositories {
mavenCentral()
}
depenencies {
implementation("de.jvstvshd.necrify:necrify-api:{version}")
}
repositories {
mavenCentral()
}
dependencies {
implementation 'de.jvstvshd.necrify:necrify-api:{version}'
}
<dependencies>
<dependency>
<groupId>de.jvstvshd.necrify</groupId>
<artifactId>necrify-api</artifactId>
<version>{version}</version>
</dependency>
</dependencies>
You can also depend on the plugin modules or common module. In order to do so, replace the artifactId with the desired module name. Note that code outside the API module is always subject to change and may not be stable. It is also not designed to allow access and modifications from outside the plugin itself and is often not documented.
If the plugin is used, you can obtain an instance of the api using the following snippet:
try {
Necrify api = (Necrify) server.getPluginManager().getPlugin("necrify").orElseThrow().getInstance().orElseThrow();
} catch(NoSuchElementException e) {
logger.error("Punishment API is not available");
}
All punishments are issued via the target user. For example, banning a player could be done this way:
//Firstly, obtain the user instance
NecrifyUser user = api.getUserManager().getUser(uuid).orElseThrow(() -> new NoSuchElementException("User not found"));
MiniMessage miniMessage = MiniMessage.miniMessage();
//temporary ban:
Ban temporaryBan = user.ban(PunishmentDuration.parse(miniMessage.deserialize("<red>You broke the server's rules! Don't cheat!"), PunishmentDuration.parse("1d"))).join();//1d equals 1 day, the duration is relative to the current time until the punishment is imposed.
//permanent ban:
Ban permanentBan = user.banPermanent(miniMessage.deserialize("<red>You broke the server's rules again! You are not allowed to join someday again!")).join();
//The ban instance you get via #join is the punishment that was issued. Note that using #join blocks the current
//Thread and since database operations take some time to complete, it is recommended to use #whenComplete or other.
//You can now use this instance to change or cancel the punishment:
temporaryBan.cancel().whenComplete((punishment, throwable) -> {
if(throwable != null) {
logger.error("An error occurred while cancelling the punishment", throwable);
return;
}
logger.info("The punishment was successfully cancelled");
});
//#cancel should always return the same instance that you called the method on
//Event tough a permanent ban was issued for an indefinite time, you can still change the duration and the reason:
permanentBan.change(PunishmentDuration.parse("300d"), miniMessage.deseriaize("<green>Okay, you may join again in 300 days!")).whenComplete((punishment, throwable) -> {
if(throwable != null) {
logger.error("An error occurred while changing the punishment", throwable);
return;
}
logger.info("The punishment was successfully changed");
});
Muting a player is similar, just replace 'ban' with 'mute'.
Kicking a player can be done by calling user.kick(Reason).join();
where it is safe to call #join since there is no
database query done synchronously. This form of punishment cannot be changed nor cancelled as it only lasts a single moment.