PageExtension API allows adding new pages & script/stylesheet sources to Plan via an API.
The API consists of these services:
ResolverService- Allows adding HTTP request resolvers to Plan
ResourceService- Allows making web resources (files) customizable by the user
You can find the documentation here: https://github.com/plan-player-analytics/Plan/wiki/APIv5
- (Networks) Clean task now takes into account the server the clean task is running for. This is to avoid one server with smaller removal thresholds removing data of other servers.
- Added a config setting ‘Data_gathering.Disk_space’ default ‘true’, to disable disk space gathering - on some OSes the disk returns free disk space very slowly (10 seconds) leading to lag spikes.
- Made free disk space use Space available to current user on Unix based OSes instead of Free space on disk, as the former is more important for proper functioning of servers.
- Webserver now uses the new API for request resolution. This refactoring was done to make sure that the new API was flexible enough to use.
The resources now need to be set as customized in the config under ‘Customized_files’ (The section should appear when the pages are viewed after the update). This is because the new API allows non Plan files to be customized. The resource will be placed the file to web/ folder inside the Plan folder when accessed (via the webserver) if the setting is true (false by default). If the file exists already it won’t be overwritten.
If you have an existing customization in place you need to set each customized file to true, otherwise the customized file is not used.
- Fixed Plan enabling before plugins it depended on, like Litebans. (There was a typo in bungee.yml
- Fixed an issue with class loader on Spigot related to Essentials extension. (Some classes were loaded twice)
- Fixed an error with player html export when two players joined at the same time
If you have any issues please open a ticket