FastAsyncVoxelSniper

FastAsyncVoxelSniper

33.4k Downloads

Undo causing crash server

nyvlunx opened this issue ยท 6 comments

commented

Bug report for FastAsyncWorldEdit 1.16.2

[REQUIRED] FastAsyncWorldEdit Configuration Files:

https://athion.net/ISPaster/paste/view/0e2cbd77df53487ba3d7bd30708946c1

[REQUIRED] FastAsyncWorldEdit Version Number:

FAWE version:

  • Bukkit-Official(1.16-328;4771297)
    ---------------- Capabilities ----------------
    GAME_HOOKS: Bukkit-Official
    CONFIGURATION: Bukkit-Official
    USER_COMMANDS: Bukkit-Official
    PERMISSIONS: Bukkit-Official
    WORLDEDIT_CUI: Bukkit-Official
    WORLD_EDITING: Bukkit-Official

[REQUIRED] Spigot/Paper Version Number:

git-Paper-152 (MC: 1.16.2) (Implementing API version 1.16.2-R0.1-SNAPSHOT)

[REQUIRED] Description of the problem:

A player made /u 2 (for undo) and 10 second after there is a crash dump
here : https://pastebin.com/ZHnQNkj7

image

How to replicate:

Do /undo 2 and wait 10 second

Plugins being used on the server:

ArmorStandEditor, Autorank, BKCommonLib, BuildersUtilities, BungeeTabListPlus, Citizens, CraftingStore, Denizen, Depenizen, DiscordSRV, Essentials, EssentialsAntiBuild, EssentialsChat, EssentialsProtect, EssentialsSpawn, FastAsyncWorldEdit, goBrush, goPaint, HeadDatabase*, HolographicDisplays, IPWhitelist*, LightCleaner, LuckPerms, Multiverse-Core, PlaceholderAPI, Plan, PlotSquared, Prism, ProtocolLib, spark, Vault, ViaBackwards, ViaVersion, VoxelSniper, WorldBorder, WorldEdit, WorldGuard

Checklist:

  • I included all information required in the sections above
  • I made sure there are no duplicates of this report (Use Search)
  • I made sure I am using an up-to-date version of FastAsyncWorldEdit for 1.16.2
  • I made sure the bug/error is not caused by any other plugin
commented

Remove VoxelSniper and retry please. /u is a VoxelSniper command.

commented

I, I confirm that this is a voxelsniper command as it is not working here. Should I create a new issue on the voxelsniper github ?

commented

Yes please :)

commented

This might be relevant here as well.

commented

In 1.16.3 the same error happened. Might be relevant for future Pull requests

commented

This is fixed since @N0tMyFaultOG 's FAWE Update.