Object: I don't see the point of adding this to Freedom-01, however I do believe that it would be useful in master builder worlds.
Bumping for further feedback.
since we are moving to permissions, it's entirely likely that we can revisit a lot of these older plugins which caused us issues in the past. But when it comes down to it, if it isn't logged it ain't gonna make the cut
Iirc we have had many issues with attempting to use FAWE but idk if the circumstances behind that have changed
As noted in the original post, this plugin depends on FAWE to work. While I would love to replace AIDSyncWorldEdit with it, FAWE itself is riddled with ridiculous exploits (making changes that affect out-of-bounds selections causes server crashes) and flat out stupid features (who's brilliant idea was it to allow people to load in schematics from remote sources???) which prevent me from doing so. As such, we can't even begin to consider adding FastAsyncVoxelSniper since requiring FAWE is a deal-breaker.
As noted in the original post, this plugin depends on FAWE to work. While I would love to replace AIDSyncWorldEdit with it, FAWE itself is riddled with ridiculous exploits (making changes that affect out-of-bounds selections causes server crashes) and flat out stupid features (who's brilliant idea was it to allow people to load in schematics from remote sources???) which prevent me from doing so. As such, we can't even begin to consider adding FastAsyncVoxelSniper since requiring FAWE is a deal-breaker.
Is worth noting that working out how to move to FAWE is on the backlog, if this suggestion has support we can always approve it but block it by the FAWE Ticket as I've had to do with a number of other plugins that people want but have dependencies on FAWE
(who's brilliant idea was it to allow people to load in schematics from remote sources???)
just quickly that could be changed when we ever switch to a diffrent way of doing permissions cause you can just block that command
(who's brilliant idea was it to allow people to load in schematics from remote sources???)
just quickly that could be changed when we ever switch to a diffrent way of doing permissions cause you can just block that command
The exploit is through the schematic loading command and blocking //schem load won't go down very well with the community.
just quickly that could be changed when we ever switch to a diffrent way of doing permissions cause you can just block that command
The exploit is through the schematic loading command and blocking //schem load won't go down very well with the community.
Simple, just switch to Plex for the command blocker and block it using regex
(who's brilliant idea was it to allow people to load in schematics from remote sources???)
What happens if you were to go in to FAWE's config and delete the link for the web interface?
Don’t have an account yet? Register yourself now and be a part of our community!
