You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just like the title says, add a command to it so that you can disable block logging temporarily. Cuz as far as i know, only way to disable it if your using this plugin is to stop the server and remove it. Disabling it via your block logging plugin does not work. We have WORLDEDIT logging disabled in coreprotect, but its still being logged because of this plugin.
The text was updated successfully, but these errors were encountered:
BlocksHub does not log WorldEdit changes by itself it requires support by other plugins. BlocksHub is ONLY a common library for other plugins to use. By design it does not control if the blocks are logged.
You didnt get what I said. I know blockshub doesnt do the logging its self. It sends the info to the appropriate plugins so it can be logged. The only way to disable that feature temporarily is to remove blockshub. Having a command to temporarily disable that feature would be helpful. Other night I was pasting a 57 million block schematic that pasted fine, but the server continued to lag after the fact. I believe it was due to core protect shitting itself from 57 million block changes. I had to force down the server and restart it. The paste never got saved as the map saving function in minecraft did not get called.
Btw, this plugin should respect core protects settings. I have WE logging disabled in core protect by default, and it still records it. I keep this plugin on the server so that I can log certain WE's and be able to remove em later if need be.
As I said BC is only a library plugin and for other plugins to use. You should disable block logging inside the plugin that uses BC.
To disable world logging in BC you need to change the BC config. If you want to do it online change the config and force BC reload using the proper command.
Just like the title says, add a command to it so that you can disable block logging temporarily. Cuz as far as i know, only way to disable it if your using this plugin is to stop the server and remove it. Disabling it via your block logging plugin does not work. We have WORLDEDIT logging disabled in coreprotect, but its still being logged because of this plugin.
The text was updated successfully, but these errors were encountered: