ℹIndependent community research, not official florr.io documentation. Mechanics can change; review our sources or report a correction.
Home › How It Works

How FlorrMobNotify Works

A look at the technology that takes a florr.io game event from the server to your browser notification in milliseconds — and how you can control exactly what you receive.

The Three-Step Overview

1

Connect

Your browser opens a persistent WebSocket connection to the FlorrMobNotify notification server. Authentication happens automatically using your saved session.

2

Configure

Choose which rarities, regions, and mob types you want to be notified about. All filtering happens client-side and takes effect instantly without reconnecting.

3

Receive

Game events arrive the moment they occur. Your browser fires a native notification (with optional sound) and logs every event in the real-time feed.

Why WebSockets Instead of Polling

Most web applications fetch data by making individual HTTP requests — the browser asks the server a question, the server answers, and the connection closes. For real-time use cases, this means asking the server "is there anything new?" once per second, burning bandwidth on mostly-empty responses and still introducing a worst-case one-second delay before you see anything.

FlorrMobNotify uses WebSockets instead. When you open the app, your browser and the notification server establish a single persistent two-way connection that stays open as long as the page is loaded. When a mob spawns, the server immediately pushes that event to every connected client over their existing open connection. No polling, no reconnection overhead, no wasted round-trips.

The result is sub-100ms delivery from the moment an event is detected to the moment it appears in your feed and triggers your browser notification.

The Full Event Pipeline

Stage 1 — Game Event Detection

The FlorrMobNotify backend monitors florr.io server activity and detects game events including mob spawns, mob defeats, rift openings, rift player-count updates, shop inventory changes, and petal crafting actions. Each event is captured with a precise timestamp and enriched with metadata: mob name, rarity tier, server region, and any available player information.

Stage 2 — Server Broadcast

Processed events are broadcast to all authenticated WebSocket clients simultaneously. The server also maintains authoritative state including the list of currently alive mobs, open rift data, current shop inventory, forge locations, and daily statistics — all of which can be queried on demand by any connected client.

Stage 3 — Client-Side Filtering

When your browser receives an event, it checks your active filter settings before deciding whether to fire a browser notification. If the mob's rarity is enabled, its server region is included, and it is not on your blacklist — a notification fires. Events are always logged in the feed regardless of your notification filters, so you can always review what happened even when certain notifications are muted.

Stage 4 — Browser Notification

Notifications use the standard Web Notifications API built into every modern browser. When triggered, the notification appears in your operating system's notification area — the same place where email or calendar alerts appear. FlorrMobNotify does not need to be in the foreground or even visible; the notification will appear even if you are working in another window or application.

Authentication

Guest Mode

Guest access requires no account. When you choose guest mode on the welcome screen, the server creates a temporary session and issues a session token. This token is stored in your browser's localStorage. The next time you open the app within the session window, your session is automatically resumed from that stored token — no need to click through the welcome screen again. Guest sessions do expire, and the remaining countdown is shown in the app header while logged in as a guest.

Discord OAuth

Discord login uses the standard OAuth 2.0 authorization flow. Clicking "Login with Discord" redirects you to Discord's authorization page where you approve read access to your basic profile. Discord returns a short-lived code, which the app exchanges with the server for a persistent session token. Only your Discord username, user ID, and avatar URL are accessed — the app never requests access to your messages, servers, or friends list.

A Discord session persists indefinitely until you log out. It also shows your Discord username in the community panel and unlocks role-based features such as earlier mob deletion access.

Notification Filtering in Detail

All filtering in FlorrMobNotify is purely client-side. The server sends every event to your browser, and the filter logic runs locally before a notification is triggered. This means:

  • The event feed always shows everything, even events your notification filter would suppress.
  • Changing a filter takes effect immediately — no reconnection, no delay.
  • You can always review missed events in the feed, even if you had certain notifications muted.

Rarity Filter

Each of the 10 rarity levels (Common through Eternal) can be individually toggled. A mob spawn event only triggers a browser notification if that mob's rarity is currently enabled in your settings. This lets you silence lower-rarity noise while staying alerted for the rarities that actually matter to you.

Region Filter

Mob events include the server region where they occurred: US, EU, or ASIA. You can restrict notifications to only the regions where you actually play, avoiding irrelevant cross-region alerts.

Mob Whitelist and Blacklist

For precise control, you can specify exact mob names in two separate lists. A spawn whitelist guarantees notification for those mobs regardless of rarity settings. A blacklist prevents notifications for named mobs regardless of their rarity. Both lists apply to spawn notifications; defeat notifications have their own corresponding lists.

The Live Event Feed

In addition to browser notifications, every incoming event is logged in the real-time event feed panel. The feed records event type, mob name, rarity, server region, timestamp, and — for defeat events — the usernames of the players who claimed the kill.

Rift events are pinned to the top of the feed for 30 seconds after arrival, keeping them visible even as other events scroll by. You can configure the maximum number of events kept in memory (10, 20, 50, 100, 1000, or unlimited), and you can clear the feed manually at any time while preserving any currently pinned rift events.

Latency Display

The ping indicator in the app header measures the round-trip latency between your browser and the notification server using periodic ping/pong WebSocket frames. This is not the same as your florr.io game latency — it shows how quickly the notification server is communicating with your specific browser connection.

The indicator is color-coded: green for under 80ms (excellent), yellow for 80–160ms (good), orange for 160–300ms (acceptable), and red for above 300ms (degraded). You can click the ping display to immediately trigger a new measurement.

Connection Recovery

If your connection drops — due to a network interruption, a brief server restart, or a browser tab being suspended — a connection overlay appears automatically. The app attempts to reconnect on its own. When reconnection succeeds, your session is restored from your locally saved session token, your settings are reloaded from localStorage, and the server sends a fresh snapshot of current alive mobs to bring the display back up to date.

See It in Action

Open the app and connect as a guest. You will be receiving live mob notifications within seconds — no account, no setup required.

Open the Notifier →