Closed TomLewis closed 2 years ago
No, I'm no longer supporting FAWE. Please get rid of the plugin and use vanilla WorldEdit, theres no need for FAWE.
woah, that is a bold, bold statement.
There are plenty of reasons for FAWE, Doing //regen on large selections of land to bring new terrain in because you are moving from 1.12.2 to 1.17, thats one we will be doing for the following months easily.
I use fawe for CLI manipulation of schematics, so I can have auto re-setting areas in my world.
I use fawe for GriefPrevention and WorldGuard protection with my regen team so that they can keep the world clean and fresh without the worry of wiping someones claim.
FAWE is far from "theres no need for FAWE." Theres a hell of a lot of reasons its required to run a server.
And there are even more reasons not to use it. Its the main source of problems and huge headache for developers. You can do all of those things with vanilla WE without causing any problems with other plugins, or corrupting your world.
Can I just disable the WorldGuardExtraFlagsPlugin WE integration? I don't need it at all, then we can both carry on. I looked and I cant seem to find a "WorldGuardExtraFlagsPlugin" plugins folder with settings?
No, but as far as I remember you can just ignore that warning and FAWE automatically disables the WE integration. Or you can do as it says and allow the plugin to run.
Could we please get a config even if its just this one value to toggle and a reload for the config.
I just find this problem for a few moments and I completely fixed it.
You go to config.yml in FAWE's folder and scroll down until you see extent's lore following my picture and input "net.goldtreeservers.worldguardextraflags.wg.wrappers.v7.WorldEditFlagHandler" under - "com.example.ExamplePlugin" lore
And then you restart your server once time.
My solution was to remove WorldGuardExtraFlags
I just find this problem for a few moments and I completely fixed it.
You go to config.yml in FAWE's folder and scroll down until you see extent's lore following my picture and input "net.goldtreeservers.worldguardextraflags.wg.wrappers.v7.WorldEditFlagHandler" under - "com.example.ExamplePlugin" lore
And then you restart your server once time.
Strangly I already have this there.
extent:
# 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:
- "net.coreprotect.worldedit.CoreProtectLogger"
- "net.goldtreeservers.worldguardextraflags.wg.wrappers.v7.WorldEditFlagHandler"
# Should debug messages be sent when third party extents are used?
debug: true
it seems my solution at the time was to remove WorldGuardExtraFlags! So I already had that in my settings for FAWE and stoll chose to remove the plugin. I would have to re-test again it was so long ago.
Can you please support the FAWE API, this plugin is blocking me (As OP) from even doing a copy in FAWE worldedit!