Connect Floating Islands With a Player-Built Transport Network

Prototype anchor placement, route reachability and cargo limits across open sky.

Seele Editorial TeamUpdated November 18, 2026

Make the gap a route-building problem

In fictional Sky Thread, three floating islands hold a workshop, a storehouse and a beacon. The player has two bridge-span tokens and must move a light crate from island A through B to C. Each span supports a combined load of 2. A second crate weighs 2, so carrying both together weighs 3 and exceeds the rating. The network makes cargo order matter before the bridge starts swinging.

Three floating islands sit across open sky with a small crate waiting on the first island.
Sky Thread is a fictional transport-sandbox concept, not a screenshot of a tested game.

Let the player place two hinged spans between anchor points, then preview which islands connect. The route graph should show that A reaches C through B, while a broken anchor leaves C isolated. A light crate can cross either span alone; the two-crate load must be split into separate trips. The player sees the cost of using limited spans and the benefit of keeping a stable middle hub.

Store each span as a pair of island anchors, a load rating and a placed state. A route exists only when the placed links form a connected path from source to destination. Sum cargo weight along a trip and reject a span when the total exceeds its rating. Keep this abstract validator separate from the later physics scene, where flexible bridge motion, crate sway and collisions need real hands-on tuning.

A modular suspended bridge with visible hinge anchors connects two neighboring floating islands.
The fictional jointed span connects at two anchors; the capacity rule is checked separately from its motion.

The deterministic check connects A–B and B–C with two rating-2 spans. It confirms that a weight-1 crate reaches C through B. Adding a weight-2 crate to the same trip produces load 3 and is rejected. Removing either link also breaks reachability. This verifies the small network rule only. It does not simulate forces, bridge stability, falling cargo, camera movement or player control.

Deliver in two trips, then add the swinging bridge

Make the first objective readable: carry the light crate to C, return for the heavier crate, and deliver it separately. Show span usage, cargo weight and why an overloaded route is blocked. Once that planning loop works, make the bridge span a physics object. Godot PinJoint2D attaches two 2D physics bodies at a point and lets them rotate; RigidBody2D is moved by a physics simulation. Those engine features are implementation options, not proof that this fictional bridge is stable.

A small cargo crate crosses two connected bridge spans through the central floating island.
Concept outcome: the lighter crate reaches the destination over a two-link route.

Prompt for a network before adding physics effects

Start with three islands, two span tokens, anchor sockets and crates with visible weights. Add a route preview and an overload warning. Give each trip a simple begin, carry and arrive state so the test can compare planned and actual network data. Then prototype one hinged span at a time and test its load, settling and collision behavior in the playable scene rather than inferring them from the graph check.

SEELE AI Game Maker offers a prompt-based entry point for building a game concept. Use it to start a fictional sandbox, then inspect each bridge and cargo interaction in your own build. Keep the article's graph test labelled as local design evidence. Do not present generated concept art or a route table as a physics playtest.

Create an original floating-island transport sandbox with three islands, two hinged bridge spans rated for load 2, and crates weighing 1 and 2. Preview routes before a trip. Reject combined load 3, and allow the weight-1 crate to cross A–B–C. Removing a span must disconnect the route. Label the bridge motion as prototype physics requiring separate testing.

Start a fictional sandbox prototype in SEELE · Godot PinJoint2D documentation

Frequently asked questions

Why validate the route before simulating the bridge?

A graph check catches missing anchors and overloaded trips with a small, repeatable test. It helps distinguish a planning error from a physics problem. It cannot tell you whether a hinged span will sag safely or whether cargo will bounce off. Keep the abstract route rules and the playable physics checks as separate evidence.

How should cargo weight affect the network?

Give every span a visible rating and every crate a weight. Sum the load for the current trip, then reject it if any link on the route would be overloaded. In this example, one light crate weighs 1 and fits a rating-2 span; adding a weight-2 crate makes 3 and requires a separate trip.

What should I test when the bridge swings?

In the playable scene, try the heaviest permitted load, a crate near each edge, a settling bridge and a failed delivery. Check for falling cargo, unintended rotation and repeatable resets. The local route test does not cover these behaviors, so report physical results only after running the actual prototype.

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating