LitematicaFolia - серверная Litematica для Paper и Folia

First release with an external contribution: CoreProtect support, by UPSOKen. Thanks for a clean PR. Optional hook, no-op default, and it survives CoreProtect dying mid-paste without touching the paste itself.

Added

• CoreProtect integration. Pasted block changes are now recorded in CoreProtect when it's installed, under the player who started the paste (console/RCON pastes log as #litematica). Replacements are logged WorldEdit-style: removal of the old block, then placement of the new one, so /co i and /co rollback behave exactly as they do after a WorldEdit operation. Unchanged blocks are skipped (re-pasting the same schematic writes zero records). Block states only for now; tile-entity NBT and entities are not logged.
• logging.coreprotect config toggle (default true). Measured cost on a 4.19M-block stress paste: 5.4 s without logging, 7.1 s with it, plus one CoreProtect consumer-queue entry per changed block. If you paste city-sized schematics and don't need the audit trail, flip it off.

Changed

• Now built against the Paper 26.2 stable dev bundle (build 111). 0.5.1 was built on the build-62 beta bundle.

Compatibility

• Requires CoreProtect API v10+ to log (the plugin prints the detected API version at startup). No CoreProtect, a too-old build, or a failing one: clean no-op, pastes are never affected.
• Heads-up for 26.2 servers: stock CoreProtect CE 24.0 predates Minecraft 26.2 and disables itself at boot ("Minecraft 26.2 is not supported"). You need a newer dev or patched CoreProtect build to actually get records on 26.2. Until then the integration simply stays dormant.
• Tested on Paper 26.2 (build 111) and Folia 26.2: full unit suite, boot/paste/save smokes with and without CoreProtect, replacement semantics verified against the CoreProtect database, attribution checks, and the 4.19M-block + 629k-tile-entity stress paste on both plain and CoreProtect-enabled servers. Zero errors, all rows ingested. On Folia the logging calls run on region threads; no thread-safety issues in any run.

For 26.1.x servers, use the 0.4.x releases.