All versions
1.0.0
Beta
Only Server Gunpack 1.0.04 months ago 20
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
1.0.0 — 2026-06-27
Initial release.
Features
- Server-side gunpack distribution — packs are scanned from
server_gunpacks/, streamed to clients on join, and loaded entirely in memory - AES-256/GCM encrypted transport — per-session random key, per-chunk random IV; packet capture yields ciphertext only
- Key masking — encryption key is XOR-masked before transmission
- Resumable transfer — interrupted downloads resume without restarting
- CRC32 integrity — chunk-level and full-pack checksum verification
- Zero local footprint — gunpack data never touches the client filesystem, auto-cleared on disconnect
- No Mixin — plugs into Forge's standard
RepositorySourceandPackResourcesAPIs; zero conflicts with other mods - Sequential pack delivery — packs are sent one at a time with ACK flow to avoid network congestion
- Anti-collision sending — per-player send generation counter prevents stale transfers
- Priority override — server packs load at
Pack.Position.TOP, taking precedence over any local duplicates - External pack provider API — other server mods can register packs programmatically via
ExternalPackRegistry - Client adapter API — client mods can hook post-download processing via
ClientAdapterRegistry - Commands:
/osg statusand/osg reload - i18n — English and Simplified Chinese translations
Server Config
[gunpack_paths]
gunpackDirectory = "server_gunpacks"
[transfer]
maxPackSizeMB = 100
chunkSizeBytes = 1048064
transferTimeoutSeconds = 120
requireAckBeforeJoin = true
Requirements
- Minecraft 1.20.1
- Forge 47.3+
- TACZ 1.1.8
Known Limitations
- Encrypted packs (e.g. Arcana) are not supported — use their native loader
- Reload may cause a brief client freeze while TACZ processes resources — this is expected
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:fYgT4bsA:wkHikBy2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fYgT4bsA:wkHikBy2"
}

