Перейти к содержимому
Mineforgian

Fiw Clock

Tickwatch is a tiny, server-side Minecraft mod that records each player's playtime, kills, and deaths and stores them in a plain JSON file per world. It runs on both Fabric and NeoForge.

Загрузки
63
Подписчики
0
Обновлён
7 июня 2026 г.
Лицензия
MIT

Опубликован 7 июня 2026 г.

Tickwatch

Track playtime, kills, and deaths — server-side, lightweight, crash-safe.

Tickwatch quietly records how long each player has played and how many kills and deaths they rack up, then stores it all in a clean JSON file. No client mod required, no commands to learn, no impact on your TPS.


✨ Why Tickwatch?

  • 🪶 Featherweight — tracking is one integer per online player per tick. That's it.
  • 🖥️ Server-side only — your players join with a vanilla client. Install it on the server and forget it.
  • 🔀 Fabric and NeoForge — same mod, both loaders.
  • 💾 Crash-safe by design — atomic writes with a rotating backup. A sudden power loss or hard crash cannot corrupt your stats.
  • Never blocks the server — all disk writes run on a dedicated background thread.

📊 What it tracks

For every player, per world:

Stat Detail
⏱️ Playtime Counted in ticks, with a human-readable 2h 14m 30s field
⚔️ Kills Mobs and players killed by that player
💀 Deaths Times that player died

Stored at <world>/fiw-clock/stats.json:

{
  "players": {
    "069a79f4-44e9-4726-a5be-fca90e38aaf5": {
      "name": "Notch",
      "playTimeTicks": 144000,
      "playTimeFormatted": "2h 00m 00s",
      "kills": 12,
      "deaths": 3
    }
  }
}

Perfect for leaderboards, web dashboards, Discord bots, or anything that can read JSON.

📦 Requirements

Minecraft 1.21.11 · Java 21+

  • Fabric: Fabric API + Fabric Language Kotlin
  • NeoForge: Kotlin for Forge

No Architectury or other wrapper mod required.

🚀 Install

  1. Install Fabric or NeoForge on your server.
  2. Add the matching dependencies to mods/Fabric: Fabric API + Fabric Language Kotlin; NeoForge: Kotlin for Forge.
  3. Drop in the Tickwatch jar for your loader.
  4. Start the server — stats start tracking immediately.

💡 Tickwatch is purely server-side. Players do not need it installed to join.

📖 Links

Ченджлог

1.0.0Релиз1.21.11 · 7 июня 2026 г.

Changelog

All notable changes to Tickwatch are documented here.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

1.0.0

Added

  • Initial release.
  • Server-side tracking of playtime, kills, and deaths per player.
  • Multi-loader support for Fabric and NeoForge from a single codebase, with a Minecraft-free common module and no Architectury / wrapper dependency.
  • Per-world JSON storage at <world>/fiw-clock/stats.json, including a human-readable playTimeFormatted field alongside the raw playTimeTicks.
  • Crash-safe write pipeline: temp file + fsync + rotating .bak + atomic rename, with automatic backup recovery and per-entry fault tolerance on load.
  • Off-thread asynchronous saving (every 5 minutes and on player logout) plus a final blocking save on server shutdown, so the server tick loop never blocks on disk I/O.
1.0.0Релиз1.21.11 · 7 июня 2026 г.

Changelog

All notable changes to Tickwatch are documented here.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

1.0.0

Added

  • Initial release.
  • Server-side tracking of playtime, kills, and deaths per player.
  • Multi-loader support for Fabric and NeoForge from a single codebase, with a Minecraft-free common module and no Architectury / wrapper dependency.
  • Per-world JSON storage at <world>/fiw-clock/stats.json, including a human-readable playTimeFormatted field alongside the raw playTimeTicks.
  • Crash-safe write pipeline: temp file + fsync + rotating .bak + atomic rename, with automatic backup recovery and per-entry fault tolerance on load.
  • Off-thread asynchronous saving (every 5 minutes and on player logout) plus a final blocking save on server shutdown, so the server tick loop never blocks on disk I/O.

Комментарии

Загружаем…