Skip to content

Base event tier, lifetime, and eviction on message importance #4717

Open

Description

@bighurdan-cell

Purpose

Events that need a reaction expire and get evicted on the same rules as routine chatter.


Objectives

Events you have to react to should stay up longer than routine ones, and shouldn't get pushed off screen by a burst of low value messages.


Description

#3910 split the feed into two panels so high value notifications weren't mixed in with low value ones. That split decides where an event renders, but not how long it lives.

Everything expires on the same rule at EventsDisplay.ts:215, a flat 8 seconds. Eviction is by age too, tier 2 keeps the last 4 entries and the feed keeps the last 30. So a chat burst can push an inbound nuke warning off screen before you react to it.

My plan is to give each MessageType an importance level, then have the tier split, lifetime, and eviction read from that instead of the hardcoded TIER_1_TYPES set. Events that need a reaction get a longer lifetime and get skipped by the eviction caps. Nothing currently prominent gets demoted, it's the same membership split into two levels.

This doesn't overlap with the grouping work in #4516, that reduces volume by merging entries and this weights them.

I'm also able to keep the mapping client side if you'd rather not touch src/core.


Discord: Hurdan

Activity

  1. github-actions commented on Jul 25, 2026

    @github-actions
    Contributor

    Hi @bighurdan-cell, thanks for opening this issue. It hasn't been approved by a maintainer yet — we'll get back to you shortly to either milestone it (approval) or close it.

    — Automated. See CONTRIBUTING.md.

  2. added this to the Backlog milestone on Jul 25, 2026
  3. added
    approvedApproved for a PR, if you assigned to the issue.
    and removed
    not-approvedThis issue has NOT been approved by the maintainers.
    on Jul 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

approvedApproved for a PR, if you assigned to the issue.

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions