- This isn't necessarily targeting any fix, but I think we should be ensuring a ticket is being added to chunks "access asynchronously", as done by the getChunkAtAsync method
* Add paper adapter for 1.19.4
* Add paper module for 1.19.4
* Port 1.19.3 to 1.19.4
* Switch to Paperweight release
* Update worldedit-bukkit/adapters/adapter-1_19_4/src/main/java/com/sk89q/worldedit/bukkit/adapter/ext/fawe/v1_19_R3/PaperweightAdapter.java
Co-authored-by: Antti Koponen <koponen942@outlook.com>
* Update worldedit-bukkit/adapters/adapter-1_19_4/src/main/java/com/sk89q/worldedit/bukkit/adapter/impl/fawe/v1_19_R3/regen/PaperweightRegen.java
Co-authored-by: Antti Koponen <koponen942@outlook.com>
* Add 1.19.4 to release template
* Update refractions for regen support
* Bump paperweight
---------
Co-authored-by: TheMeinerLP <p.glanz@madfix.me>
Co-authored-by: Antti Koponen <koponen942@outlook.com>
* 1.19.3
* More fixes
* fix: compile time issues for 1.19.3
* fix: new mappings and GeneratorStructureState
* Add 1.19.3 to release and issue template
* Update dependencies for 1.19.3
* Update worldedit-bukkit/adapters/adapter-1_19_3/build.gradle.kts
Co-authored-by: Pierre Maurice Schwang <mail@pschwang.eu>
* avoid usage of ticking chunk future on paper
* fix entity handling
* fix entity handling but on spigot
* seems like no one uses spigot
Co-authored-by: Alexander Brandes <mc.cache@web.de>
* Only synchronise tree generation at the very lowest level
- Fixes#1681
* Perform the generate inside try-finally and actually use the resultant copied map to place blocks to the editsession
* Check result of generateTree and return null if failed
* feat: Add support for 1.19
* build: Update paperweight version
* fix: obfuscated names, invalid method signatures
* avoid NPE on config access
* build: Update paperweight
* implement no-op light engine to avoid stalled tasks that never complete
* Apply DelegateSemaphore fixes to 1.19 (#1782)
* Apply DelegateSemaphore fixes to 1.19
* Fixes
* Avoid using PalettedContainerRO#recreate as much as possible. Show an error or warning when we're forced to use it to help fix (#1784)
Co-authored-by: Pierre Maurice Schwang <mail@pschwang.eu>
Co-authored-by: SirYwell <hannesgreule@outlook.de>
Co-authored-by: Jordan <dordsor21@gmail.com>
