Paper · Purpur · Velocity
Network down? Be the first to know — and know why
Tickwise is an open-source agent for Minecraft networks. It recognises known failures right on the server, merges proxy and backend errors into a single incident and sends the cause, the evidence and the next steps to Telegram.
All servers healthy
3 backends · MSPT p95 18 ms · 0 open incidents
- signed signatures in the knowledge base
- 42
- signed signatures in the knowledge base
- commands the agent can run on your server
- 0
- commands the agent can run on your server
- message per network outage instead of an alert storm
- 1
- message per network outage instead of an alert storm
- maximum retention of log excerpts
- 7 days
- maximum retention of log excerpts
01 One outage, minute by minute
What Tickwise sees while you still know nothing
A real scenario: a plugin was updated, lobby crashed, the proxy stopped letting players in. On the left — what happened in the network; on the right — what Tickwise did.
lobby
Plugin LuckPerms updated 5.4.140 → 5.4.141
The agent compares plugins, Java version and key settings on every start and remembers what changed.
lobby
[ERROR] Encountered an unexpected exception — Exception in server tick loop
The error is caught right in the log and matched against 42 signed signatures — locally, without the cloud and without sending the whole log.
lobby
The server stopped abnormally, a crash report was saved
The crash and the unclean restart become lifecycle events; three failures in 30 minutes is a crash loop.
velocity
23 players could not connect to lobby · no available servers
The proxy agent counts failed connections and pings every backend every 15 seconds.
Tickwise
One Telegram message: incident NW-01 with the probable root cause
The cloud waits for signals from every server in the network, merges proxy and backend into one incident and attaches the LuckPerms change as a suspect, not a verdict.
TWTickwise
bot
CRITICAL · network default
Backend “lobby” is down: server crashed — players can't join
Servers: velocity (proxy), lobby
Cause: the proxy can't connect players to lobby. Probable root cause — a crash on the backend itself (Exception in server tick loop).
What changed before the failure:
• lobby: LuckPerms 5.4.140 → 5.4.141, 12 min before (possible cause, not proven)
What to do:
- Open the crash report on lobby
- Check the port in velocity.toml
- Make sure the proxy sees lobby again
10:19
Details Helpful Not helpful On it Resolvedyou
LuckPerms rolled back, lobby accepts players again
The incident closes itself when the signals stop. The Helpful / Not helpful buttons feed the signature's statistics.
02 How it works
From a log line to a Telegram card
All heavy lifting happens on your server, off the main thread. Only cleaned, compressed events go to the cloud.
01On your server
Logs & metrics
Log4j, TPS/MSPT, memory, plugins
02On your server
Sanitizer
secrets, IPs, names — removed
03On your server
Signatures
Ed25519-signed pack
04On your server
Disk queue
survives network outages
05In the Tickwise cloud (Russia)
Correlation
proxy + backend = one incident
06In the Tickwise cloud (Russia)
Telegram
cause, evidence, next steps
03 Privacy
What is sent after linking
- Per-minute metrics: TPS, MSPT, memory, GC, disk, players online
- Platform, Java and plugin versions
- Errors — fingerprint, template and counter
- Sanitized log excerpts — up to 20 per hour by default
What is never sent
- Chat, private messages and player command arguments
- Passwords, tokens, forwarding secret, webhook URLs
- Plain IP addresses, UUIDs and nicknames
- World files, whole configs, private keys
The sanitizer runs on your server before anything is sent, and again in the cloud. Data is stored in Russia. Nothing leaves your server before /tickwise link.
04 Knowledge base
What Tickwise recognises without the cloud
Every signature is verified on real Paper and Velocity logs: the agent recognises the error on the server itself and already knows the cause and the steps.
- CriticalSIG-VE-001Modern forwarding mismatch between Velocity and the backend
Your server did not send a forwarding request to the proxyVelocity - WarningSIG-PA-001The server cannot keep up with ticks (Can't keep up!)
Can't keep up! Is the server overloaded?PaperPurpur - ErrorSIG-PL-004Plugin crashed while enabling (Error occurred while enabling)
while enablingPaperPurpur - CriticalSIG-MEM-001Out of heap memory (OutOfMemoryError: Java heap space)
java.lang.OutOfMemoryError:PaperPurpur - CriticalSIG-ST-003The server cannot bind its port (FAILED TO BIND TO PORT)
FAILED TO BIND TO PORT!PaperPurpur - ErrorSIG-DB-002Database connection pool exhausted (HikariCP: Connection is not available)
Connection is not available, request timed out afterPaperPurpurVelocity
05 Setup
Three steps, two minutes
No passwords, no API keys. Linking is confirmed in your server console, so someone else's code won't work.
step 1/3
Install the plugin
Drop the jar into plugins/ on every server and proxy, then restart.
plugins/> cp Tickwise-Paper-0.1.0.jar plugins/Tickwise agent 0.1.0 started (pack 2026.09.24-1, bundled).Cloud not linked: local diagnosis only.step 2/3
Get a code
A console command prints a one-time code valid for 15 minutes.
console> tickwise linkLink code: K7QM-4XPD. Send to the bot: /link K7QM-4XPDstep 3/3
Confirm
Send the code to the Telegram bot and confirm the link in the console.
consoleTickwise: server requested by “My Network”.> tickwise link confirmTickwise: server linked to “My Network”.
06 FAQ
The short version
Check it yourself
One console command shows exactly what the agent sends and what it strips.
Not there yet
- No web dashboard or password login — everything happens in Telegram
- No Fabric, Forge or BungeeCord — only Paper, Purpur and Velocity
- No AI diagnosis — only verified signatures and rules
- Agent console and bot messages are in Russian
Know about outages before your players do
Closed beta for Paper and Velocity network owners. Two minutes to install, one command to remove.