Give each colonist a personal work order
RimWorld is a sci-fi colony simulation driven by an AI storyteller. Sable Arch is a separate fictional colony game. Its colonists, tasks and scheduling rules are original examples, not claims about RimWorld's priority system or simulation.

Let each colonist rank tasks from 1 to 4, with 1 highest. When a colonist is idle, consider only open tasks in their allowed work types. Choose the lowest rank first; if ranks tie, choose the colonist's higher skill, then the shorter travel distance, then the task ID alphabetically. A colonist takes one job at a time, and a task can be claimed by only one colonist.
Resolve choices with a stable sort order
Store each colonist's allowed tasks, rank and skill separately from the colony task queue. Sort eligible colonist-task pairs by rank ascending, skill descending, distance ascending and task ID. Reserve a task as soon as a colonist accepts it, then move to the next idle colonist. This prevents two residents from starting the same job.

In the test, Ava ranks cooking 1 and repair 3, so she chooses cooking despite higher repair skill. Bo ranks repair 1 and cooking 2, so he takes repair. A tie in rank uses skill, then distance; identical cases use alphabetical task ID. Once a task is claimed, the next colonist receives another open task. These checks validate assignment order, not colony balance.
Let players change priorities without losing work
Show each colonist's ranks, allowed tasks, current job and skill beside the queue. Changing a rank affects the next scheduling pass; it should not cancel a job already in progress unless the player explicitly interrupts it. Keep unavailable tasks visible with a short reason such as blocked, reserved or missing materials.

Test task assignment before adding emergencies
Keep task selection as a deterministic function of colonist data and open jobs. Godot Resource can store original colonist and work definitions; SEELE AI Game Maker is a starting point for a prototype. RimWorld provides broad colony-simulation context only and does not validate Sable Arch's fictional scheduling values.
Build an original colony scheduler. Each colonist ranks allowed work from 1 to 4. Choose the lowest rank, then higher skill, shorter distance and alphabetical task ID. One colonist can hold one job, and one task can be claimed only once. Changing priorities applies on the next scheduling pass and does not interrupt active work automatically.
Create an original colony sim in SEELE · RimWorld on Steam
Frequently asked questions
How should a colony game choose a colonist's next task?
Filter for open tasks the colonist is allowed to do, then apply a visible ordering rule. Sable Arch uses personal rank first, followed by skill, distance and a stable task ID. Showing these fields helps players understand why a resident selected one job over another.
What prevents two colonists from taking the same task?
Reserve the task as soon as the first colonist accepts it, then remove it from the open queue before scheduling the next resident. Keep one current job per colonist as well. These two limits prevent duplicate work and make the queue state easier to inspect.
Should changing a work priority cancel an active task?
In this example, a rank change affects the next scheduling pass and leaves current work alone. If a player wants to interrupt a job, provide a separate explicit action. This keeps a routine priority edit from unexpectedly discarding progress or moving resources.


