Orbled StudiosCorrespondence ↗

RESPONSIBILITIES, NOT RÉSUMÉS

Assembly Office

Orbled Studios examines what happens between an industrial plan and the next object that must move. Our game concepts begin with concrete arrangements rather than a list of production bonuses. A sketch might show a cradle, a transport spine and three waiting containers. The useful question is whether a person can explain which movement is possible next and why another must wait. If that relationship is unclear, adding more machines will not solve it.

DESK 1

On the planning table

The systems-design role describes the rules for occupation, transfer and release. It identifies which conditions a task needs and what changes when the task finishes. The level-design role puts those relationships into spaces where more than one response is possible. These are responsibilities within the design process, not biographies of named employees. We do not claim a particular headcount or a history of commercial releases.

DESK 2

At the drawing station

Visual development establishes the difference between structure, machinery and handling equipment. A module should not look accessible on the screen when its service face is actually blocked. We use clear silhouettes and restrained overlays to connect appearance to proposed behaviour. The concept art provides a world to imagine, while diagrams expose relationships that a dramatic image can easily conceal. Both forms are labelled according to what they represent.

DESK 3

Beside the interface model

Interaction design follows a waiting task from its label to the condition that prevents progress. The interface should help a player trace that dependency without opening a separate report for every object. We compare focused explanations with whole-yard views, asking what each one makes easier to understand. A dense display is not automatically a useful display. Details belong where they support a decision.

DESK 4

In the revision record

The Assembly Record separates proposed rules from evidence. A note may explain why a mechanic is worth investigating without claiming that it has passed a playtest. When discussing an alternative, we describe the trade-off that makes it interesting. This keeps the development writing useful even while the concepts remain unsettled.

DESK 5

Bring a specific obstruction

The most useful feedback names a page and a relationship that remains unclear. Perhaps a container appears able to pass through an occupied zone, or a diagram does not explain when a reservation ends. Use Yard Correspondence to describe that case in words. We can review focused observations more readily than broad requests to make every system more realistic. Please avoid sending confidential material or personal documents.