ASA Event Notifier DC
The Discord half of Shadow Events Notifier. The plugin watches your world, this turns what it sends into proper Discord embeds - your channels, your wording, your colours.

READ THIS FIRST - this addon is free. Its a ShadowBot addon, so you enable it from the Addons page and thats the whole install. What it needs is the other half: the plugin needs the events_notifier_dc licence key before it will send anything out. No plugin, no events, and this has nothing to listen to.

Setup - Enable it from the Addons page. No licence key, no database, no RCON, no dependency on any other addon
One shared token secures both receivers, the player one and the world one. Generate it on the dashboard, paste it into the plugin config
Until you set a token every inbound request is refused, so it ships switched off instead of sat there open
Everything is per Discord server, so one bot feeds several communities off the same cluster

Player Events - Eight of them. Login, logout, death, tribe join, tribe leave, tribe created, tribe renamed and new characters
Each one has its own switch, its own channel and its own embed. Theyre not one shared feed you have to filter by eye
Login and logout are on out of the box. The other six are off, so enabling this doesnt start posting stuff nobody asked for
Death is off on purpose - its the loudest event on a busy cluster and its a decision you should make deliberately, not inherit
Deaths carry no killer, no cause and no location. The position isnt hidden from the embed, its never read out of the payload at all - a death spot is where the loot bag is

World Events - Supply drops, orbital drops, element veins, wild fertilized eggs and bosses
Unlike the eight player events these arent a fixed list. Theyre rules you add
One rule per spawn code, each with its own channel and its own embed, so SupplyCrate_Level03_C can go somewhere different to the white ones
Add as many as you want, edit them, or duplicate one to build the next in a couple of clicks
Which means you can announce every drop in game but post only the red ones to Discord, and never touch the plugin config to do it
Categories the plugin doesnt send yet are tolerated rather than rejected, so a plugin update cant break the setup you already have

Embed Editor - Title, description, colour, footer text and icon, author name, icon and link, thumbnail, image and fields. The whole embed, with a live preview beside the form
Write your own wording with {playerName} {tribeName} {tribeRank} {serverName} {mapName} {memberName}
World events add {name} {classKey} {category} {lat} {lon} {coords}, and eggs open up further with {creatureClass} {level} {mutations}
Every token is registered with the dashboard, so they turn up on the Available Variables page instead of being something you only find out about by reading a doc
Running the Embedder addon as well? These embeds pick up its richer resolver on their own, nothing to configure
Discords own limits are enforced as the embed is built, so an over long title truncates instead of the whole message silently failing to send

Coordinates - {lat} and {lon} come out blank when the plugin couldnt convert the position reliably
A blank beats a confident wrong number that sends half your server to the wrong place
Raw {x} {y} {z} are still there for when you want them anyway

Rate Limits - Sending is queued per channel and paced at about one message a second
An OSD wave or a boss spawn arrives as a burst, and throwing a burst straight at Discord is how a channel gets rate limited and messages quietly go missing. This spreads it out instead
Repeated event ids are ignored, so a retry from the plugin cant double post the same drop
If the channel has been deleted the queue is dropped with a warning rather than retried forever against a channel thats never coming back

Access Control - Viewing the page and editing the config are separate permissions, granted per role like every other addon
The plugin token field is owner only, because its the shared secret both receivers authenticate against
The owner always passes, so you cant lock yourself out of your own dashboard

Runs on ShadowBot ASA
No database, no RCON, no other addon required - the config lives in addon_config.json

The events_notifier_dc key lives on the plugin side. Thats what lets the plugin post out to Discord in the first place
Once the plugin has it, everything on this page is yours

NEEDS SHADOWBOT AND THE SHADOW EVENTS NOTIFIER PLUGIN
The plugin needs events_notifier_dc to send anything out