This update adds a new option called disable_cache
to the config.yml
When set to true (Defaults to false) will the caching of players be disabled. This means the following:
- No player names will be loaded from the
cache.data
file, if present - No
cache.data
file will be created if none is present - No player data will be saved to the
cache.data
file when the plugin gets disabled
Placeholders
It's important to note, that any placeholder requiring a cached player will NOT work when this option is used.
In particular, the following placeholders won't work:
${player name}
(Will display the text set inunknown_player
)${player hasPlayedBefore}
${player isBanned}
${player isWhitelisted}
${player uuid}
- Any PlaceholderAPI placeholders
There was a chance of an exception appearing due to the file not being able to create the cache.data file due to a missing setting. This should be fixed. It never showed up to me since I use windows and test my plugin locally.
The output of /asl reload
, namely the Loaded x Profile(s)!
was formatted wrong.
It looked something like this:
Fixes a few random errors that may appear under certain conditions.
Fixes
clearFaviconCache()
throwing an exception when FaviconHandler instance has never been created- Random
Double operator
error when usingsomething != something
(Would see the=<space>
as second expression)
It should now just ignore any followup expressions if it found one.
NOTE
This update is a breaking change, as the Server list profiles have been changed in structure! Please read the Migration Page on how to migrate from previous versions to this one.
Changed
- [BREAKING] Restructured the Server List profile
Improved
- Improved how fake players for the Hover are created.