Systems
Chat Announcement Filter
Server-wide announcements (boss kills, encounter starts, achievements, rare rewards) can be filtered by each player in the bell menu of the profile window. Which settings row an announcement belongs to is data: packs define rows in config/chatnotify*.json.
Each row lets the player choose All, Nearby only or Off. Participants of the announced event (for example the players of the encounter) always receive it. An announcement that no row matches goes to everyone.
Configuration
Any pack can add config/chatnotify.json (any file name starting with chatnotify):
{
"nearbyRadius": 150,
"categories": [
{
"code": "ossuary-awaken",
"order": 20,
"name": "albase:chatnotify-cat-ossuaryawaken",
"default": "nearby",
"priority": 10,
"matches": [
{ "events": ["encounter-awaken"], "encounterIds": ["albase:encounter:ossuary"] }
]
}
]
}File fields
| Field | Default | Description |
|---|---|---|
nearbyRadius | 150 | Radius in blocks for "Nearby only" (horizontal). The last loaded file that sets it wins |
categories | [] | Settings rows |
Category fields
| Field | Default | Description |
|---|---|---|
code | required | Unique row id. A duplicate replaces the earlier row (warning in the log) |
name | none | Lang key of the row label |
default | all | all, nearby or off - used until the player picks something |
nearby | true | false hides the "Nearby only" choice (for announcements with no place in the world, such as achievements) |
order | 0 | Row position in the window, lower first |
priority | 0 | When several rows match one announcement, the highest priority wins |
matches | required | The row covers an announcement when any rule here fits. A row without a rule that has events is skipped |
Match rule fields
An announcement must have its event in events, and every other filter that is set must also pass.
| Field | Description |
|---|---|
events | Required. Event codes (below) |
entityTags | The source entity has any of these tags (for example ossuary, hollowtrials, duat) |
targetIds | The source entity's quest target id matches any of these (* wildcard) |
encounterIds | The encounter id matches any of these (* wildcard) |
Event codes
| Code | Announcement |
|---|---|
bosskill | A boss was killed |
playerkilledbyboss | A player died to a boss |
encounter-preparation | An encounter is being prepared |
encounter-awaken | An encounter boss awakens |
encounter-completion | An encounter was completed |
encounter-fail | An encounter failed |
encounter-rotation | A rotating world boss changed |
encounter-modifier | An encounter modifier was announced |
achievement | An achievement was unlocked |
quest | A quest was completed |
casereward | A case (lootbox) reward |
reroll | A reroll result |
Tagging New Content
For a new boss, either give the entity a tag and match it with entityTags, or match its encounter with encounterIds / its quest target with targetIds. No code change is needed.
The framework's generic rows live in resources/assets/alegacyvsquest/config/chatnotify.json. Area rows: quests/albase/assets/albase/config/chatnotify.json and quests/alzenith/assets/alzenith/config/chatnotify.json.
A player's choices are stored per account and move with account transfer when the target has none.