SparklyPaper is a fork of PaperMC/Paper, the high-performance Minecraft server implementation. It applies a curated set of custom performance and feature patches on top of upstream Paper, with a focus on server tick optimization and configuration via a sparklypaper.yml file. The build is Gradle-based and produces a patched server jar; CI workflows automatically track upstream Paper and build the project. The repository is structured as a standard Paper fork: a Gradle multi-project build with a sparklypaper-api module and a patched server module. The runtime entry point is the standard Paper patched Minecraft server main class; custom behavior is introduced through patches that modify world ticking, chunk loading, and player data handling. The sparklypaper.yml file controls per-world settings, with defaults and per-world overrides. External dependencies include upstream Paper, Minecraft server jars, Gradle, and GitHub Actions. The repository also contains design notes (PARALLEL_NOTES.md), performance results (RESULTS.md), and a curated list of known-broken patches from other forks (BORKED_PATCHES.md). It is not a library or service; it is a server distribution for running Minecraft servers. No test suite is visible; CI focuses on build and auto-update.
This is a web application for viewing and analyzing Minecraft server performance timings reports. It consists of a PHP backend that handles report upload, caching, and data transformation, and a React-based frontend for interactive visualization. The backend parses a proprietary compressed timing format from Minecraft servers (Paper, Sponge, etc.) into a structured JSON object, caches it, and serves it via REST endpoints. The frontend fetches this data and renders charts, tables, and drill-down views of timing handlers, regions, and plugins. The application is a single-page application built with React 15, Webpack 2, and Babel 6, with a heavy reliance on jQuery-like PHP utilities and the Stiphle rate-limiting library. The architecture is a classic LAMP stack with PHP serving as both the API and the HTML shell. Key entry points are index.php (main page), data.php (API), post.php (upload endpoint), and backend_daemon.php (CLI daemon). The system uses a file-based cache with gzip compression and serialization. The frontend manages state with a global data object and uses Chart.js for TPS and entity graphs. The codebase demonstrates a custom JSON deserialization trait (FromJson) that maps JSON arrays to typed PHP objects using PHPDoc annotations, which is a notable pattern for handling evolving data formats. However, the project shows significant technical debt with outdated dependencies and a monolithic global state approach in the frontend.