EssentialsX random teleportation bug
LeoS0 opened this issue ยท 15 comments
EssentialsX version (essentials 2.0.1-b448
):
Server software (Spigot 1.12
):
EssentialsX config (if applicable):
Basically every now and then a random tp starts. Without triggering anything, it doesn't even output a error. Here is a basic review on how it goes https://www.youtube.com/watch?v=iBwBN_HkeA4 I've been trying to fix it for weeks now by removing and disabling plugins.
Thanks
Do all users experience this?
This looks like a plugin conflict - what plugins do you have installed?
Once it starts some of the users do. Not everyone, also the only plugin that is custom is our STCore. It allows players to fly within a towny area by typing /tfly but my developer said that it hasn't got anything to do with essentials.
You can join the #drtshock channel on EsperNet if you prefer, but anyone who is intending to help needs to know what plugins you have installed and ideally it should be public so we can identify and help solve similar issues in the future.
Is it possible to do this in private somehow? As we don't like to share our plugins in public.
I could send a screenshot on my plugins through a private chat and once we've found the problem we can post which plugin it was.
Thanks
Could I just send the image through discord or Skype? Because nobody is answering on there.
Thanks
We don't have any private support channels. I don't see the issue with sharing your plugins - there isn't any security issue if your server is configured correctly.
Is it only happening on that specific location? Try removing the RandomCoords plugin and see if the problem persist.
My best best is to use the simple and easy debugging method.
Take half the plugins out, if it persist, take half more.
If the problem disappeared, put the plugins you took back and remove the other half.
Do it until you have one plugin left and there you go!
Use the test server which you have set-up (as a competent admin) that mirrors your production environment.
You do have a test server, right?
That isn't really the best option here
It actually asymptotically is the best option. It identifies the offending problem in O(log n) steps, which is much better than removing plugins 1 by 1 in O(n) time! Here's a proof:
That isn't really the best option here. The tp bug doesn't happen instantly, it happens after a few 1 or 2 days. Imagine removing half of the plugins for 2 days with a playerbase of 40 players...I'm sure you can figure out why that isn't the best idea here..