Skip to content

Multiplayer

Jump to bottom
zapzapwav edited this page Aug 26, 2026 · 2 revisions

Multiplayer

Cozy CIT works on servers. The one rule everything below follows from: the server and every client build their furniture from the packs in their own resourcepacks folder — so both sides need the packs, and the sets must match.

Folder layout

Server (self-hosted or a hosting panel's file manager — the top level where you see mods/ and server.properties):

(server root)
├── mods/
│   └── CozyCIT-neoforge-1.21.1-x.x.x.jar     (or the Fabric jar + Fabric API)
├── world/
├── server.properties
└── resourcepacks/          ← create this folder if it doesn't exist
    ├── Mizunos 16 Craft JE CIT_x.x.zip
    ├── Mizunos 16 Craft JE_x.x.zip
    └── (any other supported packs, as .zip — do NOT unzip)

Every player's client:

.minecraft
├── mods/
│   └── CozyCIT-neoforge-1.21.1-x.x.x.jar
└── resourcepacks/
    └── (the SAME pack zips as the server)

Copy the packs to the server — don't move them. Both sides need their own copy.

⚠️ The hosting-panel trap

Hosting services (Exaroton, Aternos, Apex and the like) have a "resource pack" option in their web settings. That is Minecraft's server resource pack feature — it sends a pack to players when they join. It is a completely different system and this mod cannot see it. If you add the packs there, the server still starts with zero furniture and every placed block vanishes instantly.

The packs must be actual .zip files inside a folder named exactly resourcepacks at the server root, created through the file manager. (You can use the panel's resource-pack option in addition if you want players to auto-download the visual pack — it just doesn't replace the folder.)

Setup steps

  1. Install the mod on the server (NeoForge, or Fabric + Fabric API).
  2. Create the resourcepacks folder at the server root and upload the pack zips into it.
  3. Restart the server — packs are read once, at startup.
  4. Verify in the server log. Success looks like:
[CIT] scan complete: 6 pack(s), classified: [hanana, heritage, maeflowers, mizuno, moondrop]
[CIT] registered 1956 furniture blocks from manifest

Failure names the exact path it checked:

[CIT] resourcepacks directory not found: /server/resourcepacks
[CIT] no supported CIT pack installed - furniture disabled
  1. Make sure every player has the same packs in their own client resourcepacks folder.

The pack sets must match

Both sides register blocks from the packs they find, so:

  • Server missing a pack a client has → that pack's blocks don't exist server-side, and placing them fails (they vanish instantly).
  • Client missing a pack the server has → the client doesn't know those blocks and may be refused connection with a registry mismatch error.

Pick one pack set for the server, distribute the exact same files to every player, and change it for everyone at once or not at all.

Practical advice

  • Decide the pack set before the world gets built. Removing a pack later deletes that pack's furniture from the world.
  • Share the actual zip files with your players rather than telling them to "download the pack" — different versions of a pack may register different blocks.
  • Back up the world before changing the pack set.

Verified

Tested on a dedicated server with all five supported packs: 1,956 blocks registered, placement, storage, shelf displays and rotation all working in multiplayer. The "server without packs" failure mode (blocks vanish on placement) was reproduced and confirmed fixed by exactly the steps above.

Cozy CIT

Clone this wiki locally