WorldEventComms

A Wynncraft mod for easily communicating world events to party members.

56 Downloads

fabricsocialutility

About this Mod

WorldEventComms is a simple client mod for Wynncraft that adds commands to help you communicate your tracked world event to the rest of the party to make sure everyone is on the same page.

The commands that can be used are below:

/we next: Sends your currently tracked world event to party chat.
/we busy: Sends information about the ongoing world event to party chat.
/we none: Disappoint everyone by telling them there's no active world events.

Partially compatible with Wynntils, almost.

Yes, the icon is a placeholder. I'm not a graphic designer.

Available Versions

WorldEventComms 1.0.1+1.21.11release

MC 1.21.11fabric

May 14, 2026

How to Install WorldEventComms on Your Server

Order Server

Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).

Set fabric Loader

In the panel under "Egg", select the fabric loader and matching Minecraft version (1.21.11).

Install Mod

Open the mod browser in the dashboard and search for "WorldEventComms". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.

Compatibility

Mod Loaders

fabric

Minecraft Versions

1.21.11

Server-side

✗ Unsupported

Recommended RAM

4 GB(min. 3 GB)

Frequently Asked Questions

WorldEventComms server crashes on startup – what to do?

Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.21.11). You can switch loaders with one click in the panel.

Is WorldEventComms compatible with fabric?

WorldEventComms officially supports fabric for Minecraft 1.21.11. The Mado dashboard automatically detects incompatible loader combinations.

Server lagging with WorldEventComms – how to optimize performance?

Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if WorldEventComms consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.