Sync the rules into a bot-maintained rich post in Discord #1092

New issue

Open

opened 2026-08-20 05:05:11 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-20 05:05:11 +00:00

Member

Filed from the Sirens Discord #suggestions-feedback-bugs forum.

Source // https://discord.com/channels/1300204416229441587/1530053101900529694
Raised by // Kai, 2026-07-24
Forum tags // discord meta
Signal // no replies

Routing note // One of three discord meta threads with no home in the eco repos. Kai routed them here on 2026-08-20.

What was asked

Keep a Discord rich post containing the server rules, maintained automatically rather than hand-edited.

The thread title says "Eco app maintained rich post", meaning the post is maintained by the app rather than being a post about the app. The thread body is //, so the title is the whole suggestion.

The set this belongs to

Kai posted five placeholder threads in three minutes on 2026-07-24, all describing one job: get the rules onto every surface a player might look at, from one source. This is the Discord surface.

Move canon rules into forgejo, coilyco-gaming/eco-ops#83
Sync rules into F1 help page, coilyco-gaming/eco-ops#85
Sync rules into /rules popup window, coilyco-gaming/eco-ops#86
Sync rules into Eco app website, coilyco-gaming/eco-app#315
Sync rules into a maintained Discord rich post, this issue

Why this one lands here rather than eco-app

The write path is Discord. Something needs a bot token with permission to edit a message in #rules, which is this repo's territory. The rules content itself comes from the canonical source in eco-ops.

Dependency

Blocked on the canonical source landing: coilyco-gaming/eco-ops#83

Implementation notes

Edit one pinned message in place rather than posting a new one per change, so the permalink stays stable and members do not get repeatedly notified.
#rules currently has a last message from 2026-05-30, so whatever is there now is the thing being replaced. Read it before overwriting.
Discord message length caps will force either a condensed rendering or a multi-message post. Decide which before building.
Consider surfacing a last-synced marker, so a stale bot is visible rather than silently serving old rules.

Filed from the Sirens Discord `#suggestions-feedback-bugs` forum. **Source** // https://discord.com/channels/1300204416229441587/1530053101900529694 **Raised by** // Kai, 2026-07-24 **Forum tags** // discord meta **Signal** // no replies **Routing note** // One of three `discord meta` threads with no home in the eco repos. Kai routed them here on 2026-08-20. ## What was asked Keep a Discord rich post containing the server rules, maintained automatically rather than hand-edited. The thread title says "Eco app maintained rich post", meaning the post is maintained by the app rather than being a post about the app. The thread body is `//`, so the title is the whole suggestion. ## The set this belongs to Kai posted five placeholder threads in three minutes on 2026-07-24, all describing one job: get the rules onto every surface a player might look at, from one source. This is the Discord surface. * Move canon rules into forgejo, https://forgejo.coilysiren.me/coilyco-gaming/eco-ops/issues/83 * Sync rules into F1 help page, https://forgejo.coilysiren.me/coilyco-gaming/eco-ops/issues/85 * Sync rules into /rules popup window, https://forgejo.coilysiren.me/coilyco-gaming/eco-ops/issues/86 * Sync rules into Eco app website, https://forgejo.coilysiren.me/coilyco-gaming/eco-app/issues/315 * Sync rules into a maintained Discord rich post, this issue ## Why this one lands here rather than eco-app The write path is Discord. Something needs a bot token with permission to edit a message in `#rules`, which is this repo's territory. The rules content itself comes from the canonical source in eco-ops. ## Dependency Blocked on the canonical source landing: https://forgejo.coilysiren.me/coilyco-gaming/eco-ops/issues/83 ## Implementation notes 1. Edit one pinned message in place rather than posting a new one per change, so the permalink stays stable and members do not get repeatedly notified. 2. `#rules` currently has a last message from 2026-05-30, so whatever is there now is the thing being replaced. Read it before overwriting. 3. Discord message length caps will force either a condensed rendering or a multi-message post. Decide which before building. 4. Consider surfacing a last-synced marker, so a stale bot is visible rather than silently serving old rules.

coilyco-ops added the

labels

2026-08-20 05:05:11 +00:00