Ever previewed your platformer and watched the camera drift past your background into grey nothingness? That’s the fastest way to make a finished game look like a prototype. GDevelop makes fixing this surprisingly painless — two steps, no code, no math.
This guide covers the exact setup: a smooth-follow camera behavior plus boundary enforcement tied to your background’s bounding box.
What You’re Building
A camera that:
Follows your player with a slight interpolated delay (no jerky snapping)
Stops hard at the edges of your background image (no void)
Adapts automatically if you resize or reposition your level
Step 1: Add the Smooth Platformer Camera Behavior
Stop using the basic “Center camera on object” action. It works for prototypes but the instant snapping looks cheap. GDevelop has a dedicated behavior that handles interpolation for you.
Setup:
Double-click your player character in the object list to open its properties.
Go to the Behaviors tab.
Click Add a behavior to the object.
Search for “camera” and select Smooth Platformer Camera.
When you apply it, GDevelop actually installs two components: Smooth Camera and Smooth Platformer Camera. Together they give the camera a weighted delay that smooths out jumps, falls, and direction changes.
Preview your game now — the camera follows nicely, but it’ll sail right past the edges of your background. That’s what Step 2 fixes.
Step 2: Enforce Camera Boundaries in the Event Sheet
Boundaries aren’t a behavior — they’re an action you add to your event sheet. The key move is linking the boundary values to your background object’s bounding box instead of hard-coding pixel coordinates.
Event Sheet Setup:
Add a new action (no condition needed — this runs every frame).
Search for Enforce camera boundary.
Fill the four fields using the Object Selection tool:
Field Expression Path Object
Left Object Position → Bounding Box → Left Position Your background object
Top Object Position → Bounding Box → Top Position Your background object
Right Object Position → Bounding Box → Right Position Your background object
Bottom Object Position → Bounding Box → Bottom Position Your background object
Using bounding box expressions instead of raw numbers means the boundaries update automatically if you scale or move your background in the editor. No maintenance.
Common Mistake: Wrong Boundary Object
If your scene has multiple layers (parallax clouds, decorative props, mid-ground platforms), make sure you’re selecting the primary background object that defines the playable area. Binding the camera to a small cloud sprite or a decorative prop will cause jittering or a stuck camera because the boundaries are too small. Double-check your object names in the event sheet.
Why This Matters
Smooth Camera behavior handles interpolation math — no manual lerping.
BoundingBox expressions adapt to level changes — no hard-coded coordinates to maintain.
Layer awareness — apply boundaries to the layer your gameplay lives on (usually Base Layer), not your UI layer.
No void — players never see outside your level, which is one of the cheapest ways to make a game feel finished.
Two steps. No plugins, no extensions, no subscriptions. Your camera now glides with the player and stops exactly where your world ends.
Top comments (0)