Tags
Creators
Details
3.2.0
Compatibility
Changes
Features!
Channels
Introducing the new Channels Feature! Add Places or Players or both if you would like! Into each other and priortize them from top to bottom according to the importance of each channel!
GlobalSending: true
channels:
admin:
players:
- "OmarOmar93"
- "HoneySalted"
- "Notch"
places:
- "World"
- "Lobby"
main:
places:
- "world"
- "world_nether"
- "world_the_end"
Debug Mode - (Implemented in Channels only Currently)
The New Debug mode is what prints out more information about WorldChatter! like, Warnings, Errors and infos for each action happening inside the plugin!
debug:
enabled: true
info: "&7[&9WorldChatter Debugger &r| Info&7]&r "
warning: "&7[&9WorldChatter Debugger &r| &eWarning&7]&e "
error: "&7[&9WorldChatter Debugger &r| &4Error&7]&4 "
Changes!
- The Built-in Placeholders of WorldChater are now using { } instead of this symbol % to make both WorldChatter and PlaceHolderAPI Work Together without interfering.
{player_name_raw}and{player_place_raw}are implemented to get the non formatted name of those instead of the aliases formatting them and with multiverse-core a brand new placeholder called{player_mvworld}- Added a new Hex code translator for MiniMessage
�-><#000000> - Changed how cancelling event works in Spigot and Bungeecord by removing receptients instead of cancelling the event
- Delayed the chat events to be the lowest priority in both proxies to be able to let the other plugins work.
- Listeners are Addons are now isolated in the API Meaning you can create addons or Listeners (creating listeners no longer requires an addon!)
- Added event cancel check before executing WorldChatter's Chat System (Bungeecord and Spigot)
- Lots of code optimization.
- Lots of Under-the-hood Changes.
Bug fixes!
- Fixed bugs found by the community related to the Following [Plugin incompatibility with Events, Join and Quit and Others i forgot cuz they were alot of bugs.]
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:12lXE0dp:dsK6kuIj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:12lXE0dp:dsK6kuIj"
}

