ChatEvents v0.6

Details

  • Filename
    ChatEvents.jar
  • Uploaded by
  • Uploaded
    Feb 27, 2015
  • Size
    9.37 KB
  • Downloads
    293
  • MD5
    814ba70996cbbf9b1acf1e0e77cff7fb

Supported Bukkit Versions

  • 1.8.1

Changelog

Warning

This version is VERY unstable!! Be careful before downloading it!!
If you want to install this on your server you should probably download VERSION 0.7 instead!
This version has a lot of bugs, and the events doesn't event work!!
Most of these bugs have been fixed in version 0.7, so please, don't use this one.

Changelog

Added per-player management
Added {VIEWER}, {VIEWERNAME}, {VIEWERCUSTOM} and {VIEWERTAB} variables
Added configurable priority for the event (for maximum support with Factions and other plugins)
Added option to disable each event (used for maintenance or testing for exemple)
Made it easier to create a Module
Removed empty strings in JSON to make it "cleaner"
Rewrote Module.java to add documentation and per-player compatibility

Modules

Before

ChatEvents.addModule(new Module("test") {

	@Override
	public String getValue (Player player) {
		return "Hello, World!";
	}

});

After

new Module("test") {

	@Override
	public String getValue (Player player, Player viewer) {
		return "Hello, World!";
	}

};

Changes

  • ChatEvents.addModule still works, but you don't need to use it while creating a variable.
  • New argument added: Player viewer = The player to which this message will be sent to.

#1: The {MESSAGE} variable will always be in white, no matter what color code is before.
#1 (bis): If the color code for the player name isn't inside the {[...]}, the name will show as white.
#2: The event will never fire unless you put an invalid priority
#3: The "new" variables are not implemented yet
#4: The events for the "username" part apply to all the message because of the cleaner JSON
#5: When several players are connected, the plugin is messing up the JSON
#6: If the priority set in config is invalid, the event will trigger 6 times