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
Basically the feature that will prevent water/lava to flow near spawners (under certain conditions or globally and always)
Or at least prevent spawner watering if enemy is near spawner/territory
But i think the addition of anti-spawner-liquiding is a better idea, because people can just spread a lot of water around their spawners to keep the territory and stay strong for some period and yeah.
The text was updated successfully, but these errors were encountered:
or making this togglable just like spawnerlock command is togglable
(example /f spawnerliquiding - will enable/disable spreading lava/water over/near spawner blocks)
i think that feature is necessary because Enemy-Spawner-Mine won't prevent players from making sure that spawners in their faction territory are kept with them
Yes, the Enemy-Spawner-Mine is making sure player can't break it and put it in their inventory to save it if someone is raiding them, but they can water region in radius of their spawner like 10+ blocks, i am not sure that all servers will allow cannoning and i am not sure how many players would be smart enough to make cannon that can break that + depends on what server settings are
Also the one more important thing to notice
we need to check if player placed water/lava stream
if he did, it'll check if there is nearby spawner and it won't flow to the spawner in {x} defined radius blocks from it.
Basically the feature that will prevent water/lava to flow near spawners (under certain conditions or globally and always)
Or at least prevent spawner watering if enemy is near spawner/territory
But i think the addition of anti-spawner-liquiding is a better idea, because people can just spread a lot of water around their spawners to keep the territory and stay strong for some period and yeah.
The text was updated successfully, but these errors were encountered: