Only Server Gunpack

# OSG — Online Server Gunpacks **Server-side TACZ gunpack distribution. Zero setup for players — join and play. Pure in-memory, nothing touches disk.** --- ## ✨ What problem does this solve? > **Protect gunpack authors' art assets + hassle-free server management.** > Packs live on the server, players do nothing. Versions are always in sync. No more "I installed it but it's not showing up". > Players load into memory on join, cleared on disconnect — authors' assets are protected from copying. --- ## 🆚 Comparison | | 🗂️ Manual | ⚡ OSG | |---|---|---| | **Player setup** | Download & install each pack | **Zero — join and play** | | **Updates** | Everyone re-downloads | **Replace once on server** | | **Security** | Files exposed on disk | **In-memory + encrypted transport** | | **Consistency** | Version mismatches cause bugs | **Server-enforced** | --- ## 🎯 Features | Feature | Description | |---|---| | ✅ **Server digital signature** | Client rejects fake servers, anti-phishing | | 🔄 **Forced version sync** | Update once on server, everyone gets it — no more "I installed it" | | 🧹 **Zero maintenance** | Players install nothing. Adding a new pack requires no server-wide announcement | | ⚡ **No TACZ modification** | Just feeds resources to TACZ in-memory | | 🧠 **Bonus protection** | Pure memory, players can't copy files — anti-piracy comes for free | | 📦 **Any format** | Folders or zips (zip is better) | | ✅ **All TACZ packs** | Except encrypted ones | --- ## 🔧 How It Works TACZ loads gunpacks through Forge's `RepositorySource` interface — it scans the `tacz/` folder, wraps each pack as a `PathPackResources`, and hands them to Minecraft's resource system. OSG does the exact same thing, but the files come from **memory** instead of disk: 1. Server scans `server_gunpacks/` → sends packs to clients over the network 2. Client assembles them in RAM → provides them as `PackResources` through the same `RepositorySource` interface 3. TACZ sees them exactly like local files — no difference. No Mixin. No patch. And the player never gets the raw file. > Think of it as clicking "Done" on the resource pack prompt, but everything stays in RAM. --- ## 📥 Installation | Side | What to do | |---|---| | 🖥️ **Server** | Install OSG, put packs in `server_gunpacks/` | | 💻 **Client** | Install OSG. **That's it.** | > 💡 **Tip**: Put frequently updated packs, or packs you don't want players copying, in `server_gunpacks/`. Stable base packs can stay local — saves bandwidth and hassle. --- ## 📋 Requirements `Minecraft 1.20.1` `Forge 47.3+` `TACZ 1.1.8` --- ## ⌨️ Commands | Command | Description | |---|---| | `/osg status` | Show loaded packs | | `/osg reload` | Server-side hot reload (connected players need to rejoin) | --- ## ❌ Not Supported > ⚠️ **Encrypted packs** (Arcana, etc.) — use their original loader. OSG does not decrypt. --- ## ❓ FAQ <details> <summary><b>🔄 How do I update packs?</b></summary> Replace files in `server_gunpacks/`, run `/osg reload`. Connected players keep the old version; new joiners get the update. Packs loaded via the API cannot be hot-updated. </details> <details> <summary><b>⚖️ Is this copyright infringement?</b></summary> OSG is a neutral transport tool. Technical facts: - **No modification** — CRC32 integrity ensures byte-level fidelity. The tool does not alter any gunpack data. - **In-memory loading** — Pack data is loaded into memory and cleared on disconnect. No permanent copies are created. > ⚠️ **Important**: A neutral tool does not guarantee legality. Server owners must verify they have the right to distribute the packs they configure. Distributing unlicensed copyrighted material may still constitute infringement. Strongly recommend only distributing original or explicitly authorized packs. </details> <details> <summary><b>💾 Does this use a lot of memory?</b></summary> No — and it was already being used. TACZ loads all gunpack files into memory regardless of whether they come from the local `tacz/` folder or through OSG. The memory usage is **exactly the same**. OSG just skips the "write to disk, then read into memory" step — zero extra overhead. Data is cleared on disconnect and does not stay resident. </details> <details> <summary><b>🎨 How does this benefit gunpack authors?</b></summary> OSG does not change your copyright. Your art assets remain fully yours. - Players never access raw files (in-memory, cleared on disconnect) — your models, textures, and sounds cannot be casually copied and spread. - Server-side version management means no compatibility issues from outdated local copies. This isn't about pushing a new order — just giving creators who want to protect their work an option they didn't have before. </details> <details> <summary><b>🛡️ How does this prevent version mismatch bugs?</b></summary> All players load the exact same pack data from the server. No one can accidentally use an outdated local copy, because there are no l