levels

Level Data in FlatRedBall2

Levels are defined as TMX files using the Tiled map format. Use the tmx skill to create or edit TMX files.

Level Setup in a Screen

Load a TMX file with TileMap, add it to the screen, and generate collision:

using FlatRedBall2.Tiled;

public class GameScreen : Screen
{
    private TileShapes _solidCollision = null!;

    public override void CustomInitialize()
    {
        var map = new TileMap("Content/Tiled/Level1.tmx", Engine.GraphicsDevice);
        map.CenterOn(0, 0); // center map on world origin
        Add(map);

        _solidCollision = map.GenerateCollisionFromClass("SolidCollision");
        Add(_solidCollision);
    }
}

Key types (all in FlatRedBall2.Tiled):

• TileMap — loads a TMX file, wraps layers, generates collision
• TileMapLayer — per-layer Z, visibility, and render layer control
• TileShapes — collision grid (FlatRedBall2.Collision)

TileMap Position

TileMap.X and TileMap.Y define the top-left corner of the map (Tiled convention). Default (0, 0) places the top-left at the world origin; the map extends right (+X) and down (−Y).

CenterOn(worldX, worldY) repositions the map so its center is at the given point.

Layer Z-Order

Layers are assigned Z values automatically: 1 apart in TMX order, with GameplayLayer at Z = 0 if it exists. Entities at Z = 0 naturally interleave at the gameplay layer. Override per-layer Z only when needed:

map.GetLayer("Foreground").Z = 100f;

Multiple Collision Types

var solid = map.GenerateCollisionFromClass("SolidCollision");
var jumpThrough = map.GenerateCollisionFromClass("JumpThroughCollision");
Add(solid);
Add(jumpThrough);

Each collection can have its own collision relationship. For jump-through platforms, set OneWayDirection = OneWayDirection.Up and CanDropThrough = true on the relationship — the player passes through from below, lands from above, and can drop down with Down+Jump. For hard one-way barriers (OneWayCollision tile class — Yoshi-style ratchet doors), set OneWayDirection = OneWayDirection.Up and leave CanDropThrough = false. See the collision-relationships skill for details. By default all tile layers and object layers are scanned — hand-drawn rectangle/polygon <object>s with a matching Class are collision sources too, not just painted tiles (see "Collision from hand-drawn object-layer shapes" below). Passing layerName restricts the scan to a single tile layer, skipping object layers entirely: