Event does not detect players correctly

When the event timer expires and the player is no longer inside the monument, the plugin still incorrectly detects them as being in the event area. As a result, it teleports them out of the zone. This issue occurs specifically with the Oil Rig monument.

Also on plugin reload its not clearing old bubbles/zones it seems

This is with the plugin unloaded

Changed Status from Pending to Work in Progress

I think the issue comes from players teleporting out of the monument zone. If they fly out, everything works fine. But when they teleport, the plugin doesn’t detect them leaving, so it assumes they’re still inside and the timer keeps running. Once the timer ends, it kicks them out to the edge of the monument zone, even if they’re nowhere nearby. This happens because the plugin never registered that they left via teleport. A solid workaround would be adding a command block inside monuments or detecting when a player teleports out. @jtedal

@jtedal

21 hours ago, Papi Rusty said:

@jtedal

Yes, I have seen your message and I have already replied to it in the discord.

No reply

4 minutes ago, Papi Rusty said:

No reply

This will be updated in the new global version of the plugin. So far, I can't tell you the exact timing of its release.

Not good. This is not useful in this state.

Just now, Papi Rusty said:

Not good. This is not useful in this state.

You can write to killyou with this problem. The bug does not appear due to my fault of the plugin, since if you had used some kind of NTeleportation, then this problem would not have occurred.

You can begin by fixing the issue that occurs when i reload the plugin and the zones do not dissapear. Fix this!

16 minutes ago, Papi Rusty said:

You can begin by fixing the issue that occurs when i reload the plugin and the zones do not dissapear. Fix this!

Perhaps this problem is related to the fact that the plugin is not working correctly. If I could see the errors that you get when you restart the plugin, it would speed up the solution to the problem.

We alredy talked about this. You said you were aware of the issue and that it only occured when the plugin was reloaded.

2 minutes ago, Papi Rusty said:

We alredy talked about this. You said you were aware of the issue and that it only occured when the plugin was reloaded.

Yes, but your specific problem may be related to other actions. What's the point of correcting if it might not help you?

4 minutes ago, Papi Rusty said:

We alredy talked about this. You said you were aware of the issue and that it only occured when the plugin was reloaded.

I'm just asking you to send me an error that appears when you restart the plugin. It's not difficult. 

No errors