SimpleCrossChatPlus V0.1
Easy cross-server chat, entity/item/money transfer, no BungeeCord or proxy needed!
SimpleCrossChatPlus
SimpleCrossChatPlus is the ultimate solution for cross-server communication and data transfer in Minecraft networks. Whether you run a large network, a small community, or a private server cluster, this plugin brings your players together like never before.
Use Cases
- Minigame Networks: Keep players connected across lobbies and game servers
- Roleplay Communities: Share stories and items between themed worlds
- Survival/Creative Clusters: Trade, chat, and transfer resources seamlessly
- Private Server Networks: Maintain privacy and control with your own broker
Why choose SimpleCrossChatPlus?
- Innovative cross-server features
- Secure, encrypted communication via MQTT
- Granular permissions for full control
- Simple configuration and plug-and-play setup
- Compatible with Minecraft 1.16.5+ and Java 16+
Privacy & Security
Messages are encrypted and transmitted via your chosen MQTT broker. For maximum privacy, host your own broker. Only global and cross-server messages are sent—other plugin messages remain local. Vault integration activates money transfer.
Configuration
Easy to set up: just drop the plugin in your folder, configure your broker and server name, and you're ready to go! Advanced options allow you to customize message formats, debug output, and more.
FAQ
- Who is this for? Any Minecraft admin who wants seamless cross-server communication and data transfer without bungeecord OR together with bungeecord for the easiest entity/item cross-server transfer YET!
- Is it secure? Yes, messages are encrypted but you can also host your own broker to make it even more secure.
- Is setup easy? Yes, plug-and-play with simple config options to control everything.
Version Compatibility
- Old to new Minecraft versions: Transfers work most often without problems, as newer versions can read and upgrade legacy data formats for entities and items.
- New to old Minecraft versions: Transfers are basically not reliable due to NBT/data differences—items usually fail, but some entities may work if their type and properties exist in both versions.
- Same version: Transfers between servers running the same Minecraft version work as expected.
Connect your servers. Connect your players. Connect your community.
Disclaimer
SimpleCrossChatPlus transmits messages via your chosen MQTT broker. While encryption is used, privacy and security depend on your broker setup. The developer cannot be held responsible for misuse, data interception, or legal issues. It is the sole responsibility of the server owner to ensure correct, secure, and compliant usage of this plugin.
Command Security
The `/scc get` command allows anyone with the unique redeem ID to claim the associated entity or item. This can be both advantageous and risky, depending on the use case. Users must exercise caution and only share redeem IDs with trusted individuals.
SimpleCrossChatPlus - Technical Documentation
Configuration Overview
All settings are managed in the options.yml file in your plugin folder. This file controls every aspect of the plugin’s behavior, from broker connection to chat formatting and feature toggles.
Example options.yml
[code]donottouch:
configexists: true
debug:
showmessages: false
general:
info: '- INFO: id and key have to match on other servers, to enable a global chat, one value different and it wont work'
servername: YourServerName
broadcastmessageformat: '&a%PLAYER% &0| &f%MESSAGE%'
enabled: true
privacyinfo: '- INFO: Even tho the messages are not readable for outstanders, I would host my own broker for a safe communication!'
technical:
broker:
address: broker.emqx.io
protocol: tcp
port: 1883
communication:
channel:
id: examplechannelonthebroker
key: z87d3z8hde3z8
...more options...[/code]
Config Value Explanations
- broker.address: The MQTT broker address. Use a public broker for testing, but a private broker for production.
- broker.protocol: Choose tcp for standard or ssl for encrypted connections.
- broker.port: The port your broker listens on (default: 1883 for tcp).
- general.servername: Unique name for your server, shown in cross-server messages.
- broadcastmessageformat: Customize how global chat messages appear.
- debug.showmessages: Enable to see debug output in your console/logs.
- communication.channel.id/key: Must match across servers to enable communication. Change for privacy.
- enabled: Toggle global chat and other features on/off.
How it works
All (configured) content and cross-server messages are sent through the broker, encrypted for privacy. You can disable global chat or other features to limit data transmission. Vault integration enables money transfer.
Permissions
Use permissions to control who can transfer entities, items, or money. Example:
- sccplus.admin.*
- sccplus.entity.transfer
- sccplus.entity.tier.owned
- sccplus.entity.tier.animals
- sccplus.entity.tier.everything
MQTT Broker Setup
- Public Broker: Quick setup, but less privacy. Use for testing.
- Private Broker: Recommended for production. Host your own for full control and security.
- Toggle features per server or per player.
Troubleshooting
- If messages aren’t sent, check broker address and port.
- Ensure channel id/key match across all servers (or else communication and encryption/decryption is not possible)
- Verify Vault is installed for money transfer.
Step-by-Step Guides
1. Place the plugin JAR in your plugins folder.
2. Edit options.yml to match your broker and server settings.
3. (Optional) Install Vault for economy features.
4. Restart your server.
5. Test global chat and cross-server features.
6. Adjust permissions for staff and players.
Admin Tips
- Host your own broker for maximum privacy and control.
- All configuration is non-technical and can be managed by server admins—no coding required.
- Use permissions to restrict sensitive features.
- Regularly update your plugin for new features and security.
FAQ
- Can I use this with any server type? Yes, supports all major server types.
- Is Vault required? Only for money transfer and if you want people to pay for transfers.
- How do I secure my communication? Use a private broker.
- Can I disable features? Yes, certain features have a toggle in options.yml.
Version Compatibility
- Old to New: Transfers from older Minecraft versions to newer ones work most often without problems. Newer versions can read and upgrade legacy data formats for entities and items.
- New to Old: Transfers from newer to older versions are unreliable. Items usually fail due to NBT/data differences, while some entities may work if their type and properties exist in both versions.
- Same Version: Transfers between servers running the same Minecraft version work as expected.
Command Security
The `/scc get` command allows anyone with the unique redeem ID to claim the associated entity or item. This can be both advantageous and risky, depending on the use case. Users must exercise caution and only share redeem IDs with trusted individuals.
Simple, secure, and powerful cross-server communication for every Minecraft admin.
