Ikariam Notifications Guide

The Notifications feature combines wine monitoring, incoming-attack monitoring, browser delivery, Telegram delivery, and per-category routing. Enable the Notifications master toggle plus the Wine or Attack subtask you want monitored.

Wine Alert

Set the threshold in hours and enable Wine Alert. The task compares the selected city’s current wine and consumption state with that threshold and sends a notification when the known supply enters the configured window.

If no alert appears, confirm the city data is current, the threshold is appropriate, and the Wine subtask’s Next check timer is due.

Attack Alert

Attack Alert periodically checks the incoming movement count exposed by Ikariam. The panel displays the last known count so you can compare stored state with the live military advisor.

The notification is intended to report a change in known incoming activity. It does not replace reviewing the movement details in Ikariam.

Browser Notifications

Enable browser delivery and grant notification permission when prompted. If the browser has blocked the permission at site or profile level, enabling the checkbox alone cannot display a notification.

Use the delivery test after changing permissions. Also check operating-system notification settings when the browser reports permission but no message appears.

Connect Telegram

Telegram delivery is relayed through the Helper Bot backend. Raw Telegram bot credentials and chat routing are not stored in the extension.

Select Connect Telegram.
Open the generated Telegram link.
Complete the connection in Telegram.
Return to the extension and check the connection.
Enable Telegram delivery.
Send a test message.

If testing fails, cancel or disconnect the existing link state, reconnect, and verify that the current Ikariam account is linked.

Per-Category Routing

Browser and Telegram channels can be enabled separately for attack, wine, building, trade, piracy, and general events. Disabling one category does not disable the same delivery channel for all other categories.

Only categories emitted by enabled features can generate messages. For example, a Piracy route does nothing while Piracy is disabled and has no event to report.

Telegram Commands

The backend task supports command polling, but its setup panel is not currently exposed in the released Notifications interface. This guide therefore does not recommend enabling remote commands until that UI is restored and can be configured visibly.

Troubleshooting

Confirm the Notifications master toggle and monitoring subtask are enabled.
Check browser and operating-system permissions.
Verify Telegram displays Connected and passes a test message.
Review routing for the missing event category.
Wait for or clear the correct Next check schedule.
Review the extension task log for backend or game-state errors.

FAQ

Why do browser notifications not appear?

The most common causes are blocked browser permission, blocked operating-system notifications, disabled category routing, or a monitoring subtask that is not enabled or due.

Does the extension store my Telegram bot token?

No. Telegram credentials and chat routing remain on the Helper Bot backend; the extension uses its account connection and the backend relay.

Can Telegram start a completely stopped bot?

No. Command polling is an extension task and requires the bot loop to already be running. The command setup UI is also currently hidden.