Disabled plug-in for specific item or players or zone
GabrielChev opened this issue ยท 5 comments
Hello,
Is their a way to disabled the plug-in just for specific item or zone ?
I use the plug-in but i want continue to use the new version at the same time in the same server.
For exemple can i rename a sword and re-apply the 1.18 stats for this specific item renamed ?
Other way : Is it possible in a specific zone to disable all the plug-in on the same server and same world?
Thanks a lot in advance
The plugin works on a worlds or player level, not on an item level. You can specify which worlds the whole plugin or the various modules are enabled in by changing the worlds
list in the config. You can also use the toggle
and enable/disable
commands to change the attack version for players programmatically. More information about the commands can be found here.
The plugin does't works correctly on a world level. I blacklisted a world but the calcul of armor resistance (or domage taken i don't know) continue to be modify on it. Can you help me on that, i have disabled ALL in config file for this world and add it in blacklist
So, you request a new feature, because an existing feature has a bug ?
May be we can try to fix the bug before to add new feature ๐
I think we can begin to try to debug if you give us your configuration file, the version of the plugin and the version of the server.
Please check also you don't have error in logs.
Hello,
Thanks a lot for your answer.
I found the bug after i made my request, it's not a question anymore.
I put the world "world" in all blacklist for turn-off the plug-in just in this world.
But i noted that :
- The shield does not deflects the arrow like normally in vanilla 1.18
- The calculation of damage is not the same as in vanilla (Full Protection 4 netherite is much too resistant, don't know if it's because of the damage given or protection enchant or netherite)
The server is Paper-Spigot version 1.18.2
Here is my config.yml (in txt format for transfer) :
No log error
Thanks in advance for your help
Following the bug at #615