TaterComms
A simple, cross API plugin that bridges communication between servers, using built-in Proxy methods, Discord channels and TCP sockets.
Link to our support: Discord
Download
Usage
- Configuration guide wiki entry
- Create and add a Discord bot to your server
- The bot will need permissions to read and send messages with whatever permission scopes you set up, and in the channels you want to use
Known Issues
- Under certain circumstances with a proxy, prefix/suffix information is not read correctly, still narrowing down the cause
- Global chat still needs some tweaking and a proper, per-user toggle
- Sponge death messages are a tad off with how the component serializes (eg:
playerName Skeleton was shot by
instead ofplayerName was shot by Skeleton
) - Still need to tweak the pass-through system and get that working properly
- Some implementations fire the shutdown event after the plugin unloads, so the shutdown message doesn’t get sent
- Bukkit 1.6.4 doesn’t have an advancement event
- Bukkit b1.7.3 doesn’t support the following
- proper death/advancement events
- plugin messaging
Dependencies
Optional Dependencies
- LuckPerms - For permissions/prefix/suffix support
Compatibility Cheatsheet
TaterComms supports: Bukkit, Bungee, Fabric, Forge, Sponge, and Velocity
Server type | Versions | Jar Name |
---|---|---|
All 1.20 (Sponge11) | 1.20-1.20.2 | TaterComms-1.20-<version>.jar |
All 1.19 (Sponge10) | 1.19-1.19.4 | TaterComms-1.19-<version>.jar |
All 1.18 (Sponge9) | 1.18-1.18.2 | TaterComms-1.18-<version>.jar |
All 1.17 (Sponge9) | 1.17-1.17.1 | TaterComms-1.17-<version>.jar |
All 1.16 (Sponge8) | 1.16-1.16.5 | TaterComms-1.16-<version>.jar |
All 1.15 (Sponge8) | 1.15-1.15.2 | TaterComms-1.15-<version>.jar |
All 1.14 | 1.14-1.14.3 | TaterComms-1.14-<version>.jar |
Commands and Permissions
Command | Permission | Description |
---|---|---|
/tatercomms reload | tatercomms.admin.reload | Reload the plugin |
/discord | tatercomms.command.discord | Get the Discord invite link |