Version 1.4.0 - Compatibility with vehicle plugins #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release adds a new listener type, which is more aggressive. This can be enabled by setting
aggressive-listener
totrue
inconfig.yml
.This replaces the PlayerMoveEvent listener with a repeating task which occurs every tick. This makes sure players using vehicle plugins that don't activate the PlayerMoveEvent event will not be ignored in lines.
This might come at the cost of some performance, but it likely is not much, it's just theoretically not as good as the move events.
This update also has some major internal changes to make the plugin more expandable.
From here on out every config file will have a version prefixed to it, config files should automatically get
version: 1
written to them after updating. Don't edit this value manually, this will be used to migrate to newer releases for if/when the config file format changes.