IntellectualSites / FastAsyncWorldEdit

Blazingly fast world manipulation for artists, builders and everyone else: https://www.spigotmc.org/resources/13932/
Other
611 stars 218 forks source link

Edits are not displayed before chunk reload #847

Closed lusu007 closed 3 years ago

lusu007 commented 3 years ago

[REQUIRED] FastAsyncWorldEdit Configuration Files

/fawe debugpaste: https://athion.net/ISPaster/paste/view/e64973a2c55249cd9e02d6e8c38ee45d

Required Information

Describe the bug All actions performed with FAWE work without problems, but they are not displayed. The changes are only visible when the chunks are unloaded and loaded again. Also F3+A is not sufficient.

Can send-before-history be to blamed for this?

To Reproduce Steps to reproduce the behavior:

  1. Execute any action with FAWE (e.g. //replace diamond_block)
  2. Changes are not visible
  3. Fly away until the chunks are unloaded
  4. Fly back to the position where you did the change
  5. Changes are now loaded.

Plugins being used on the server

Arceon, Builders-Utilities, BungeeTabListPlus, Essentials, FastAsyncWorldEdit (WorldEdit), goBrush, goPaint, HeadDatabase, Hyperverse, LegendEssentials, LegendSchematicScatter, LuckPerms, Vault, VoidGenerator, VoxelSniper, WorldGuard

Checklist:

aurorasmiles commented 3 years ago

I'm not able to replicate your issue

lusu007 commented 3 years ago

I made a short clip to illustrate the problem. Its quality is a bit bad because Githubs file limit is at 10MB.

This is captured using the newest Paper and FAWE build. No stacktraces in console and same configuration as in the debugpaste above.

https://user-images.githubusercontent.com/10341994/104454443-26decd80-55a6-11eb-84ca-163b2db538ae.mp4

LaurenceBarnes commented 3 years ago

could you try to do //set stone multiple times? I wonder if it is shown then after the 2nd or 3rd time. This is what happened to me multiple times, but not consistently. Brushes seem to work fine though, at least for me.

lusu007 commented 3 years ago

Executing //set stone multiple times doesnt help.

LaurenceBarnes commented 3 years ago

I'm not able to replicate your issue

well I can though, on build-560 too.

I noticed that it happens when you do a small edit in a recently edited region. That is how I noticed it. I tested through every dimension we have, it only occured as I describe below.

Since I am copying over a lot of progress, whole dozens of chunks are changed. To adjust some things, I used FAWE in those newly pasted chunks to adjust landscape, and then the bug described in that issue occured to me, multiple times at different spots. In regions that haven't been edited in a while (at least a couple hours), it doesn't occur. It is really hard to reproduce.