1. Builds
  2. WorldGuard (fix/improve-boat-item-detection)
  3. Build #2402

WorldGuard Build #2402

Be aware that this branch (fix/improve-boat-item-detection) is not the main branch (version/7.0.x)!

Branches other than the main one may be experimental. In addition, you should be using stable releases rather than these test builds.

Go to main branch View stable downloads
ProjectWorldGuard
StatusSUCCESS
Branchfix/improve-boat-item-detection
Number#2402-1d409fe
Date10 hours ago
Artifacts
worldguard-bukkit-7.0.20-SNAPSHOT-dist.jar(1170.8 kBytes)
Sponsor
Apex Hosting
Changes
IDSummaryCommitterDate
1d409fe9
  • Fixed Poplar boats causing an error, and harden against future issues
Maddy Miller10 hours ago
a6d64dcc
  • Back to SNAPSHOT for continued development
Maddy Miller4 days ago
f395a167
  • Release 7.0.19
Maddy Miller4 days ago
0aeb9d8d
  • Fix lock flag restoration after session reinitialization (#2304)
brokkonaut4 days ago
7c280a13
  • Cancel blocked natural spawns before the entity is created (#2300)
    • Cancel blocked natural spawns before the entity is created The mob-spawning and deny-spawn checks in WorldGuardEntityListener fire on CreatureSpawnEvent, at the very end of the spawn pipeline. By that point the server has picked a spawn position, run the placement checks, constructed the mob and run finalizeSpawn, and the cancelled mob is thrown away. Since a cancelled spawn never counts toward the mob cap, the natural spawner keeps retrying the same area at full rate, so regions that deny mob spawning become permanent spawn attempt hotspots that pay entity construction over and over for nothing. On Paper servers the same checks can run in PreCreatureSpawnEvent, before the entity exists. Cancelling there also ends the remaining attempts for the chunk in that spawn cycle, so the wasted work is gone almost entirely. Measured on a flat test world with a region denying mob-spawning over the whole spawn range and the mob cap kept empty, the attempt rate around a single player collapsed from roughly 75000 attempts per second to roughly 60 per second, with no entities constructed at all. The new listener mirrors the natural spawn conditions from onCreatureSpawn exactly: activity halt, block-creature-spawn, mob-spawning and deny-spawn region flags, and block-ground-slimes. All other spawn reasons keep going through the existing CreatureSpawnEvent checks unchanged, and the listener is only registered when the Paper event class is present.
    • Move the pre spawn handler into the existing Paper inner listener Review feedback: platform specific code lives in the Paper inner classes of the main listeners, and WorldGuardEntityListener already has one for EntityZapEvent, so the handler moves in there and the separate listener class is gone.
    • Match the HIGH priority of the other protection handlers
    • Extract the shared spawn checks into a method used by both handlers The pre spawn handler duplicated the...
rasmus kjær damgaarda month ago
c90c4838
  • Add Cause tracking for SulfurCube (#2295)
vladimir turov2 months ago