Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 2 months ago
All versions
0.3.0+26.1.2
Release
v0.3.0+26.1.25 months ago 342
Compatibility
Minecraft: Java Edition
26.1.2
Platforms
Folia
Paper
Changes
v0.3.0+26.1.2: Servux Direct Paste end-to-end
Added
- Real Litematica 0.27.6 clients can now Direct-Paste their schematics to the server with full block-state, tile-entity, entity and pending-tick fidelity, validated in production with 869,514 blocks + 6,516 TEs in 5.6 s.
- Inline
LitematicaPastetask handler (the maruohon Litematica payload schema, separate from the upstream Servux multi-frame Transmit protocol; both now handled). - Servux BulkRequest fulfillment with per-player rate limiter.
- Easy Place V3 server-side scaffold (PacketEvents 2.7, gated off by default).
- Java protocol bot for autonomous validation (
test-harness/protocol-bot/). - Local Fabric client harness for visual smoke testing.
Fixed
- Brigadier
StackOverflowErrorat command registration (recursive flag dedup via bitmask). /litematica pasteparses off the command thread → no more Folia Watchdog ERRORs on big files.PackedLongArrayswitched to compact cross-word packing (the.litematicformat).- 7 Servux wire-format discrepancies vs upstream
sakura-ryoko/servux 26.1.2-0.10.2. - PacketSplitter cap raised 16 MiB → 128 MiB, configurable.
- Proactive
S2C_METADATApush 3 s after PlayerJoin so Litematica clients enter Servux mode without user action.
Production gotchas documented (in README + TUTORIAL)
- Litematica client config: must set
ENTITY_DATA_SYNC = truein Generic config;PASTE_USING_SERVUX = truealone is useless. - Velocity 3.5: set
[packet-limiter] decompressed-bytes-per-second = -1(default 5 MiB/s kicks Direct Paste). - Paper: add
-Dpaper.playerconnection.keepalive=120for clients running DataFixer on old.litematicfiles.
Performance
- 4,194,304 blocks + 629,533 tile entities in 9.5 s (stress fixture).
- 870 k blocks + 6.5 k tile entities in 5.6 s (real client Direct Paste).
- 62 JUnit tests + 3 smoke harnesses all green.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:3V8UVQdb:jBB7u0L0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3V8UVQdb:jBB7u0L0"
}

