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 14, 2020. It is now read-only.
Describe the bug
mobs stacked in one of my player's land gets instantly killed but not for other players which worked fine
To Reproduce
Steps to reproduce the behavior:
-create 3 spawners stack ontop of each other and creating a star shape.
-Use grief prevention and grief prevention flags
when leaving land claim, mob stack works fine and doesnt gets instantly killed
when enter that particular player's claim land, mobs gets instantly killed.
Expected behavior
mobs shouldn't be instantly killed and it should work for all players
Screenshots/Videos
If applicable, add screenshots to help explain your problem.
Bukkit/Spigot AND StackMob version:
paper 1.14.4 and stsackmob 4.0.2
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
mobs stacked in one of my player's land gets instantly killed but not for other players which worked fine
To Reproduce

Steps to reproduce the behavior:
-create 3 spawners stack ontop of each other and creating a star shape.
-Use grief prevention and grief prevention flags
when enter that particular player's claim land, mobs gets instantly killed.
Expected behavior
mobs shouldn't be instantly killed and it should work for all players
Screenshots/Videos
If applicable, add screenshots to help explain your problem.
Bukkit/Spigot AND StackMob version:
paper 1.14.4 and stsackmob 4.0.2
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: