Logging WorldEdit
StonFlip opened this issue ยท 5 comments
instead of the original worldedit, I use the more convenient FAWE (FastAsyncWorldEdit)
and coreprotect does not log FAWE actions
Could you add FAWE support in future updates?
You could have looked at earlier issues: #234 (Also FAWE can corrupt your world.)
As I understand it, it says to use an older version 2.4.1, but I'm using the latest version from the site and is it possible to fix this without changing the FAWE version?
I'm not sure if it is still needed but have you tried putting Blockshub on the server also?
You could have looked at earlier issues: #234
(Also FAWE can corrupt your world.)
If you don't know...
CoreProtect has added FastAsyncWorldEdit compatibility starting with v21.0.
Therefore, it is not necessary to use BlocksHub if you are using this or later versions.
To use FastAsyncWorldEdit and CoreProtect to log block edits with set commands, etc., FastAsyncWorldEdit settings must be changed as follows:
plugins/FastAsyncWorldEdit/config.yml
--- config.yml.old 2022-06-15 04:44:06.753611000 +0900
+++ config.yml 2022-06-15 04:46:38.612349700 +0900
@@ -89,7 +89,7 @@
# Don't bug console when these plugins slow down WorldEdit operations
# - You'll see a message in console or ingame if you need to change this option
allowed-plugins:
- - "com.example.ExamplePlugin"
+ - "net.coreprotect.worldedit.CoreProtectLogger"
# Should debug messages be sent when third party extents are used?
debug: true
That they work is confirmed in FastAsyncWorldEdit build #291 on 10/13/2022 and CoreProtect v21.2.
However, at this time there is a problem that even with this method, the results of copy/paste edits are not logged.
According to Intelli, if you need to resolve this issue, please create a pull request.
- Reference: #234