Releases: Cryptkeeper/Minetrack
5.5.0
5.5.0 (May 20 2020)
IMPORTANT
This update moves ping timestamps to a shared timestamp per round. Meaning that when pinging servers, each will share the same timestamp for that series of pings. The legacy backend used a timestamp per ping per series of pings. This means after updating Minetrack, the historical graph may render slightly inaccurate for the first 24 hours (or whatever your config.json->graphDuration is), and will automatically correct itself as it receives new updates. Don't worry.
- Replaces flot.js charts with uPlot charts. This new chart library renders much quicker and supports a reduced data format. This results in ~1/12th the bandwidth use when sending the historical graph.
- Removed jQuery (flot.js required this dependency). Between removing flot.js and jQuery, the page size has been reduced by 100KB (33%)!
- New historical graph tooltip design to better compare multiple servers.
- Historical graph now supports click dragging to zoom in to a custom time frame. Double click to reset.
- Historical graph now displays time markers along the bottom.
- All graphs now have horizontal ticks to improve readability.
- Graphs will now display gaps (null) when the ping fails. This removes legacy graph smoothing code and prevents 0 player count pings messing up graph scales.
- Graphs will now render the same on initial page load as they will after being open for a while. This fixes a long standing bug where the frontend ignored 0 player count pings in updates but not on initial load.
- Removes the mobile browser detection/manual historical graph load request. It is now automatically loaded given its smaller size.
5.4.3
5.4.3 (May 14 2020)
- Added support for the optional field
config->skipSrvTimeout
inconfig.json
. If a configured server does not return a valid response when unfurling potential SRV records, it will avoid re-unfurling SRV records for this duration in milliseconds. Use a value of0
to disable this feature altogether. - Removes support for the
config->performance->skipUnfurlSrv
andconfig->performance->unfurlSrvCacheTtl
fields in `config.json
5.4.2
5.4.2 (May 13 2020)
- Fixes a typo causing
_minecraft._tcp.*
SRV records to not resolve.
5.4.1
5.4.1 (May 10 2020)
- Adds warnings when the system is pinging more frequently than it is getting replies.
- Replaces the legacy mc-ping-updated dependency with a new library, mcping-js. This fixes some bugs that could cause "zombie" connections and cause stuttering in the ping loops.
- Fixes potential crash issue when hashing favicons.
5.4.0
5.4.0 (May 9 2020)
- Favicons are now served over the http server (using a unique hash). This allows the favicons to be safely cached for long durations and still support dynamic updates.
- Adds "graphDurationLabel" to
config.json
which allows you to manually modify the "24h Peak" label to a custom time duration. - Adds "serverGraphDuration" (default 3 minutes) to
config.json
which allows you to specify the max time duration for the individual server player count graphs. - Adds "performance.skipUnfurlSrv" (default false) to
config.json
which allows you to skip SRV unfurling when pinging. For those who aren't pinging servers that use SRV records, this should help speed up ping times. - Adds "performance.skipUnfurlSrv" (default 120 seconds) to
config.json
which allows you specify how long a SRV unfurl should be cached for. This prevents repeated, potentially slow lookups. Set to 0 to disable caching. - Ping timestamps are now shared between all server pings. This means less data transfer when loading or updating the page, less memory usage by the backend and frontend, and less hectic updates on the frontend.
- Optimized several protocol level schemas to remove legacy format waste. Less bandwidth!
- Fixes a bug where favicons may not be updated if the page is loaded prior to their initialization.
5.3.1
5.3.1 (May 5 2020)
- Fixes Mojang service status indicators not updating after initial page load.
5.3.0
5.3.0 (May 5 2020)
- Replaces socket.io library (and dependency) with vanilla WebSockets.
- Frontend reconnect behavior has been improved to use exponential backoff behavior (up to 30 seconds) with unlimited retries.
- The "Lost connection!" message will now show the reconnection attempt timer.
- "Counting N players on N Minecraft servers" is now instantly updated when initially loading the page.
5.1.2
This is the last 5.0.x/5.1.x release build using the legacy backend.
It is unsupported and unmaintained. It is kept for reference and any users who choose to deploy outdated builds. It is NOT recommended for use and may be insecure.
Contains 5.0, 5.1, 5.1.1 release fixes.
v4.0.5
This is the last 4.x release build using the legacy frontend AND backend.
It is unsupported and unmaintained. It is kept for reference and any users who choose to deploy outdated builds. It is NOT recommended for use and may be insecure.