Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stargate and Matrix anti-cheat #2

Open
KabanFriends opened this issue Oct 20, 2019 · 2 comments
Open

Stargate and Matrix anti-cheat #2

KabanFriends opened this issue Oct 20, 2019 · 2 comments

Comments

@KabanFriends
Copy link

When a player enters a gate, an anti-cheat plugin Matrix detects the teleport movement as cheating.
I reported the issue to Matrix, but dev said Stargate uses "wrong way" to teleport. So Matrix devs aren't going to fix the issue. (re-ovo/Matrix-Issues#923)
Since Matrix isn't going to support Stargate, can Stargate support Matrix? And please fix the "wrong way" to teleport which Matrix devs said. There must be more regularly used way to teleport players.

@KabanFriends
Copy link
Author

Matrix anti-cheat isn't open source so you can't see how it detects movement, but I think it doesn't trigger teleport movement as cheating IF the plugin used the recommended way to teleport.

@PseudoKnight
Copy link
Owner

So, that bit of code was last changed by Drakia eight years ago to use the PlayerMoveEvent's new setTo() method at the time. Stargate isn't doing anything crazy here, and many popular plugins modify the move event destination. It shouldn't interfere with a plugin listening to the event on the earliest priority to detect odd player movements.

But I understand detecting cheats is complex and challenging. Unfortunately I currently have no way of knowing why this is a problem for them because they didn't tell us and their source is obfuscated. That's annoying and is making this harder than it should have been. In my experience it's anti-cheat plugins that are far too rigid and a compatibility nightmare, so not communicating doesn't help. It just sounds like they're hostile to other plugins. Quote:

You should be compatbile with Matrix, not Matrix compatible with you.

sigh

But I'm maintaining this project for people like you, so let's see what I can do without breaking something else -- lol. One alternative is to change it to call the teleport in the handler (like it was eight years ago, ironically) instead of letting Spigot call the teleport after all handlers are done. I looked up three other plugins and they seem to teleport on LOW, HIGHEST, and MONITOR priorities. Maybe these approaches are compatible with Matrix? I'm thinking HIGHEST might be best, since this still allows us to cancel entering the portal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants