4.1.0latest4.1.0 - Code ChangesFeb 9, 2020 There has been no new features or changes to existing features in this update. The only changes have been in the code. This will make it MUCH easier to make changes to the code in the future. If you want to know more about the changes that I made, you can read the spoiler below. .SpoilerTarget">Spoiler: Change Log 4.1.0 - The plugin now has 5 classes to make it more organized. This is an upgrade from the previous two. - More comments have been added to the plugin, but I'll admit there is still not nearly enough. This may come in the future. - Previously, I was using a complicated method to replace (config) variables with their values. I recently discovered that Java can do that for me using the .replaceAll method. There will likely be a future update that fixes everything more Please report all bugs to me as I have not fully tested the plugin, and have only tested the newest version on 1.14.4.4.0.14.0.1 - Bug FixesJan 17, 2020 - Case no longer matters in command arguments - Added [GreetingCommand] prefix for "You can only run that command if you are a player!" message - Added "You can only run that command if you are a player!" message to the /replytogreeting command4.0.0RELEASE 4.0.0Jan 16, 2020 PLEASE! Upgrade IMMEDIATELY! 3.2.0 has quite a few bugs! Change Log 4.0.0 - Made the plugin a lot more organized, and therefore easier to expand on in the future. I will likely do more of this in future version. The file size has also been reduced. - Fixed bug where sending /greet from the console caused an ArrayIndexOutOfBounds exception. - Added a non-configurable message: "You can only run this command if you are a player" for the /greet command (not for arguments reload and version) - Fixed permission issues. - Added a setting to the config (settings: permission: per-reply: ) that allows server admins to decide whether or not they want to be able to control what moods players can use with permissions (greet.reply.<mood>). By default, this setting is false, and players are given access to all moods defined in the config file. - Changed some of the default config messages If you are upgrading from an earlier version, you will need to add the following code to your config file: Code (YAML): settings: permission: per-reply : false3.2.03.2.0 - New messages configurationJan 15, 2020 - Added configuration for new permissions messages, as well as /greet version and /greet reload. - Added the {permission} and {version} variables in the config file. A side note (please read): Due to the plugin being badly coded, difficult to expand, and having numerous bugs and inabilities, I will be spending likely a few days doing a lot of recoding. There will not be much in terms of features in the next update, but it will be infinitely easier to make changes in the future, as well as allowing me to fix simple, but annoying bugs.3.1.0Permissions + CommandsJan 14, 2020 Hello! I have finally been able to work on releasing version 3.1.0 of the GreetingCommand plugin. Here are a list of the new features: - Added permissions for all commands --- greet.version --- greet.reload --- greet.greet --- greet.reply --- greet.reply.<mood> - Some permissions are given by default, so no permission configuration is required --- greet.greet --- greet.reply --- greet.reply.* --- (Please see the main resource page for more information) - Added /greet version command: Shows the version of the plugin as well as the author. - Added /greet reload command: Reloads the config file.3.0.13.0.1 - Minor TweaksJan 12, 2020 - Made some small changes to the config.yml file. You will not have to make any changes if upgrading from an older version. - Fixed "Loaded GreetingCommand v2.2.0" when plugin loaded despite the plugin version being 3.0.0.3.0.0RELEASE 3.0.0 - Major Config UpdateJan 12, 2020 - Added the ability to add new moods in the config file! - Added the {moods} variable to the config file. The {moods} variable will now be replaced by a list of all configured moods. If you upgrade to this version, your current config file WILL NOT work. Please look at the main resource page for instructions.2.2.0Huge Config Updates!Jan 11, 2020 Changes in this update include: - Added config options for almost all messages! Note: If you are upgrading from an earlier version of the plugin, you will have to either regenerate your config or add the new options. A full copy of the config can be found on the main resource page. - Removed some unnecessary code - Allowed the {player} variable to be used in all messages (even prefixes) - Fixed bug that let console and command blocks run the /replytogreeting command, then created an internal error2.1.1Bug Fix - 2.1.1Jan 11, 2020 - Config comments needed to be changed2.1.0ColorsJan 11, 2020 In the latest update (2.1), I have introduced color codes into the config! You can also change the prefix for the broadcast in chat when a player replies. PLEASE READ IF UPGRADING FROM AN OLDER VERSION: You will need to update your config if you are switching from an older version or the config WILL NOT work! Read the spoiler below for instructions: .SpoilerTarget">Spoiler: Instructions if switching from older version Your first option is to delete the config and reload/restart the server and a new one will be generated. However, if you don't want to do that, there is another option: Add 2 spaces in front of each of the greeting reply messages and add "replies:" on the line above it (see code below). Code (YAML): replies: amazing : "&6{player} &2is doing &aAMAZING&2!" good : "&6{player} &2is doing &agood :)" eh : "&6{player} &2is not doing &agood&2, nor is he/she doing &cbad&2." bad : "&6{player} &2is doing &cbad :(" terrible : "&2Oh no! &6{player} &2is doing &4TERRIBLE! &2You probably want to stay away from him/her!" none : "&6{player} &2does not have a mood." You should then add the following code to your config file so you can change the prefix in reply broadcasts: Code (YAML): prefix: replytogreeting : "&7[&aGreetingCommand&7] " If you still have problems, you can look at the config (posted on the main resource page) and use the same structure it has while keeping your custom messages. Feel free to contact me here on spigot with any other questions!2.0.1Minor Changes - 2.0.1Jan 5, 2020 - Fixed bug where the {player} placeholder could not be used twice in the same message. - Changed message sent to the player in /greet so it is more obvious the message is from the GreetingCommands plugin. Also, I changed the color coding to highlight the responses and the /replytogreeting command.RELEASE-2.0.0Official Release - Update 2.0.0 - Config.yml UpdateJan 5, 2020 Hello! Finally, version 2 of the plugin has released! This update brings a config.yml file: - Change greeting replies - Use the {player} variable to specify where the player's name will be - Color codes not yet supported (likely coming in 2.1) I have also made the code a bit better to make it easier for me to expand the plugin in the future!1.0.3ULTRA Bug Fix - 1.0.3Jan 5, 2020 - Fixed the bug that caused an internal error when running /replytogreeting without arguments for the second time. Apparently my first fix was not sufficient. - Fixed bug that caused both the "usage" and "invalid mood" error to show up at the same time when there are no arguments. - Fixed color codes in the "usage" error. Next version should be 2.0.0. It will come with some major changes!1.0.2Internal Error Bug Fixed - 1.0.2Jan 5, 2020 - Fixed bug where players get an internal error if they don't enter any arguments in the /replytogreeting command. New update (version 2) coming soon! Stay tuned!1.0.1Bug Fix - 1.0.1Jan 5, 2020 · Fixed bug where responses had to be lowercaseRELEASE-1.0Official release - update 1.0Jan 5, 2020 In this update, the command /replytogreeting was added allowing players to reply to the plugin's greeting. The plugin will display in chat a message correlating to the greeting the player entered.BETA-1.0Jan 5, 2020
Similar projects
Plugin →Let Me Despawn
Improves performance by tweaking mob despawn rules. Say bye to pesky unintentional persistent mobs.
25MSueta
JourneyMap
Real-time map used for mapping in-game or your browser as you explore.
14.7MSueta
Emotecraft
Create your own emotes in Minecraft.
7.5MSueta
Simple Tpa
A simple tpa plugin which sends requests
5.4MSueta
Common Network
Forge and Fabric Unified Networking Solution
3.9MSueta
Set Home
A lightweight plugin for players to set their homes.
3.8MSueta