Setup guide

Alerts and notifications

The control panel

How alerts work

A shield drops, fury, a player renames or migrates. Onyx sends a message. You decide which of those notifications you want to hear about, and for shield drops, fury, migration, guild switches and renames you also set a might range so small or too big targets never spam your chat.

Start here

Open your settings

Everything lives in one place. Send the command and Onyx replies with a card of toggle buttons, one per alert type.

1

See every toggle

The reply is a "Your Settings" card. Each row shows whether that alert is on or off as a button.

/settings Your Settings
2

Tap to flip

Tap a toggle button to switch that alert on or off. The card updates so you can confirm the change without retyping anything.

Reset. /resetsettings puts every toggle and range back to defaults. It asks you to confirm first, and only admins can run it.

The part people mix up

Three separate might ranges

There are three independent might-range systems. Setting one does not touch the others, so if an alert is firing on the wrong size band, make sure you are editing the range that actually controls it.

Range 1

Shield drops and list defaults

These set the low and high might for shield-drop alerts. They also become the default range the list commands use. Admins only.

1

Set the minimum might

Ignore anything below this might.

/minmight 500M
2

Set the maximum might

Ignore anything above this might.

/maxmight 2B
Range 2

Fury alerts

Fury has its own range, completely separate from shield drops. Defaults are 100M to 1.5B.

1

Set the minimum might

Lower limit for fury alerts.

/furyminmight 100M
2

Set the maximum might

Upper limit for fury alerts.

/furymaxmight 1.5B
Range 3

Migration, guild switch and rename

Kingdom enter, kingdom leave, guild switch and rename alerts all share this one range.

1

Set the minimum might

Lower bound for all four of those alerts.

/alertminmight 500M
2

Set the maximum might

Upper bound for the same four alerts.

/alertmaxmight 5B
One exception. The captured and leader-returned alerts carry their own min and max inline as part of the command, so they do not use any of the three ranges above.

What fires and what it looks like

The alert toggles

Each alert is a simple on or off switch. Some are on by default, some are off. Here is what each one watches for and how the message reads.

Default ON

Fury alerts

1

A scout or attack march is sent

When an unshielded castle starts attacking. Uses the fury range you set in Range 2.

/furyalert on Fury Alerts: ON

Rename and guild switch

1

Name changes

Alerts when a player renames. On by default.

/alertrename on Name Changed: NEYVI to NEYVI Reborn
2

Guild changes

Alerts when a player switches guild. Off by default.

/alertguildswitch on NEYVI: [VNX] to [PkT]
Default OFF

Kingdom migration

These two share Range 3 with rename and guild switch.

1

Moving in

Alerts when a player migrates into your kingdom.

/alertkingdomenter on
2

Moving out

Alerts when a player leaves your kingdom.

/alertkingdomleave on

Leader captured and returned

Each of these takes its own might range inline, right after the on or off.

1

Leader captured

Turn it on and set the band in one command.

/alertcaptured on 500M 10B
2

Leader returned

Same shape, for when a captured leader comes back.

/alertleaderreturned on 500M 10B

Cut the noise

Skip recently active castles

A shield that drops on a castle whose owner is clearly online usually is not worth tracking, since they can re-shield right away. This filter stops shield-drop alerts for castles that were active in the last few minutes.

The ignore-active filter

1

Turn the filter on

When on, shield-drop alerts for recently active castles are skipped. Admins only.

/setignoreactivecastles on
2

Set the window

How many minutes of quiet before a castle counts as inactive again. Admins only.

/setignoreactiveminutes 10
Only shield drops. This filter applies to shield-drop alerts. It does not silence fury, migration or the other alert types.

Silence specific targets

Muting guilds and players

Keep every alert running but stay quiet on a friendly guild or a specific player. Shield-drop mutes and fury mutes are separate lists, so read the card carefully before you add a name.

Mute a guild (shield drops)

Stops shield-drop alerts for everyone in that guild.

1

Add or remove

Mute a guild, or take it back off the list.

/muteg VNX /unmuteg VNX
2

Review or clear

See who is muted, or wipe the whole list.

/mutedguilds /unmuteallguilds

Mute a guild (fury only)

A separate list that only affects fury alerts. Muting a guild here leaves its shield-drop alerts alone.

1

Add or remove

Mute or unmute a guild for fury only.

/mutefuryg VNX /unmutefuryg VNX
2

Review or clear

List the fury-muted guilds, or clear them all.

/mutedfuryguilds /unmuteallfuryguilds

Mute a player

One player mute covers their shield-drop, fury and leader-returned alerts together.

1

Add or remove

Mute a single player, or unmute them.

/mutep NEYVI /unmutep NEYVI
2

Review or clear

List muted players, or clear the list.

/mutedplayers /unmuteallplayers

Quiet during tracking

Keeps a live tracking session readable by holding back the rest.

1

Focus on the track

When on, all other alerts are muted while a track is running, so its output does not get buried. Admins only.

/mutetracking on

Reference

Every alert command

/settings

Open the toggle control panel and tap to flip any alert on or off.

/resetsettings

Reset all toggles and ranges to defaults after a confirm. Admins only.

/minmight <might>

Minimum might for shield-drop alerts and list defaults. Admins only.

/maxmight <might>

Maximum might for shield-drop alerts and list defaults. Admins only.

/furyalert <on|off>

Fury alerts when an unshielded castle starts attacking. Default on.

/furyminmight <might>

Lower might limit for fury alerts. Default 100M.

/furymaxmight <might>

Upper might limit for fury alerts. Default 1.5B.

/setignoreactivecastles <on|off>

Skip shield-drop alerts for recently active castles. Admins only.

/setignoreactiveminutes <minutes>

Inactivity window for the ignore-active filter. Admins only.

/alertcaptured [on|off] [min max]

Leader-captured alert with its own might range.

/alertleaderreturned [on|off] [min max]

Leader-returned alert with its own might range.

/alertrename <on|off>

Alert when a player changes name. Default on.

/alertguildswitch <on|off>

Alert when a player changes guild. Default off.

/alertkingdomenter <on|off>

Alert when a player migrates into your kingdom. Default off.

/alertkingdomleave <on|off>

Alert when a player leaves your kingdom. Default off.

/alertminmight <might>

Lower might bound for migration, guild-switch and rename alerts.

/alertmaxmight <might>

Upper might bound for those same alerts.

/mutetracking <on|off>

Mute all other alerts while a track is running. Admins only.

/muteg <guild>

Mute a guild's shield-drop alerts. Fury is a separate list.

/unmuteg <guild>

Unmute a guild's shield-drop alerts.

/mutedguilds

List the guilds muted for shield drops.

/unmuteallguilds

Clear the shield-drop guild mute list.

/mutefuryg <guild>

Mute a guild's fury alerts only.

/unmutefuryg <guild>

Unmute a guild's fury alerts.

/mutedfuryguilds

List the guilds muted for fury.

/unmuteallfuryguilds

Clear the fury guild mute list.

/mutep <player>

Mute a player's shield-drop, fury and leader-returned alerts.

/unmutep <player>

Unmute a player.

/mutedplayers

List muted players.

/unmuteallplayers

Clear the player mute list.

Tip. If an alert is firing on the wrong size of target, check which of the three ranges controls it before changing anything. Shield drops use /minmight and /maxmight, fury uses /furyminmight and /furymaxmight, and migration, guild switch and rename share /alertminmight and /alertmaxmight.
See plans Full command guide