Out of Office Son Mesai

Built like a product, not like a game jam.

Every folder is its own assembly and dependencies only flow one way. Systems never know about each other; they talk through a typed signal bus. Adding a character, an obstacle or a power-up takes no code.

[CreateAssetMenu(menuName = "Out of Office/Effects/Magnet")]
public sealed class MagnetEffect : EffectDefinition
{
    [Min(0f)] public float radius = 7f;

    public override void Apply(EffectContext context)
    {
        context.Player.MagnetRadius = radius;
    }

    public override void Remove(EffectContext context)
    {
        context.Player.MagnetRadius = 0f;
    }
}

Rules

• 01

  Systems don't know each other

  49 typed signals, all readonly structs. The UI sends requests, gameplay decides and announces the result as an event.

• 02

  One owner for game state

  Only GameFlow changes the state (StateMachine<GameState>). Invalid requests are quietly ignored.

• 03

  Content is data

  Professions, obstacles, power-ups, accessories, worlds and store items are ScriptableObjects. New content means a new asset.

• 04

  New behaviour, one new class

  Every effect derives from EffectDefinition, every movement from MovementPattern. Existing code stays untouched (open/closed).

• 05

  No allocations during a run

  Obstacles, coins, road and effects come from pools. No LINQ, new lists or captured lambdas in the frame loop.

• 06

  A curved-world shader

  The road bends left and right and drops away in the distance. It is purely visual: a custom HLSL shader bends vertices while collisions stay in a flat world.

Tech stack

• Unity 6 (6000.6)
• C#
• URP 17
• UI Toolkit
• Input System
• Unity Localization
• VContainer
• Addressables
• IL2CPP · ARM64
• HLSL
• Meshy
• Blender
• Python