You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
Bug was introduced during the initial addition of vector manipulation to events and entities.
Vectors don't persist through properties due to bukkit api nature on vectors.
It creates a new vector on every method you use against it.
There are two approaches to this kind of issue. Create a custom handle to it. Or a transformer to a Mutable version of vector provided similarlly to how item stacks work.
Will see what method seems best for future.
Current workarounds are to set the vectors with a new vector object with the previous vector values read through properties.
The text was updated successfully, but these errors were encountered:
BlockDispense
LightningBolt
ThunderChange
WeatherChange
SignChange
Plus basic support for vector parameters and properties.
Closes#249
Introduces bug #251
Bug was introduced during the initial addition of vector manipulation to events and entities.
Vectors don't persist through properties due to bukkit api nature on vectors.
It creates a new vector on every method you use against it.
There are two approaches to this kind of issue. Create a custom handle to it. Or a transformer to a Mutable version of vector provided similarlly to how item stacks work.
Will see what method seems best for future.
Current workarounds are to set the vectors with a new vector object with the previous vector values read through properties.
The text was updated successfully, but these errors were encountered: