Changed bounds to use a new region system, see below.
Full bounds now don't actually stretch the locations. You can now modify if the bound is full or not afterwards.
Bounds now use locations 2 different ways, see below for more info.
Bound saving has changed:
Previous behaviour: each bound would save when it was created/modified.
This could cause massive lag if creating/modifying many in a short period of time.
New behaviour: bounds are only saved every 5 minutes (off the main thread) and when the server stops.
This is a massive performance boost.
ADDED:
Added support for set in the item flags of item expression (it was documented that this worked, but never actually worked)
Added support for set in the bound locations expression (allowing you to set greater/lesser corners)
Added support for add/remove in the bound locations expression (allowing you to add/remove vectors to/from greater/lesser corners to offset size)
Added an expression to get the world of a bound
Added an expression to get/set the full state of a bound
BOUND REGIONS:
Bounds internally now use a region system.
The issue before with bound events was when a player moved, ALL bounds were looped and checked if the player moved in/out of that bound.
Now, bounds are put into regions with a size of 16x16 chunks. So when a player moves, only the bounds within that region at the player are checked.
This GREATLY increases performance.
Spark Test:
19200 bounds
50 players (all moving)
Old System:
SkBee was using about 50% of server resources per tick
New System:
SkBee was using about 0.3% of server resources per tick
BOUND CREATION CHANGES:
When creating a bound, you have 2 options as what to pass in for your 2 points:
LOCATIONS: If you use locations, your bound will be created using the exact location you pass in.
In the image on the left, locations were used, and the bound created using the exact location of the blocks.
Example: create bound with id "test" within (location of {_a}) and (location of {_b}) (a/b representing blocks)
BLOCKS: If you use blocks, 1 will be added to the x/y/z axes of the bound to account for the blocks on the edge.
In the image on the right, blocks were used. The x/y/z axes had 1 added to account for those blocks.
Example: create bound with id "test" within {_c} and {_d} (c/d representing blocks)
Temp changelog:
FIXED:
CHANGED:
ADDED:
setin the item flags of item expression (it was documented that this worked, but never actually worked)setin the bound locations expression (allowing you to set greater/lesser corners)add/removein the bound locations expression (allowing you to add/remove vectors to/from greater/lesser corners to offset size)BOUND REGIONS:
Bounds internally now use a region system. The issue before with bound events was when a player moved, ALL bounds were looped and checked if the player moved in/out of that bound. Now, bounds are put into regions with a size of 16x16 chunks. So when a player moves, only the bounds within that region at the player are checked. This GREATLY increases performance.
Spark Test:
Old System:
New System:
BOUND CREATION CHANGES:
When creating a bound, you have 2 options as what to pass in for your 2 points:
In the image on the left, locations were used, and the bound created using the exact location of the blocks. Example:
create bound with id "test" within (location of {_a}) and (location of {_b})(a/b representing blocks)create bound with id "test" within {_c} and {_d}(c/d representing blocks)