PROJECT_JUMPMAPPING
Mapping guide · Unreal Engine 5.8 · Map Kit 1.0

project_jump Map Kit

Make a map, play it with the real movement in the editor, package it, share it. No code needed. New here? Read the six rules below, then follow the Quick start.

Read this first

Six rules. Most stuck maps broke one of them.

  1. Use Unreal Engine 5.8. Asked to rebuild modules? Say No: wrong version. More
  2. Keep everything in your map's plugin folder (YourPluginName Content in the Content Browser). Fab and Megascans imports get moved there for you when you package. More
  3. Never rename your plugin. Leaderboards and the Workshop use its name.
  4. Give everything players jump on box, convex or "complex as simple" collision. With sphere or capsule collision, or BSP brushes, players can get stuck on edges and walls. More
  5. Add a Player Start, plus a Start and a Finish timer zone. More
  6. Test with Play in the editor as you build. When the map is finished, package it with Tools\PackageMod.cmd and give it a final check in the game from Steam. More

1What you need

  • Unreal Engine 5.8 from the Epic Games Launcher (Library → Engine Versions → +). Any 5.8.x works; 5.7 or older won't open the kit.
  • The kit, unzipped to a short path like D:\JumperMapKit. Not in OneDrive or any other synced folder.
  • The game from Steam, to play your packaged map.

2Your plugin folder

Your map lives in its own plugin: a folder under Plugins\ that holds your level (or several) and every asset they use.

In this guide, YourPluginName stands for your plugin's name and YourMapName for your level's. Use your own names; they can be the same.

JumperMapKit\
  project_jump.uproject          <- the kit (never edit this)
  Content\                       <- the game's own assets: use them, don't change them
  Plugins\
    YourPluginName\              <- YOUR PLUGIN FOLDER, made once in step 3.2
      YourPluginName.uplugin     <- made for you
      Content\                   <- shows in the Content Browser as "YourPluginName Content"
        Maps\
          YourMapName.umap       <- your level, step 3.4
        Meshes\                  <- anything you import or create: your choice of folders
        Materials\
        Textures\

Rule: everything you add goes under Plugins\YourPluginName\Content. The kit's own Content folder is the game's assets: use them freely (every player has them), but don't add yours there.

3Quick start

  1. Open the kit

    Double-click project_jump.uproject. The first open takes a few minutes (shaders). Asked to rebuild modules? Say No: you have the wrong engine version.

  2. Make your plugin (once)

    Edit → Plugins → + Add (top left) → Content Only.

    • Plugin Name: letters and digits only, e.g. YourPluginName. It's permanent, and it has to be yours alone: the Workshop won't take a name another map already uses, so make it distinctive (GemSkyBounce, not Sky). Names the game itself uses (Game, Engine, a plugin the game has) are refused.
    • Author: you. Leave the rest.

    Click Create Plugin. No restart needed.

  3. Show it in the Content Browser

    Content Browser (Window → Content Browser) → Settings (top right) → tick Show Plugin Content. Right-click YourPluginName Content in the folder tree → New Folder → Maps.

  4. Make the level

    File → New Level → Basic (floor, light, sky) or Empty Level. Then File → Save Current Level As... into YourPluginName Content → Maps, named YourMapName. Don't reuse a shipped map's name (Aquatic, JumpLevel2, Tutorial, MainMenu).

  5. Add a Player Start

    Window → Place Actors, search "Player Start", drag it onto your floor and rotate it to face where players should look. No Player Start, no spawn.

  6. Build

    Add geometry, with box, convex or complex-as-simple collision on everything players jump on (section 4). Import and create assets with YourPluginName Content selected, so they land in your plugin folder.

    Fab and Megascans always import into the kit's Content instead. Leave them there: the package step moves them for you.

    How the automatic move works
    • When the package step finds assets your map uses in Content, it offers to move them. Close the editor and type Y: it moves them into your plugin, fixes every reference, and packages again.
    • Assets your map doesn't use are left alone.
    • Fab's shared master materials (Content\Fab\Materials, MaterialFunctions, MaterialParameterCollection, Textures) stay put: the kit and the game both have them.
    • To move without packaging: close the editor, double-click Tools\MoveIntoPlugin.cmd.
    • Every file it touches is backed up to Saved\MoveIntoPlugin-Backup\.
    • Why: in the game every map shares one Content path, so two maps with the same pack there would overwrite each other's copies.
  7. Play

    Press Play (▶). That's the real game: movement, HUD, saves, timer, RPG. M opens the pause menu (CONTROLS lists the binds), ~ the console, and Esc stops playing and returns to the editor. Save often (Ctrl+S).

  8. Package it

    Double-click Tools\PackageMod.cmd (section 7). Your map appears in the game's map list.

Before you publish

  • Player Start (step 3.5)
  • Box, convex or complex-as-simple collision on everything players jump on (4)
  • A Start and a Finish timer zone (5)
  • Map card with a thumbnail and a difficulty per route (5)
  • Packaged and played in the real game (7)
  • workshop.txt filled in, preview.png added (8)

4Building for the movement

In shortAnything players stand on, jump from or bounce off needs box, convex or complex-as-simple collision.

The movement uses classic jump-map physics. At load it turns box and convex collision into movement brushes, where bounces and elevators work as intended and lineups repeat. Meshes set to complex as simple are converted too: their flat parts become brushes and their smooth curves become curved-surface collision. Anything else falls back to engine collision, which plays worse.

Collision

Collision on the meshResult
✓ Box (any rotation: ramps, 45° sections), convex hullBrush. Clean; bounces and elevators work.
✓ Blocking VolumeBrush (each convex piece). Good for invisible walls and smoothed-out bounces.
✓ Per-triangle ("Use Complex Collision As Simple")Converted at load. Flat parts become brushes: bounces and elevators work. Smooth curves (slides, rounded ramps) and finely detailed models (most edges under 4 units) become curved-surface collision: smooth to slide and bounce on, no elevators.
~ Sphere, capsuleEngine collision for the whole mesh. Fine for props; no elevators.
✗ Geometry brushes (BSP)Engine collision. Players catch on edges and stick to walls.

A single sphere or capsule puts the whole mesh on engine collision, so keep curved shapes for props nobody jumps on.

Boxes or complex as simple? Both play right. Boxes are exact: the brush is the box you drew. Complex as simple saves you the boxes: the brushes are built from the mesh's own triangles, which matches what players see on solid meshes. Cube-grid and Modeling Mode meshes, which usually come with per-triangle collision, work as they are. Spline meshes (roads, rails) work too: the collision bends with the spline. If one converted surface still plays wrong, give that mesh boxes.

To see collision, turn on Show → Collision in the viewport. It draws the collision on every mesh.

To use complex as simple: double-click the mesh in the Content Browser, and in its Details panel set Collision Complexity to Use Complex Collision As Simple.

To give a mesh boxes instead:

  1. Double-click the mesh in the Content Browser to open it.
  2. Click Collision → Remove Collision.
  3. Click Collision → Add Box Simplified Collision, or a convex collision for angled shapes. If the shape isn't a single box (an L-shaped ledge, say), add several boxes to cover it.
  4. In the mesh's Details panel, make sure Collision Complexity isn't set to Use Complex Collision As Simple: with it, the boxes are ignored.

Built it from geometry brushes (BSP)? Select the brush, click Brush Settings → Create Static Mesh, then give the new mesh boxes or set it to complex as simple, as above.

Check what the movement made of your map (CmWorld log)

Play, open the Output Log and filter on CmWorld:

  • each converted mesh or volume with angled faces: its brush count and where it is;
  • each complex-as-simple mesh: its triangle count and whether it became brushes or triangle collision (curved-surface collision), then one line totalling them, with how many faces sat in smooth bends;
  • each skipped mesh, and why ("sphere/capsule collision", "not convex"). Skipped means engine collision;
  • one line counting the Blocking Volumes.

Sizes

1 game unit = 2.54 cmGame unitscm
Player, standing70178
Player, crouched50127
Player radius1538.1
Standing jump, height reached≈39≈99
Sprint jump on flat ground, no strafing≈180≈450

Don't set Kill Z

Leave Kill Z in World Settings at its default: a map that sets it removes the player with no respawn. Players save and load positions instead (V / F), so give them clear save spots and no soft-locks.

Ice

Tag a surface Slick to make it ice: no friction, players keep their speed and can't stop or turn sharply, and slopes slide them downhill faster. Jumping works as normal.

  1. Select the mesh (or Blocking Volume) in the level.
  2. In Details, search Tags and click + (Tags or Component Tags, either works).
  3. Type Slick, press Enter. Play and walk on it: you should slide.
  • The tag only changes the movement: give it an icy material so players can see it.
  • Duplicates (Ctrl+D, Alt+drag) keep the tag.
  • Tagging a placed Blueprint makes all of it icy. For one piece, open the Blueprint, select that mesh in Components and add Slick to its Component Tags.
  • Tag in the editor. Tags are read when the map loads, so a Blueprint adding one while playing won't reliably work.

Ladders

Place Actors → search "Ladder" → drag a Jumper Ladder in. It's an orange box, invisible in the game and solid only to players (shots and the camera pass through it).

  1. Put it flush against your ladder mesh, covering the side players climb on.
  2. Turn it so its thin side (Box Extent X) faces the way players come.
  3. Make it as tall as the ladder: Box Extent Z is half the height, in cm. The default is a 3 m ladder 60 cm wide.
  • Players climb by walking into it while facing it. Looking up or down while holding forward climbs faster.
  • Strafing slides them along it and off the side. Jumping pushes them off, and they can't grab it again until they land.
  • The weapon goes away while climbing and comes back up after.
  • A mesh tagged Ladder (like Slick for ice) climbs the same, so the mesh's own collision can be the ladder.

Ledges to climb (mantles)

Players can climb onto a ledge, or vault over a low wall, by jumping while they face it. That only works where you put a Jumper Mantle (Place Actors → search "Mantle"): a box with no collision of its own that marks the ledge.

  1. Put it against the wall, just under the ledge, covering the part of the wall players climb from.
  2. Keep it thin (the default is 4 cm), and turn it so its thin side faces the players. A player standing inside it can't mantle.
  3. Set Kind. On: they climb up onto the ledge. Over: they vault over it and drop down the far side.
  • To mantle from standing, the ledge's top has to be 18 to 60 units above the floor (46 to 152 cm). A higher ledge can only be mantled mid-jump, once the player's feet are within 60 units of its top. The ledge also needs room for a crouched player on it. Without standing room, players climb up crouched.
  • An Over wall needs a clear 31 units (79 cm) beyond its top and an 18-unit (46 cm) drop on the far side. Without that, players climb onto the wall instead.
  • Players have to be standing (not crouched) right in front of the box, facing it within 60°. When they can mantle, the HUD shows PRESS SPACE TO MANTLE (with their own jump key), so Play and walk up to it to check.

Performance

Frame rate never changes the physics (it runs at a fixed rate), but players want high FPS. stat fps in the console shows your cost. The game uses Lumen; big landscapes with foliage are where frames go.

Map size doesn't cost frames in the movement: it only checks the collision near the player, so tens of thousands of brushes are fine. Converting complex-as-simple meshes adds a second or two to loading on a big map.

5Timer zones, teleporters and the map card

In shortOne Start zone, one Finish zone, and a _Info asset for the menu card.

Timer zones

Timed runs come from TimerZone actors: Place Actors → search "Timer Zone". Set these in Details:

  • Zone Type = Start (green). The clock starts when the player leaves it, so cover the whole spawn platform.
  • Zone Type = Finish (red). The clock stops when the player enters it, so make it generous.
  • Box Extent: half-size, in cm.
  • Route (Finish only): leave main for one finish. More finishes = more routes, each with its own leaderboard, all from the same Start. Name them what players say: easy, hard, rocketless.

Ignore TutorialZone: it's for the game's tutorial.

Leaderboard limits, and how the zones look
  • Online leaderboards: one per finish route, up to 32 per map. Route names: letters, numbers, spaces, - and _, up to 32 characters. Extra routes or other characters still count locally.
  • Every finish counts on the local leaderboard (top in the console).
  • A Workshop item with more than one map gives each map its own leaderboards. Adding a map to an item that had only one starts the first map's online leaderboards over, so decide at the start.
  • Wireframes of the Start/Finish boxes show in the editor and the game. You can customize the look of them by adjusting Line Thickness, the colours and Draw Through Walls.

Teleporters

No Blueprint needed. Place Actors → search "Teleport":

  • Teleport Sender: a box. Entering it teleports the player. It's purple in the editor and invisible in the game.
  • Teleport Receiver: where they land. Put it on the floor like a Player Start and turn it: players look along its arrow.
  • Teleport ID pairs them: a sender goes to the receiver with the same ID (easy → easy). Any number of senders can share one receiver, like every finish sending back to spawn. Each receiver needs its own ID.
Arrival SpeedStop: arrive standing still. Keep: keep the velocity. Redirect: keep the speed, heading along the receiver's arrow.
Set ViewTurn the player to the receiver's arrow. Off keeps their own view.
Restart RunWhat pressing restart does, on the way: the run and the save are cleared. Tick it on a finish that sends players back to spawn. Without it, a player holding a save who lands in the Start zone goes back to their save, as walking in would.

In the editor each sender draws an arrow to its receiver, and both show their ID. Red text means a sender with no receiver, or two receivers with the same ID.

The map card

In-game, the menu shows each map as a card: picture, name, gamemode, difficulty. The loading screen shows the same picture, title, author and routes while your map loads, and the pause menu's STATUS page shows the picture and lists every route with its number and leaderboard. Without one, yours gets a coloured placeholder and no difficulty or gamemode.

  1. In the Content Browser, open the folder your level is in (YourPluginName Content → Maps). Right-click → Data Asset → JumperMapInfo.
  2. Name it exactly your level's name plus _Info: YourMapName_Info. The game only finds it with that name, next to the level.
  3. Open it and fill in:
TitleA custom map name. Empty = the level's name, as saved in the editor.
AuthorYou.
GamemodeCJ. (BHOP, SURF and KZ are for later.)
Is TutorialShows TUTORIAL instead of a difficulty.
ThumbnailSquare picture: screenshot while playing (F9), crop square (1024×1024 is plenty), import the PNG next to the level.
RoutesOne entry per finish route: its Route name (main if just one) and a Number 1–10. The card shows your easiest route to your hardest (routes rated 1 and 5 read "1–5"), and a map with more routes gets an "N ROUTES" badge on its picture.
Radio OffThe game's radio stays quiet on your map. Tick it if the map has its own music or voicelines. The player's song carries on when they leave.

Rating a route

Rate who can finish it, and how long it takes them, not which tricks it uses.

EASY 1–3a brand-new player
MEDIUM 4–5a regular jumper
HARD 6–8only experienced jumpers
INSANE 9–10only the best players

Rate each route as meant to be played; skips don't count. If nobody finishes your "3", change it. Unsure? Ask in #mapping. 0 = not rated yet. What each number means

6Blueprints

Blueprints in your plugin run in the game: moving platforms, doors, buttons, launch pads, teleporters, low gravity, timed sequences, sky and weather, on-screen text. Normal nodes work on all your own actors, meshes, lights, sounds, effects and widgets.

The player is the exception. Normal nodes can read it (position, speed, view) but not change it. Use the Map Scripting nodes, and check Is Local Player first.

Moving the player

  1. In the Event Graph, right-click and type Map Scripting to list them (or a node's name, like Launch Player).
  2. Plug the player into the Player pin. In a trigger, that's the overlap's Other Actor.
  3. Put a Branch on Is Local Player in front. In multiplayer every player's game runs your triggers; this makes each player move only themselves.
// a launch pad
On Component Begin Overlap (Box)
  -> Branch (Condition: Is Local Player, Actor = Other Actor)
     True -> Launch Player (Player = Other Actor,
                            Launch Velocity = 0, 0, 800,
                            Replace Vertical = ticked)
  • Teleporter: the same with Teleport Player With View, using a Target Point's Get Actor Location and Get Actor Rotation.
  • Low gravity: Begin Overlap → Set Player Gravity Scale 0.5; End Overlap → Reset Player Movement Scales.
All Map Scripting nodes
Get Local PlayerThe player on this computer.
Is Player / Is Local PlayerIs this actor a player / the player on this computer.
Launch PlayerPushes the player: adds to their speed, or replaces the up-down and/or sideways part.
Set / Add / Get Player VelocitySpeed and direction, in the speedometer's units.
Teleport PlayerMoves the player. Aim a little above the floor; if the target is inside something, the player is nudged clear.
Teleport Player With ViewThe same, and turns them to face a direction.
Set / Get Player ViewWhere the player is looking.
Get Player Speed, Is Player On Ground / Crouched / SprintingReads the movement.
Set Player Gravity / Speed / Jump Height Scale1 = normal, 0.5 = half, 2 = double. Jump height 0 = no jumping. Every map starts at 1.
Reset Player Movement ScalesAll three back to 1.
Is Run In Progress, Get Run Time, Is Player PracticingReads the run timer and practice mode.
Hold RadioQuiets the game's radio while your map plays something of its own (a song, a voiceline): true pauses it, false lets it carry on. Works from Event BeginPlay; leaving the map lets go too. To keep it off for the whole map, tick Radio Off in the _Info instead.
Is Radio PlayingMusic is coming out of the radio right now.
Restarts, saves, and Unreal's own nodes
  • Restarting, or walking back into the start box, resets the scales to 1 and re-fires the triggers the player is standing in (End Overlap, then Begin Overlap), so a zone around the start keeps working. Loading a save doesn't change the scales.
  • A restart doesn't reset the rest of your map: an opened door stays open.
  • Unreal's Set Actor Location, Teleport, Launch Character and Set Control Rotation also work on the player.
  • Nothing moves a player who is spectating, watching a replay or flying in practice.

Videos on a screen

A TV, a projector screen or a billboard can play a video, with its sound, through the Map Video component:

  1. Copy the video into Plugins\YourPluginName\Movies\ with Windows File Explorer, not the editor: make the Movies folder yourself, next to Content\ (not inside it). Don't import the video or drag it into the Content Browser; that makes an asset the game doesn't use. The editor doesn't show the Movies folder, and that's fine. The video: an .mp4, at most 1920×1080 and 200 MB, named with letters, digits, spaces and _ - . only.
  2. Give the screen a material with a Texture Parameter named Video (any default texture; black is good) going into Emissive Color.
  3. Add a Map Video component as a child of the screen's mesh (on the placed actor or in a Blueprint) and pick the file in Video File.
  4. Press Play. It starts with the map and loops (Play On Start, Loop). The sound comes from the screen and fades with distance (the Sound settings).
Nodes and notes
  • Nodes: Play, Pause, Stop (back to the start), Set Video (another file from your Movies folder: a channel change), Set Looping, Set Volume, Is Playing, Show On Mesh (the same video on another mesh of the same actor).
  • Each player's game plays it on its own: not in sync between players. Up to 4 videos open at once per map.
  • PackageMod.cmd packs your Movies folder with the map and checks every video; the Workshop upload takes them along.
  • Nothing shows? The log's LogMapVideo lines say why. Videos only run while playing, not while editing.

What maps can't do

The game won't load a map whose Blueprints try to:

  • reach outside the game: files, websites, programs, downloads, video files (except your own, through Map Video), the microphone;
  • take over the game: quit, load another level, kick or rename players, pause, slow time (a Level Sequence with a Time Dilation track too), save games;
  • change player settings: language, controls, graphics, sound, mouse cursor, window;
  • find out who's playing: names, Steam IDs;
  • change the game: the player (except via Map Scripting), game mode, HUD, leaderboards, or timer zones while playing. A map can't bring its own player or game mode.
Allowed, but limited
  • Normal nodes done to the player (Destroy Actor, Set Actor Hidden In Game, Set Life Span...) are skipped. Camera shakes and fades work.
  • Execute Console Command sets how your map looks: lighting, shadows, Lumen, sky, fog, clouds, water, translucency, post-processing, foliage and grass, to a number. Sky and weather packs (Ultra Dynamic Sky and others) work as in the editor. Sound and effects switches, and debug or file settings, are ignored. The player's GRAPHICS settings come first: the lighting method (Lumen or not), reflections, shadow type, texture filtering, upscaling, anti-aliasing, motion blur and quality presets are always theirs, and so are ambient occlusion, volumetric fog, bloom, lens flares, depth of field and chromatic aberration once they've changed them. A post-process volume can't turn Lumen back on for a player who turned it off. Everything resets when your map ends.
  • Load Asset works for your content and the game's.
  • Blueprints can react to keys, but the game's controls come first. In the game, Esc always opens the menu.
  • "Run on Server" events do nothing; "Multicast" and "Run on Owning Client" work.
  • MetaSound's Wave Writer doesn't work in the game.
  • A map can use its own content and the game's, not another map's.

The package step runs the same check:

MODCHECK BLOCKEDNames the Blueprint and the node that isn't allowed, or a packaged file the game would refuse. Remove it and package again (Troubleshooting).
MODCHECK noteAllowed, but does nothing in the game (usually something done to the player without Map Scripting).
MODCHECK editorAn editor-only tool. Nothing to do.

Need a blocked thing for a good reason? Ask in #mapping.

Asset packs (Ultra Dynamic Sky etc.)

Fab packs work: import and package as usual. The sky, weather, clouds, sounds and effects go with your map; the pack's editor tools (setup windows, readme, toolbar buttons) stay in the kit and show as editor tools in the check. Packs with C++ code can't be used.

7Package it

In shortDouble-click Tools\PackageMod.cmd and type your plugin's name (YourPluginName). That's all.

It checks your Blueprints (section 6), offers to move assets out of the kit's Content (step 3.6), packages into Saved\Mods\YourPluginName\ and installs into the game. Launch the game from Steam: your map is in PLAY with a CUSTOM tag.

  • The first run is slow (shaders); later ones are quick.
  • Use the editor's Play while building. Package to test a change in the real game.
  • Packaged maps don't load in the editor. It can't mount packages, so it lists neither your packaged map nor any Workshop map.

A second map

Make a new plugin (Plugins\SecondMap, step 3.2), build there, and package it as SecondMap. It gets its own Workshop item, page, picture and rating. Two levels in one plugin share one Workshop item: fine for a map pack, not for unrelated maps.

8Steam Workshop

In shortFill in workshop.txt, package again, publish from the game's WORKSHOP → UPLOAD tab.

1. Write the page

Your first package creates a Workshop folder:

Plugins\YourPluginName\Workshop\
  workshop.txt     the page: title, tags, visibility, description
  preview.png      Workshop list thumbnail (you add it; under 1 MB, 16:9 looks best)
  Screenshots\     the gallery (you add them; .png or .jpg)
// workshop.txt
title: Sky Bounce
tags: bounce, hard
visibility: public
description:
Twelve bounces over a canyon. Two routes: the main one, and a rocketless
one for people who hate themselves.
  • visibility: public, friends, unlisted (link only) or private (only you). Use private for a first test.
  • description: everything after that line. Steam formatting works: [b]bold[/b], [i]italic[/i], [url=https://...]a link[/url], [list][*]...[/list].

Then package again so the game sees it.

2. Publish

  1. Launch the game from Steam → WORKSHOP → UPLOAD.
  2. Pick your map on the left. The right side previews the page and lists anything blocking it.
  3. Press PUBLISH TO WORKSHOP. When it's done, OPEN WORKSHOP PAGE. If Steam asks you to accept the Workshop agreement, do it, or the item stays hidden.

Updating

Change the map, package, WORKSHOP → UPLOAD, pick it, write what changed (it becomes the change notes), PUBLISH UPDATE.

  • Reset the leaderboards: tick it when the course changes (jumps, bounces, shortcuts). Everyone's times start over and old runs are hidden. Leave it off for looks and lighting. Can't be undone.
  • Also update the title, description... resends workshop.txt. Leave it off if you edit the page on Steam.
  • Screenshots only upload on the first publish; after that, manage them on Steam.
  • Don't delete workshop.json (in %LOCALAPPDATA%\project_jump\Mods\YourPluginName\): it links the map to its item. Without it, the next publish makes a second item. The exception is an item that no longer exists (Troubleshooting).

Playing Workshop maps

Subscribe on the map's Workshop page (WORKSHOP → DOWNLOAD → BROWSE THE WORKSHOP). It appears in PLAY within seconds, tagged WORKSHOP. The DOWNLOAD tab lists your subscriptions, their download state, and lets you unsubscribe.

Without the Workshop

Zip Saved\Mods\YourPluginName\ from the kit and send it. It goes in %LOCALAPPDATA%\project_jump\Mods\.

9Multiplayer

  • Host a custom map like any other, or call a map vote for it.
  • Workshop maps download automatically for players who lack them: when they click a [WORKSHOP] lobby (then they join), or as soon as a map vote starts. They stay subscribed afterwards.
  • Non-Workshop maps can't be downloaded. The lobby says "you don't have it"; send those players the zip.
  • Each player's game runs your Blueprints on its own. Doors and moving platforms aren't in sync between players, and a launch pad only launches whoever stepped on it.
  • Multiplayer is off in the kit (its console could bring cheat settings into a lobby). Use the Steam game. Runs finished in the kit go to a separate local board (Leaderboard.kit.json) and never count.

10When the game updates

Updates that change shipped content come with a new kit (a new Releases\<version> folder). Run PackageMod.cmd again from it; your map itself doesn't change. Maps packaged for an old release may reference things the new game no longer has.

11Troubleshooting

Opening the kit

Asks to rebuild modules / "missing modules"
Wrong engine version. The kit needs 5.8.x.
My plugin folder isn't in the Content Browser
Settings → Show Plugin Content (step 3.3).

Playing in the editor

The player falls through my floor
The mesh has no simple collision and isn't set to complex as simple. Add a box, or set Collision Complexity to Use Complex Collision As Simple (section 4).
The player sticks to a flat wall and slides along it
The wall is on engine collision (a geometry brush, or a sphere/capsule somewhere on the mesh). See the collision table; the CmWorld log names the culprits.
Elevators or bounces feel wrong on one platform
Its collision isn't a brush: a sphere/capsule somewhere on the mesh, or a complex-as-simple mesh that became curved-surface collision (curves and detailed models have no elevators). Check its CmWorld line, and give it boxes for exact brushes.
My packaged map or a Workshop map isn't in the editor
Expected: packaged maps only load in the game (section 7).

Packaging

"uses N asset(s) from the kit's Content folder"
Close the editor and type Y when it offers to move them, or run Tools\MoveIntoPlugin.cmd (step 3.6).
"Close the Unreal editor first"
The move edits your files. Save, close the editor, run it again.
Something looks wrong after a move
Originals are in Saved\MoveIntoPlugin-Backup\<map>-<date>\, in their folder layout. Close the editor and copy them back over Plugins\ and Content\.
MODCHECK lines, or "MOD BLOCKED" in the game
A Blueprint uses something maps can't; the line names it. Remove that node (section 6).
"MODCHECK BLOCKED … holds …: a map's files go in its own folder"
Your map uses an engine asset the game doesn't have, and the cook packed it in with your map, outside your plugin. The game would refuse the whole map, so nothing was installed. In the Content Browser, Settings → Show Engine Content; find the asset (the path after Engine/Content/), right-click → Reference Viewer to see what uses it, and point that at something in your plugin or the game's. Package again.
"Expected exactly one .uplugin"
Your plugin folder must contain exactly one .uplugin file: your plugin's own.
The package script can't find the engine
Pass it explicitly: -Engine "C:\Program Files\Epic Games\UE_5.8".

In the game

My map isn't listed
Restart the game first: it looks for installed maps when it starts. Still missing? Open the game's log: in Steam, right-click PROJECT_JUMP → Manage → Browse local files, then project_jump\Saved\Logs\project_jump.log. Search it for your map's name. "no .pak files": the cook produced nothing. "no maps.json": the installed map is incomplete. Either way, run PackageMod.cmd again. "refused — … a map's files go in its own folder": a file was packed outside your plugin (see Packaging, above).
My launch pad or teleporter does nothing
Use Map Scripting nodes (or Set Actor Location / Launch Character) behind an Is Local Player check. Other nodes done to the player are skipped and show as MODCHECK note.
A Teleport Sender does nothing
Its label is red: no receiver has that Teleport ID (IDs must match exactly). Or the player was already inside the box: senders fire on the way in, so walk out and back in. Nothing teleports while flying in practice.

Steam Workshop

"Steam refused"
Run the game through Steam, logged in to the account that owns it. If it names an agreement, accept it on the item's page.
"Steam couldn't read the map files or an image [EResult 9]"
Usually the map is still linked to a Workshop item that no longer exists (you deleted it on Steam, or a first publish stopped halfway). Delete workshop.json from %LOCALAPPDATA%\project_jump\Mods\YourPluginName\ and from the kit's Saved\Mods\YourPluginName\, then publish again: it makes a new item. Only do this when the old item is really gone, or you'll end up with two copies of your map.
"The plugin name is already used by another map"
Someone published a map with that name first, and two maps can't share one. Switch to a new name before your first publish: make a new Content Only plugin (step 3.2); in the Content Browser drag your folders from the old plugin onto the new one → Move Here; right-click the old plugin's folder → Fix Up Redirectors; copy its Workshop folder across. Close the editor, delete the old plugin's folder from Plugins\, then package and publish the new one.
My map isn't on the WORKSHOP page, or says NEEDS ATTENTION
Package again, then press REFRESH. The page lists what's missing (usually the description in workshop.txt).
A subscribed map doesn't show up
Steam may still be downloading: wait a minute or restart the game. Still missing? It was published for an older game version; the mapper needs to re-package from the current kit and publish again.