Reminder System
Set in-game alarms with repeats and advance notifications. Runs entirely in your browser - no signup needed.
Alarm builder
Metin2 Reminder System: A Browser-Side Alarm Tool for Boss Respawns and Events
The Reminder System is a small alarm scheduler built into metin2pserver.net that runs entirely in your browser. Set named timers for boss respawns, event windows, dungeon lockouts, vote cooldowns, whatever you don't want to keep checking in-game. Each alarm has a repeat interval, an optional early-warning, a sound (text-to-speech or a built-in clip), and a play-once or loop-till-disarmed behaviour. No account, no server, no third-party service. This guide explains why it exists, how it works under the hood, and how to use it well.
Why a Browser Alarm Tool
Most useful timers in Metin2 are short and personal: a boss respawns every 30 minutes, the vote cooldown ends in 12 hours, a dungeon resets at the next server tick. Phone alarm apps don't fit the granularity, in-game timers don't survive a relog, and Discord bots need a server you don't run. The Reminder System sits in your browser tab, runs purely in JavaScript, and chirps when the time is up. That's all it does.
- Local-only. The alarms live in your browser's storage. Nothing is sent to our server, nothing is shared, nothing is tied to an account.
- Multiple alarms at once. The queue can hold as many as you want, each with its own repeat and sound.
- Free. No sign-up wall, no paid tier, no ads inside the tool.
How It Works
Open the tool, fill in the alarm builder, save. The browser then keeps an internal timer for each saved alarm and triggers the sound when its target time is reached. If you set an "advance" value, the trigger fires that many seconds before the actual target time, so you have a heads-up window to react.
Under the hood the page uses three simple browser features:
- localStorage for persistence. The alarm list is serialised to JSON in your browser and restored on the next page load.
- setInterval / Date.now() for the actual countdown. The page polls the active alarms once per second and updates the displayed time-until-next.
- SpeechSynthesisUtterance (TTS) or a plain HTMLAudioElement for the sound output, depending on what you picked in the Sound dropdown.
Because everything runs client-side, the tool works offline once the page is loaded. The flip side: if you close the tab or your browser pauses it, the timer stops too.
Building an Alarm: Field by Field
The Queue and Now-Firing Panels
Every saved alarm sits in the Queue with a live countdown. Click a row to select it; the Selected-alarm panel on the right shows the full configuration and lets you restart its countdown or remove it.
When an alarm reaches its trigger window, it moves into the Now firing panel and starts the sound. In Loop till disarmed mode the sound keeps playing until you click the row to disarm it; in Play once mode the sound plays one time and the alarm silently reschedules itself for its next interval.
Tips for Reliable Timing
- Keep the tab visible. Background browser tabs are throttled by every modern browser to save CPU. A tab in the background will drift the alarm by several seconds per minute. Pin the tab or keep it visible to stay accurate.
- Use Loop mode for the alarms you cannot miss. Boss respawns and event starts deserve the looped alert; vote-cooldown nudges are fine on Play-once.
- Set Advance for travel time. If the alarm is for a boss that spawns on a different map, set Advance to whatever your typical teleport takes (15 to 60 seconds) so you arrive before it pops.
- Keep TTS names short. "Razador" reads cleaner than "Razador respawn in front gate room two".
- Test before relying on it. Hit the Test sound button after configuring a new alarm so you know exactly what it sounds like at your volume.
Reminder System FAQ
Do I need an account to use this?
No. The tool runs in your browser. There is no login, no registration, no server-side state.
Where are my alarms stored?
In your browser's local storage on this device. Clear your site data or use a different device or browser and the alarms are gone.
What happens if I close the tab?
The countdowns pause. Reopen the tool and the alarms restart from where they were saved (the timestamps are recalculated against the current time, so anything that was supposed to fire while the tab was closed will fire immediately on reopen).
Why does the timer drift when the tab is in the background?
Every modern browser (Chrome, Firefox, Safari, Edge) throttles JavaScript timers in inactive tabs to save battery. There is no way around it from a web page. Keep the tab visible (or pinned to a small window in a corner) for accurate timing.
Can I have multiple alarms at once?
Yes, as many as you want. Each alarm runs on its own schedule. The Queue panel shows them all with live countdowns.
How do I stop a looping alarm?
Click the row in the Now firing panel. The sound stops and the alarm reschedules itself for the next interval.
Does Text To Speech work in every browser?
Modern Chrome, Edge, Safari and Firefox all ship the SpeechSynthesis API. Older browsers may not. If TTS doesn't speak, pick a built-in sound clip instead.
Can the alarm wake my computer or push a notification when the tab is closed?
No. This is a pure web page. It cannot push notifications, wake the system, or run when the tab is closed. For phone-style push alerts use a dedicated reminder app.
Is anything tracked or sent to your server?
No. The tool is fully client-side. We don't know which alarms you set, when they fire, or what their names are. Nothing about your alarms leaves the browser.
How do I restart an alarm without deleting it?
Click the alarm in the Queue. The Selected-alarm panel on the right shows a Restart button that resets the countdown to the full interval.
What's the maximum repeat interval?
120 minutes (2 hours). For longer intervals, use a dedicated reminder app or a calendar event - browser timers aren't reliable for multi-hour gaps, especially across sleep/wake cycles.