Chronicle Stats

1.2.2

• The stat cards of a player sheet pack by their own height, so a short card no longer ends in an empty block beside a long list, and the TrackerAPI chip in the dashboard header, the TrackerAPI line of /chronicle admin status and the README link to the TrackerAPI page on CurseForge.

1.2.1

• Record and personal best toasts have a quiet window per record. A kill streak or any other record that keeps rising is announced once, and further rises within recordToastQuietSeconds (120 by default) go out as one toast with the final value when the window ends.
• Queued bench crafts count one run per craft event. The engine fires one event per finished unit of a queued batch and stamps each with the whole batch quantity, so a batch of a hundred counted as ten thousand crafts. Instant crafts are unchanged.

1.2.0

Chronicle Stats works with TrackerAPI. When TrackerAPI 1.0.0 or newer is installed, Chronicle takes every tracked event from it and registers none of its own tracking hooks, so the server tracks each event once for every mod that uses TrackerAPI. Every count carries on in Chronicle's own files through the same rules. Without TrackerAPI nothing changes.

Added

• The tracker key in chronicle.json, auto by default. auto uses TrackerAPI when it is installed and new enough, always uses only TrackerAPI and tracks nothing while it is missing, never keeps Chronicle's own tracking. Read at start.
• One line at start names the path and how many tracking hooks were skipped, and /chronicle admin status shows Tracking by TrackerAPI <version> with the number of events taken from it.
• When TrackerAPI is reloaded or removed, Chronicle logs once that it needs /plugin reload Ryvrook:ChronicleStats.
• The dashboard header and the /stats page show TrackerAPI connected or TrackerAPI not connected at the top right while Chronicle tracks through TrackerAPI, and nothing otherwise. api/boot gains tracker, api/events a tracker event and api/health the tracker feature.