d5ffed09b4
Fixes #1337 😎 This PR fixes tab completions for all of the home commands in Essentials. Prior to this PR, the behavior is approximately as follows: - `/sethome` has no implementation for completions, and so it provides player names, which isn't very useful, and in my opinion can cause more harm than good by confusing users. - `/home` and `/delhome` fail to provide valid completions when a user has the `essentials.home.others` permission. The argument syntax is `[player:]<name>` but it tries to complete it as `<player> <name>`. Not only does it not show you suggestions for your own homes, but it proceeds to show you invalid suggestions! This PR provides completions that accurately reflect the syntax and real behavior of the command, including suggesting homes for player names that are partially matched. It will provide suggestions for all of your own homes, as well as providing suggestions based on how far along you are in the command (players if you haven't specified `:` yet, otherwise a specific player's homes). |
||
|---|---|---|
| .github | ||
| Essentials | ||
| EssentialsAntiBuild | ||
| EssentialsChat | ||
| EssentialsGeoIP | ||
| EssentialsProtect | ||
| EssentialsSpawn | ||
| EssentialsXMPP | ||
| nms | ||
| scripts | ||
| .gitignore | ||
| crowdin.yml | ||
| LICENSE | ||
| pom.xml | ||
| README.md | ||
This is a fork of Essentials called EssentialsX.
If you are using this, do NOT ask Essentials for support.
The official upstream repository is at https://github.com/Essentials/Essentials.
Why use EssentialsX?
EssentialsX is an unofficial continuation of Essentials, updated to support modern Minecraft and Spigot versions. It provides several performance enhancements and fixes that are currently not available in Essentials and Spigot-Essentials. For more details, see the wiki.
EssentialsX is almost a completely drop-in replacement for Essentials. However, it has different requirements:
-
EssentialsX requires Vault to enable chat prefix/suffixes and group support if you have a supported permissions plugin. We recommend using LuckPerms.
-
If you have an unsupported permissions plugin but still wish to use wildcards, enable
use-bukkit-permissionsin the configuration. Otherwise, the plugin will fall back to config-based permissions. -
EssentialsX requires Java 8 or higher. On older versions, the plugin may not work properly.
-
EssentialsX supports Minecraft versions 1.8.8, 1.9.4, 1.10.2, 1.11.2, 1.12.2, 1.13.2, 1.14.4, and 1.15.2.
Support
Need help with using EssentialsX? Join the MOSS Discord community to ask for help and discuss EssentialsX.
If you need to report a bug or want to suggest a new feature, you can open an issue on GitHub.
Building
EssentialsX builds against the Spigot/CraftBukkit server software for legacy support.
To compile EssentialsX, you first need to run BuildTools. This only needs to be done once. There are two ways to do this:
- Use the provided script at
scripts/buildtools.shto automatically download and run BuildTools if needed. - Download and run BuildTools yourself for versions
1.8and1.8.3.
Next, to build EssentialsX with Maven, run the following command:
mvn clean install
Each module's jar can be found in target/ inside each module's directory.
Using EssentialsX in your plugin
Writing a plugin and want to support EssentialsX? We have a Maven repository at https://ci.ender.zone/plugin/repository/everything/, and the EssentialsX artifact is net.ess3:EssentialsX:2.17.0. More information at the wiki.
Contributing
Want to help improve EssentialsX? There are numerous ways you can contribute to the project.
If you'd like to make a financial contribution to the project, you can join our Patreon. If you can't make a donation, don't worry! There's lots of other ways to contribute:
- Do you run a server? Take a look at our "help wanted" issues, where you can find issues that need extra testing and investigation. You can also join the MOSS Discord community and provide support to others.
- Do you speak multiple languages? If so, we always welcome contributions to our Crowdin project.
- If you're a developer, you could look through our "open to PR" issues. We're always happy to receive bug fixes and feature additions as pull requests.