Movement envelope
Record how far and how high the player can jump under the intended controls. Use those limits to size gaps and ledges. Do not design a difficult jump before the character’s movement has settled.
Plan a platform game by defining jump reach, air control, landing feedback and checkpoint spacing. Build levels from movement the player can understand and repeat.
This page is a planning guide. Elseland Game Maker is not publicly available yet. You can browse games on the website or play in the mobile app.
Make these decisions before choosing a tool or expanding the project.
Record how far and how high the player can jump under the intended controls. Use those limits to size gaps and ledges. Do not design a difficult jump before the character’s movement has settled.
Decide how the controller handles a jump pressed slightly before landing or just after leaving an edge. Make the chosen behavior consistent so players can learn it instead of guessing.
Show the next landing area before the player commits. A jump should test movement skill, not knowledge of terrain outside the camera view.
Set the time and distance between failure and another attempt. A short challenge can feel much harsher if every missed jump repeats a long approach.
Use the sequence below to keep the first version small enough to inspect.
Include a low ceiling, a narrow platform, a long gap and a moving surface. Check the character on each before tuning a complete level.
Introduce a hazard where its consequence is clear. Follow with a slightly harder use of the same movement, then combine it with an already understood obstacle.
Observe where a player pauses, overshoots or jumps without seeing the destination. Change one movement or layout variable at a time so the effect is understandable.
An original planning example, not a claim that Elseland has generated this result.
Use one fixed jump height and left/right movement. Begin with a safe roof, then introduce three gaps of increasing width with visible landing ledges. Place a checkpoint before the final gap. The acceptance target is that a tester can explain why a missed jump failed and attempt it again without repeating the whole route.
A concrete check is more useful than another variation of the same prompt.
Repeat the same jump from the same starting position. If the result changes unexpectedly, investigate control timing or moving surfaces before blaming the level.
Pause at each takeoff point. The next safe surface and the main hazard should already be visible.
Measure the actions needed after a failure. Remove unnecessary travel that adds waiting without testing a new skill.
Answers about scope, handoff and the limits of this workflow.
Tune a simple movement test room first. Attractive art cannot compensate for jumps that land unpredictably or require unseen information.
No. Smaller gaps create space to learn and recover. Reserve demanding jumps for places where the player has enough information and an appropriate retry point.
Navigation through surfaces and gaps is a central challenge. Combat can be present, but movement geometry and timing still determine how the level plays.
Elseland Game Maker is not publicly available yet. This page helps you prepare a brief and evaluate a workflow. The current website offers games to browse and play; the mobile app is a separate destination.
No. They are written examples and acceptance checks. Producing a working game or asset requires a suitable tool, implementation and testing.
Explore the Elseland homepage and choose a game to play.
Play Games Now