[REQUIRED] Spigot/Paper Version Number:
This server is running Paper version git-Paper-235 (MC: 1.14.4) (Implementing API version 1.14.4-R0.1-SNAPSHOT)
Checking version, please wait...
Previous version: git-Paper-233 (MC: 1.14.4)
You are 1 version(s) behind
[REQUIRED] Description of the problem:
I was testing some things on my server, when I wanted to add some farmland. So I selected a small region and used //set farmland when suddenly a giant hole appeared in its surroundings. I don't know why this happened, probably because I updated to the latest version of fawe 1.14 in jenkins earlier. I just filled the area with some grass with //set 2 and it worked fine. Then I used set again and nothing happened. When I restarted the server and used //set again, the issue happened again.
Here are some screens I took:
https://prnt.sc/q9kwyvhttps://prnt.sc/q9kx6v
With light fixed:
https://prnt.sc/q9kwfkhttps://prnt.sc/q9kxrz
And the errors found in my console are probably by a glitched beacon plugin I was testing. Fawe didn't generate any errors.
NotMyFault
commented
4 years ago
Bug report for FastAsyncWorldEdit 1.14.4
[REQUIRED] FastAsyncWorldEdit Configuration Files: http://athion.net/ISPaster/paste/view/abebd3b6e8e14de3a6b89cb3d9a04cea
[REQUIRED] FastAsyncWorldEdit Version Number: &7FastAsyncWorldEdit-159 created by Empire92 &7FAWE version:
[REQUIRED] Spigot/Paper Version Number: This server is running Paper version git-Paper-235 (MC: 1.14.4) (Implementing API version 1.14.4-R0.1-SNAPSHOT) Checking version, please wait... Previous version: git-Paper-233 (MC: 1.14.4) You are 1 version(s) behind
[REQUIRED] Description of the problem: I was testing some things on my server, when I wanted to add some farmland. So I selected a small region and used //set farmland when suddenly a giant hole appeared in its surroundings. I don't know why this happened, probably because I updated to the latest version of fawe 1.14 in jenkins earlier. I just filled the area with some grass with //set 2 and it worked fine. Then I used set again and nothing happened. When I restarted the server and used //set again, the issue happened again. Here are some screens I took: https://prnt.sc/q9kwyv https://prnt.sc/q9kx6v With light fixed: https://prnt.sc/q9kwfk https://prnt.sc/q9kxrz
And the errors found in my console are probably by a glitched beacon plugin I was testing. Fawe didn't generate any errors.
How to replicate:
Plugins being used on the server: Plugins (77): AdminFun, AntiVPN, AuthMe, Autorank, BeaconPlus2, BetterChairs, BKCommonLib, BlocksHub, ChestShop, ChickenGlide, Citizens, Coins, ColoredTags, ConsoleSpamFix, CoreProtect, CrazyCrates, CustomPolls, DangerousCaves, DangerousNether, DeadSouls, DeathMessagesPrime, Elevator, EnderPearlFix, EntityTrackerFixer, EpicPluginAPI, EpicWorldGenerator, Essentials, EssentialsSpawn, FastAsyncWorldEdit, FastLogin, HackedCore, HackedServer, HolographicDisplays, IllegalStack, InventoryRollback, ItemEditor, JukeBox, Lasso, LightCleaner, LimitPillagers, LuckPerms, Magma, Matrix, mcMMO, Multiverse-Core, MyCommand, NoteBlockAPI, OpenInv, PearlRider, PlaceholderAPI, PlayMoreSounds, PluginConstructorAPI, PluginLibrary, PlugMan, ProtocolLib, PvPManager, RandomTeleport, RedProtect, Revenge, SexyMotd, SmoothSleep, SnowierSnow, SuddenDeath, SuperVanish, SwimmingHorses, TabList, UltimateChat, UltimateTimber, UpdatedSpawners, Vault, ViaVersion*, VillagerOptimiser, Votifier, VotingPlugin, WorldBorder, WorldEdit, XWeather
Checklist: