-
Notifications
You must be signed in to change notification settings - Fork 12
FAQ
You can open an issue to suggest a mod to be added, although I can't give a guarantee that it will be added. Blocking a mod is a complicated process, requiring me to contact the mod authors, find out if there is a way to block and implement it.
Also, here is a list of mods that won't be added to the plugin in the forseeable future:
- WorldDownloader (the author has published his own plugin here)
- LabyMod (the authors have published their own plugin here)
- JourneyMap (no way to currently implement blocking)
eZProtector can't block hacked clients. Minecraft is Java based and there isn't any reasonable way to detect changes to a client, because anything you add to detect changes to the client can just be removed or disabled by the client. Same applies to mods. The reason mod blocking works at all is because the mod developers added features to support server owners, a mod which wants to remain hidden could just hide itself, just because Minecraft is Java-based.
The plugin is doesn't block most of the mods in version 1.7. Why? Because most of the mods blocked implemented a blocking feature when 1.8 came out. Also, it is not 100% guaranteed that eZProtector will completely block the mods, because anyone with a bit of Java knowledge can just remove the code that tells eZProtector that the mod exists.
Some mods use block codes (which are invisible strings of text in the chat) to disable themselves, this is why you receive those blank messages. There isn't anything that can be done about it. If you are really annoyed by that, you can disable the mod blocking feature.
SmartMoving and Schematica blockings do not work in the latest release, since I was unable to contact the developers to get information on how to block the mods. I'll try to
If you need help with the plugin and the documentation doesn't help you, be sure to ask for support on Discord!