New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WorldEdit //regen issues #124
Comments
I have updated my ticket with more information! |
Hello, Thanks for problem description. |
I have attached the plugins folder. To reproduce:
|
Thanks, I've reproduced problem. |
Opened the issue @ boy0001/FastAsyncWorldedit#273 as well |
I conclude that this isn't an issue: comment on the other ticket |
Therefore I'm considering this is bug on FAWE side, but I anyway applied change to convert "fake blocks" to AIR. This should fix the problem you mentioned. You can wait until new release or could compile plugin by your self from DevotedMC fork. |
Thanks @Aleksey-Terzi, it's really scary to players when you go to regenerate something and it turns into a cluster of ores! |
Just confirming. The issue appears to be fixed, awesome! Thanks - IOU a beer |
Hello! Using WorldEdit (and FAWE - so this may be an issue with just FAWE or worldedit) and Orebfuscator and the
//regen
command causes the blocks to become random ores/gravel etc - or huge portions of coal.Unfortunately no screenshot here yet (whenever it happened I was on a live server so I had to quickly unload orebfuscator and redo it), but I will undertake some further testing soon for you. Is there anything I should do while testing further to provide further useful information?
This bug was also present in the previous version. But I found it doesn't occur when I take off Orebfuscator
Edit 1: Testing
Versions:
Plugins (5): FastAsyncWorldEdit, Vault, ProtocolLib, WorldEdit, Orebfuscator4
Start to finish log: http://pastebin.com/nKZ7Vc04
If I take off Orebfuscator this no longer occurs - the above example is a much nicer result than usual.
Error that is thrown:
Disabling Orebfuscator fixes the issue.
However, disabling FastAsyncWorldEdit also fixes the issue. Perhaps @boy0001 would like to take a look too?
The text was updated successfully, but these errors were encountered: