Patch Loader

This page explains how we ensure that different maps work together without conflicts, and what you need to do on your end.

---

🧩 Shared Compatibility System

All TStudio resources rely on a central compatibility system powered by:

• tstudio_zmapdata – Shared map data used by all maps.

  • patch_loader.lua – Our custom loader that detects installed maps and activates fixes automatically.

• tstudio_maps_patches – A dedicated folder for automatic compatibility patches.

You don’t need to configure anything manually. Once you follow the folder structure, the system will:

---

🗂 Recommended Folder Structure

Make sure your resource structure looks like this:

resources/
├── [tstudio_maps]/
│   ├── tstudio_map1
│   ├── tstudio_map2
│   └── ...
└── [tstudio_maps_patches]/
    ├── tstudio_zpatch_map1_map2
    └── ...

---

⚙️ server.cfg Setup

To ensure correct loading order, your server.cfg should include:

ensure [tstudio_maps] # <-- Containing tstudio_zmapdata

❗ Do not manually start the tstudio_maps_patches folder — it is handled by the system.

---

🔍 How It Works

Our patch loader script:

• Detects which maps are active

• Sorts and prioritizes necessary patches

• Starts only the relevant fixes to avoid overlap or performance impact

This means: you can freely combine TStudio maps without worrying about compatibility or patch conflicts.

---

🧪 Before You Go Live

We recommend:

• Always testing new map combinations on a development server

• Keeping tstudio_zmapdata updated

• Never renaming patch or map resources

---

🆘 Need Help?

If you’re experiencing issues or unsure whether a patch is active, our team is here to assist:

👉 Join the TStudio Discord