Coreprotect v20 allows AWE/FAWE to hook directly into it, if I'm not mistaken. I won't get into the various intricacies of blockshub, but having NBT data being wiped after a rollback (and in some cases, block states as well) is incredibly annoying to repair.
Please for the love of Talos remove Blockshub
-
can we confirm that this problem is resolved by directly linking in to coreprotect though? i vouch even if the problem isn't fixed, because there's direct support for it now and blockshub is an absolute piece of garbage plugin
-
can we confirm that this problem is resolved by directly linking in to coreprotect though? i vouch even if the problem isn't fixed, because there's direct support for it now and blockshub is an absolute piece of garbage plugin
I might try to get a personal test server running tomorrow to see for myself. Though I suppose that the patch notes don't lie.
e: If it turns out to only support FAWE (since it only says FAWE) or something, then switch over to FAWE since it's a better plugin overall.
-
Talos?
You have committed crimes against Skyrim and her people. What say you in your defence?
-
Talos?
You have committed crimes against Skyrim and her people. What say you in your defence?
Nyan.
-
- Official Post
BlocksHub is necessary for AWE to interface with WorldGuard if I recall correctly.
-
BlocksHub is necessary for AWE to interface with WorldGuard if I recall correctly.
I'd say WorldGuarldExtraFlags since that's the one checking WE access but WG too might need it
-
BlocksHub is necessary for AWE to interface with WorldGuard if I recall correctly.
FAWE doesn't have that requirement afaik.
-
- Official Post
BlocksHub is necessary for AWE to interface with WorldGuard if I recall correctly.
FAWE doesn't have that requirement afaik.
We don't run FAWE currently and while it's on the backlog if we move to fawe it would also be the point we look at a number of other plugins to make sure the set of plugins makes sense when we move to fawe.
-
All of you who said it only works with FAWE are wrong. It does work with AWE. Add enable-awe: true to your coreprotect config file and it will work. the reason it's disabled by default is because when this feature was added, every server owner was still using blockshub and if coreprotect made it a default option it would have logged twice
-
All of you who said it only works with FAWE are wrong. It does work with AWE. Add enable-awe: true to your coreprotect config file and it will work. the reason it's disabled by default is because when this feature was added, every server owner was still using blockshub and if coreprotect made it a default option it would have logged twice
I see. Thank you for saying this.
-
Hella vouch, I can confirm that it works and logs properly from my testing
-
switch over to FAWE since it's a better plugin overall
FAWE is faster than AWE, yes, and it has a better license but AWE actually seems to do sanity checks unlike FAWE - hard object.
-
switch over to FAWE
fawe kinda stinky imo (FAI better :wink:)
object -
THIS POST IS NOT TALKING ABOUT FAWE, the main point of this post is to remove blockshub now that coreprotect adds native support for logging AWE, if y’all want to talk about FAWE make a separate suggestion
Please read before voting
-
THIS POST IS NOT TALKING ABOUT FAWE
Please read before voting
Yes, I know. If you read my post (I'm assuming you haven't due to this post you made in response) it was objecting to the notion of adding FAWE to the server.
-
Yes, I know. If you read my post (I'm assuming you haven't due to this post you made in response) it was objecting to the notion of adding FAWE to the server
It would've been clearer if you said something like "Object to adding FAWE, but vouch for removing BlocksHub."
I would like to see what Ryan has to say about this though, since he oversees most stuff like this.
-
- Official Post
I would like to see what Ryan has to say about this though, since he oversees most stuff like this.
Sorta touched on it about but specifically for Blockshub, if we don't need it and it's adding 0 value we should remove it.
I'll look to do some testing on the dev server at some point soon to verify that because it was suggested I think here or elsewhere that it is actively being used as part of the WorldGuard integration, so if that's not the case and it is redundant, then absolutely lets get rid.
-
It would've been clearer if you said something like "Object to adding FAWE, but vouch for removing BlocksHub."
I don't vouch for removing BlocksHub.
-
It would've been clearer if you said something like "Object to adding FAWE, but vouch for removing BlocksHub."
I don't vouch for removing BlocksHub.
y
