Aurélien

I can confirm this issue with a _new_ semaphore, might be caused by https://github.com/redisson/redisson/blob/master/redisson/src/main/java/org/redisson/RedissonSemaphore.java#L335

After more investigation you sould ensure that permits are correctly set, otherwise it _blocks_. Adding ``RSemaphore#trySetPermits(1)`` fixed the issue for the semaphore creation.

That's probably a _valid_ warning. Occured also running around my test map, too quickly I guess.

You should also try on Tuinity itself instead of Purpur, even if it depends on Tuinity.

Hey! If you need me to test something about your fight against last seen chat messages, I have a setup of a velocity proxy and two backend paper servers locally...

Can't reproduce from my own tests with the same config and build :/ Should I do something special ? 🤔

Wow thanks for that, but currently, there is no way to really include it on the plugin itself, maybe on StackMob's spigot page & a link in the default config!

> Yes I used /stackmob reload. > > Im no longer using a stacker plugin, they cause more lag then they prevent. Right, they cause lag, however they prevent more...

Good idea, but villagers shouldn't be authorized to stack themselves, just add them to type_blacklist ^^

Currently there is no option (trait) for villagers, maybe we could add one ? :p