Jordan

I think that the issue is slightly poorly named. It seems to me that the issue that "FAWE ignores the setBlock method in subclass of world" which is exactly expected...

Yeah so you really shouldn't be using a world here, and need to create a custom extent, the current process for which is to listen to EditSessionEvent and then set...

Yeah ultimately this behaviour should be going into a processor. Setting blocks via an extent block-by-block is much slower than using processors. Examples can be seen at https://github.com/IntellectualSites/FastAsyncWorldEdit/blob/main/worldedit-core/src/main/java/com/fastasyncworldedit/core/extent/DisallowedBlocksExtent.java#L126-L167 and https://github.com/IntellectualSites/FastAsyncWorldEdit/blob/main/worldedit-core/src/main/java/com/fastasyncworldedit/core/extent/StripNBTExtent.java#L105-L151

I think it might specifically be the layer brush. It's the only command in FAWE that accepts/requires a "pattern list" argument.

> The casts to `char` should only be present in the bukkit module, but I'm fine with changing it to int there too. I'm not sure that's something we can...

Going to close in favour of #2427 as from what I understand it is just passengers now

#2746 implements block updates but not block validation

This is simply adding NBT to an item in config.

Is this still occurring? The error message has been updated to give a little more information on the heights involved so if it still occurs, these errors would be useful...

I do not think we want to be forcing BukkitWorld objects to be kept in memory, as if a world is unloaded and loaded again we'll have garbage objects kept...