Layout
| Path | Contents |
|---|---|
Resources/Client/ | ZIPs sent to players (vehicles, maps, UI) |
Resources/Server/ | Server-side Lua / logic |
Install tips
- Stop the server before dropping large packs (optional but safer).
- Upload zips to
Resources/Client/— don’t nest incorrectly. - Restart; watch console for resource load errors.
- Join once yourself to cache downloads before a group event.
Desync prevention
- Document required mods in Discord.
- Update client + server resources together.
- Remove abandoned packs that break joins.
Related guides
Frequently Asked Questions
Client vs Server folders?
Client resources sync to players; Server Lua runs only on the host.
Desync / missing mods?
Ensure every driver downloaded required client resources; remove broken zips.
Where do files go on panel?
Under the server Resources/ tree in Pterodactyl File Manager.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.