Pywd: W AI SLOP...

2026-06-30T00:10:18Z

W AI SLOP...

New page

{{DISPLAYTITLE:Toms3-graph}}
{| class="infobox" style="width:300px; border:1px solid; padding:5px; font-size:90%; float:right; margin:0 0 10px 10px;"
|-
! colspan="2" style="text-align:center; font-size:120%; padding:5px;" | Toms3-graph
|-
| colspan="2" style="text-align:center; padding:5px;" | [[File:Tomsgraph128px.png|200px|alt=Toms3-graph logo]]
|-
| '''Developer:'''
| [[pywd]]
|-
| '''Affiliation:'''
| [[overture]]
|-
| '''Development started:'''
| April 20, 2026
|-
| '''Status:'''
| Active
|-
| '''Backend Stack:'''
| Node.js & SQLite
|-
| '''Frontend Library:'''
| Highcharts (StockChart)
|}

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

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 <code>toms-graph.overture.bar</code> domain.

== History ==

=== Discovery and Development ===
The project was conceptualized after [[pywd]] inspected the source code of the official website (<code>www.toms3.cc</code>) and discovered an endpoint named <code>getData.php</code>.

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 <code>overture.bar</code> 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 <code>getData.php</code> endpoint have maintained backwards compatibility.

=== Architecture ===
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 <code>getData.php</code> 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 <code>getData.php</code> 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 ==
The web dashboard relies on '''Highcharts StockChart''' to display interactive timelines. The layout maps data across four distinct vertical axes:

# '''tps, mspt & cpu% Axis:''' Displays server '''TPS''' (Ticks Per Second), '''MSPT''' (Milliseconds Per Tick), and '''CPU usage''' percentage (tracked since mid-2026).
# '''unique joins Axis:''' Displays the total number of '''Unique Joins''' over time.
# '''players online Axis:''' Displays '''Players Online''' metrics.
# '''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 ===
To promote transparency and allow other developers to utilize the archived data, the project exposes several API endpoints under <code>toms.overture.bar</code>. The API is completely public and requires no authentication, though it is protected by a rate limit of 60 requests per minute.

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

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

=== Toms3-terminal ===
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 ==
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:

{| class="wikitable" style="width:100%; margin-top: 10px;"
! Unix Timestamp !! Event Description
|-
| <code>1781810189446</code> || Item frame dupe is patched and the portal dupe is secretly introduced.
|-
| <code>1781986964023</code> || Portal dupe is removed.
|-
| <code>1782526106300</code> || The server is destroyed by ex-administrator [[K7rau]]. The server remains offline until restored from a backup (resulting in a ~2-hour rollback).
|-
| <code>1782671962086</code> || Server chunk trimming is performed for faster migration.
|-
| <code>1782690780949</code> || Server reopens for donors.
|-
| <code>1782742280996</code> || Server reopens for all players.
|}

== See also ==
* [[pywd]]
* [[overture]]
* [[Lurker247]]

Toms3-graph - Revision history

Pywd: W AI SLOP...