Toms3-graph is an external statistics and archiving project developed by pywd with infrastructure and optimization assistance from overture.

Toms3-graph
Toms3-graph logo
Developer: pywd
Affiliation: overture
Development started: April 20, 2026
Status: Active
Backend Stack: Node.js & SQLite
Frontend Library: Highcharts (StockChart)

It continuously archives data provided by the official Toms3 server endpoints, rendering detailed graphical visualizations of server performance, player activity, and world progression through a web interface hosted on the toms-graph.overture.bar domain.

History

edit

Discovery and Development

edit

The project was conceptualized after pywd inspected the source code of the official website (www.toms3.cc) and discovered an endpoint named getData.php.

Development began on 20 April 2026. While the core backend and frontend architectures were built entirely by pywd, members of the overture group assisted in setting up the project's subdomains under overture.bar and helped optimize the loading speeds of database snapshots.

The server administrator, cherryh4ck, is aware of the project's existence. Although the script performs thousands of fetches per day, it has not faced restrictions, and successive updates to the getData.php endpoint have maintained backwards compatibility.

Architecture

edit

Toms3-graph is designed to be highly optimized and operates on a lightweight footprint, sharing a Virtual Private Server (VPS) with the bot Lurker247 without experiencing performance degradation.

  • Backend: Written in Node.js. It performs a request to getData.php every 10 seconds. If it detects a change in the server statistics, it commits the new snapshot to the database.
  • Database: Utilizes SQLite for structural simplicity and fast read/write operations.
  • Player Count API: Early versions of getData.php did not output the active player count. To solve this, pywd integrated a third-party Minecraft query API to fetch player numbers independently. This system remains operational alongside the main fetch script. While all other data is archived directly from the official API, the player count is handled by this custom implementation.

Features and Metrics

edit

The web dashboard relies on Highcharts StockChart to display interactive timelines. The layout maps data across four distinct vertical axes:

  1. tps, mspt & cpu% Axis: Displays server TPS (Ticks Per Second), MSPT (Milliseconds Per Tick), and CPU usage percentage (tracked since mid-2026).
  2. unique joins Axis: Displays the total number of Unique Joins over time.
  3. players online Axis: Displays Players Online metrics.
  4. world size (GB) Axis: Displays World Size growth measured in gigabytes (GB).

Due to the project starting development in late April 2026, early server events such as the 200 GB terrain generation inside the Nether by the alternate accounts zog and Netanyahu1488 in March were not captured. However, the graphics clearly illustrate the 130 GB chunk generation caused by pywd in June 2026.

Public API and Endpoints

edit

To promote transparency and allow other developers to utilize the archived data, the project exposes several API endpoints under toms.overture.bar. The API is completely public and requires no authentication, though it is protected by a rate limit of 60 requests per minute.

  • /api/data: Contains the complete list of recorded database snapshots.
  • /api/daily: Provides daily aggregated data.
  • /api/historic: Serves historical data records.
  • /api/summary: Returns a lightweight summary of the database (e.g., total snapshot count).
  • /api/live: Displays the current live metrics being fetched in real-time.

Data Exports

edit

The project also features a /downloads/ directory designed to provide downloadable data exports for offline processing or independent archiving. These exports consist of direct SQLite (.db) database dumps, which are automatically generated and updated every 2 to 4 days.

Toms3-terminal

edit

A twin project named Toms3-terminal exists as an even lighter, minimalist view. It acts as an ultra-low-overhead alternative to the main graphical view, offering a very simple and highly optimized frontend that provides a direct representation of the archived data.

Captured Historical Events

edit

The chart's timeline includes custom marker flags logging some key moments in the history of Toms3. The project's main purpose is not historical tracking, so it does not include every event as a flag:

Unix Timestamp Event Description
1781810189446 Item frame dupe is patched and the portal dupe is secretly introduced.
1781986964023 Portal dupe is removed.
1782526106300 The server is destroyed by ex-administrator K7rau. The server remains offline until restored from a backup (resulting in a ~2-hour rollback).
1782671962086 Server chunk trimming is performed for faster migration.
1782690780949 Server reopens for donors.
1782742280996 Server reopens for all players.

See also

edit