Generates a large number of warning logs per second.
LSK-LW opened this issue · 6 comments
Server Log,Mod Version: 1.0.27_X4116
[12:14:07 WARN]: Entity being removed for bounding box restrictions [12:14:07 WARN]: BB Size: 1,368 > 1,000 avg edge: 10.843 [12:14:07 WARN]: Motion: (0, 0.028, 0) [12:14:07 WARN]: Calculated bounding box: box[1269.7014977290967, 10.533436375575047, 3069.356473753732 -> 1277.2014982059338, 28.061436374680465, 3076.8564742305693] [12:14:07 WARN]: Entity bounding box: null [12:14:07 WARN]: Entity: EntityQuackos['老鸭子'/401679, l='world', x=1273.45, y=10.53, z=3073.11] [12:14:07 WARN]: Entity NBT: {AgeLocked:0b,IsChickenJockey:0b,Attributes:[0:{Base:4.0d,Name:"generic.maxHealth",},1:{Base:0.0d,Name:"generic.knockbackResistance",},2:{Base:0.25d,Name:"generic.movementSpeed",},3:{Base:16.0d,Name:"generic.followRange",},],Invulnerable:0b,PortalCooldown:0,AbsorptionAmount:0.0f,FallDistance:0.006378236f,HbmLivingProps:{hfr_fibrosis:19290,hfr_asbestos:0,hfr_radiation:0.0f,hfr_blacklung:0,hfr_bomb:0,hfr_digamma:0.0f,hfr_contagion:0,hfr_cont_count:0,},InLove:0,DeathTime:0s,WorldUUIDMost:6902671731839225623L,DropChances:[0:0.085f,1:0.085f,2:0.085f,3:0.085f,4:0.085f,],PersistenceRequired:0b,Spigot.ticksLived:683960,HealF:4.0f,Age:0,Motion:[0:0.0d,1:0.027999999105930328d,2:0.0d,],Leashed:0b,UUIDLeast:-3013100584753196806L,Health:4s,Bukkit.updateLevel:2,Air:300s,OnGround:0b,Dimension:0,Rotation:[0:116.92627f,1:0.0f,],UUIDMost:4705957522005847583L,Equipment:[0:{},1:{},2:{},3:{},4:{},],CustomName:"",Pos:[0:1273.4514979675153d,1:10.533436375575047d,2:3073.1064739921508d,],Fire:300s,CanPickUpLoot:0b,HurtTime:0s,AttackTime:0s,WorldUUIDLeast:-6178962198364874037L,CustomNameVisible:0b,}
What kind of server software are you running? From a quick search, Sponge apparently has a feature like this which tries to despawn entities that are too big, which seems to backfire since Quackos is unkillable. Try shutting down the server and changing the server's config value max-bounding-box-size
either to something larger than Quackos' size or to 0 to turn off size checks (info from here). If you don't have a Sponge server, the config might be called something else.
What kind of server software are you running? From a quick search, Sponge apparently has a feature like this which tries to despawn entities that are too big, which seems to backfire since Quackos is unkillable. Try shutting down the server and changing the server's config value
max-bounding-box-size
either to something larger than Quackos' size or to 0 to turn off size checks (info from here). If you don't have a Sponge server, the config might be called something else.
Found this option in cauldron.yml, thank you
settings:
load-chunk-on-forge-tick: false
check-entity-max-speeds: false
entity-max-speed: 100
check-entity-bounding-boxes: false
#change to false
load-chunk-on-request: true
entity-bounding-box-max-size: 1000
dump-materials: false
chunk-gc-grace-period: 0
What kind of server software are you running? From a quick search, Sponge apparently has a feature like this which tries to despawn entities that are too big, which seems to backfire since Quackos is unkillable. Try shutting down the server and changing the server's config value
max-bounding-box-size
either to something larger than Quackos' size or to 0 to turn off size checks (info from here). If you don't have a Sponge server, the config might be called something else.
On the server, some block destruction caused by explosions cannot be prevented by plugins,
Is it possible to use a config file to decide whether an explosion can break blocks?
Many of NTM's explosions use a completely different system compared to those from vanilla, which means that plugins for land protection won't work against things like mining explosives and nukes. The best ways of limiting destruction is by reducing the blast sizes of nukes in the config, limiting the supply of weapons (which can be done in a number of ways like modifying recipes via assembler config or CraftTweaker, or by setting up a server shop) or outright banning bombs that might be too excessive.
Many of NTM's explosions use a completely different system compared to those from vanilla, which means that plugins for land protection won't work against things like mining explosives and nukes. The best ways of limiting destruction is by reducing the blast sizes of nukes in the config, limiting the supply of weapons (which can be done in a number of ways like modifying recipes via assembler config or CraftTweaker, or by setting up a server shop) or outright banning bombs that might be too excessive.
In some cases, the anvil will disappear immediately after falling