Turning packing into a readable decision game.

In Package Flow, product type, dimensions, box capacity, sequence, racks and time all operate at once. Merely displaying these variables makes the screen feel crowded; giving them the right hierarchy turns them into decisions.

The central design question was how to give players enough information to plan their next move while preserving tension.

On the seven-product conveyor, the item closest to the press is active. Players can access only the top box in each of six columns. The selected box moves to a two-slot preparation rack while a new box from the dispatch queue is added to the bottom of the same column.

A single-product holding rack, combo system, timer and level targets create a choice between using the right box now and saving it for a more critical product later.

• Reading product attributes quickly
• Planning the right box and rack capacity
• Choosing a sequence that completes the dispatch target
• Explaining mistakes through immediate, readable feedback

I separated product, box and level definitions from session state as ScriptableObject data. Instead of creating a new scene for every level, one Gameplay scene is configured through LevelDefinition data.

The packing calculations run in a pure C# core separated from Unity behaviours. Fit, automatic rotation, empty space and missing-requirement penalties are calculated from a single source of truth. Box movement is managed through deterministic position animations rather than random physics.

The conveyor at the top represents flow, the middle section holds active racks and the lower section is the player's decision space. Colours and icons are not decorative; they form a shared language connecting product attributes with box rules.

Testing the information hierarchy in a working prototype before completing the final visual design reduces investment in the wrong visual direction.

In the first user test, I will observe why players stop before looking at completion rate: did they miss a dimension, overlook the rack or receive system feedback too late?

First-attempt completion, retry count, press idle time, dimension and missing-requirement penalties, and rack occupancy will shape the next version of the tutorial flow and difficulty curve.