ReSkate Map Mods: Packaging, Sync and Fixes

How ReSkate map mods are packaged, why the level list goes empty, and how to sync custom maps with friends on v2.1.3, step by step.

Last Updated: 2026-10-30

ReSkate Map Mods: How Map Packs Load, Sync and Break

ReSkate map mods are ordinary mod packages with one extra job: they must register themselves as a level. A map zip carries Frostbite level data plus a reskate-levels.json file that tells the game the level's name and spawn points. If that file is missing, malformed, or built for an older protocol, the map installs, shows up in your mod list, and still never appears in the Levels menu. This page is about that layer — packaging, version gates, server sync and the failure modes that follow — as of ReSkate v2.1.3 (October 28, 2026). For the catalogue of maps and their download sizes, read the ReSkate maps overview instead.

ReSkate is a third-party open-source mod platform for skate., not an EA product. This site is unofficial and unaffiliated with EA, Full Circle or Dingo-Shenanigans.

Skatepark concrete and ledges standing in for a custom map pack
Skatepark concrete and ledges standing in for a custom map pack

Custom maps are level data first and content second — the registration file is what makes them playable.

What is actually inside a map mod

A working map pack is four things stacked together:

Layer File or folder What it does
Level geometry Frostbite layout.toc, CAS bundles, level TOC The actual terrain, props and collision
Registration reskate-levels.json Adds the level to the travel list and defines spawn points
Object families reskate-objects.json (newer packs) Declares placeable object families the map or its mods rely on
Metadata mod.json / manifest Name, version, author, and the protocol the pack was built against

Official source: ReSkate on GitHub — map mods ship Frostbite data (layout.toc, CAS files, level TOC) plus a reskate-levels.json file that registers the level and its spawn points.

The practical consequence: you cannot "just" drop a .toc into a folder and expect a playable park. Registration and geometry have to agree, and the manifest has to claim a protocol the game still accepts.

The two checks the launcher runs before PLAY

Since v1.0.4 the launcher merges your mod list before the game starts and names the mods it had to drop. That merge is where most map problems surface, in one of two shapes:

  • The pack is skipped entirely. Usually a corrupt download, a zip that was extracted and re-zipped by hand, or a manifest that claims a newer protocol than your build supports.
  • The pack loads but the level is absent. Almost always reskate-levels.json: wrong key names, a spawn point outside the playable bounds, or a level ID that collides with a base-game level.

If the merge step names a map, do not reinstall blindly. Read the name it printed, then check the mod compatibility notes for the current protocol generation before you touch anything else.

Protocol versions and the version gate

ReSkate's network and mod protocol has moved several times: 43 at v1.1.5, 44 at v1.1.7, 45 at v2.0.0 and 46 at v2.0.2. A map built for protocol 44 will still load in single-player on a 2.1.x build in most cases, but it is not guaranteed, and it will not survive a multiplayer session where the host runs a different protocol generation.

Offline is not proof

A map that loads offline is not proof that it works online. Test the map in a host-and-join session before you build a night around it.

The safest rule is boring: install map packs that were updated after v2.0.2, and prefer packs whose manifest version matches or exceeds your own build.

Syncing maps with friends

Multiplayer map sharing is manual by design. Everyone in the session needs the same map installed, and the same version of it — a 690 MB park and a 691 MB repack are different maps as far as the session is concerned.

What changed in the 2.x line helps here:

  1. Server map pools (v2.0.0). Hosts can define a pool of maps, and Load Random Parks picks from it instead of the whole install.
  2. Missing-map prompts now show size (v2.1.x). When you join a server running a map you do not own, the prompt tells you how large the zip is, so you know whether it is an 18 MB park or a 992 MB city port before you commit.
  3. Start map in the launcher (v2.1.x). Hosts can set which map the session opens on, which removes the "everyone load in, then travel" dance.

If a friend joins and cannot see the map, the order of checks is: same version string, same protocol generation, map enabled in their in-game MODS list, then the registration file.

Why big ports behave differently

Size is not cosmetic. The full Skate 3 port is 690 MB with roughly 36,400 downloads, Skate2Map is 992 MB with roughly 27,700, Skate3 University is 252 MB, Southbank is 129 MB, and Black Box Distribution Park is just 18 MB. Large ports carry more physics bodies, and physics bodies used to be the hard ceiling: the limit sat at 8,200 until v1.1.0 raised it to 65,000. Older guides that warn about body counts are describing a constraint that no longer applies in the same way, but load time still scales with pack size.

The mesh pool also adapts now: recent builds budget geometry against free RAM and the page file rather than assuming a fixed ceiling. On a 16 GB machine with a browser open, a 1 GB port can still stutter on first load — that is memory pressure, not a broken map.

A five-minute triage checklist

When a map mod misbehaves, work down this list before reinstalling anything:

  1. Confirm the zip is intact and was not re-archived after extraction.
  2. Open the pack and verify reskate-levels.json exists and parses as JSON.
  3. Check the manifest's protocol against your build (2.1.3 is protocol 46 territory).
  4. Disable every other map mod and retest — level ID collisions look exactly like corruption.
  5. Start a solo session on the map, then a two-player session.
  6. If it fails only online, compare version strings on both machines.

Maps that fail step 2 are not fixable by the launcher, and maps that fail step 5 are a sync problem, not a download problem. Everything else is usually a stale pack.

Browse packs on the Thunderstore ReSkate community or the skatemods index, and cross-check the platform's own release list. The base game is skate. on Steam; ReSkate itself is not distributed there.

FAQ

Why does an installed map not appear in the Levels menu? Almost always a missing or malformed reskate-levels.json, or a level ID that collides with a base-game level.

Do friends need the same map version? Yes. Same map, same version, and a compatible protocol generation; a repack counts as a different map.

Can a 992 MB port run on 16 GB of RAM? Usually, but first load is the stress point. Current builds budget the mesh pool against free RAM and the page file rather than a fixed ceiling.

More ReSkate Guides