A Unity toolkit. Two games.
Explore the connections
that make them move.
Reusable simulation systems, spatial algorithms, Unity tooling, and interactive technical prototypes.
Paint a grid, run path finding and waves, then play the two games built on it.
Connecting the tiles…
Square, hexagon or triangle: each tile knows its neighbors. The same graph operations turn those connections into movement, maps and games.
GridMaster · Node · neighbor queriesThe same idea, seen through classes. Explore the inheritance, inspect the responsibilities, then put a connection back into motion.
Select a class to inspect it, or follow a short walkthrough of the connections.
Selected classes and relationships from the original toolkit, with key members abbreviated for readability. The browser experiences use simplified algorithms; this diagram describes the C# project.
Polymorphic Grid gives different tile shapes a common language: nodes, neighbors and traversal. The editor builds the world. The runtime finds a way through it. These two games show where that foundation can lead.
The toolkit is open source on GitLab and available through the Unity Asset Store.
ORIGINAL GAME / GROOVY DEATHA crowd finds its way through a procedural arena. Then the music changes, the floor lights up, and even the enemies start dancing.
Groovy Death Beta, published on itch.io. Four arenas from the shipped build.
Open Groovy Death image full size
ORIGINAL GAME / THE ORANGE RUNAWAYAn escape assembled one block at a time. Hopping between grid nodes becomes a game of timing, traffic, moving platforms and pursuit.
The escape in motion. The pursuit, traffic and city run on the same node grid.
Open The Orange Runaway image full sizeThe playground introduces the ideas as you interact. Here is the broader toolkit and the work built around it.
Built-in square, hexagonal and triangular grids. GridMaster defines a shared API; GenericGrid and NonSymmetricalGenericGrid support custom cell shapes, including alternating orientation.
World/local positions, node radius, walkability, indexed access and neighbor queries. Square grids use direct index conversion; generic layouts use a two-dimensional search tree.
Generic breadth-first, iterative depth-first and recursive depth-first traversal. Acceptance conditions, callbacks, parent tracking, parent priority and breadth-first depth limits.
A* point-to-point routes and breadth-first all-path traversal. Requests, responses, callback delivery, worker threads, reusable finders and search-data pools support runtime pathfinding.
Generate, clear, save and load grids. Scene visualization and walkability painting, grouped node materials, editor preferences, collision-based Area Wizard and Grid Validator.
SerializableGrid and SerializableNode store layouts in ScriptableObjects. Separate runtime/editor libraries, heap-based priority queues and binary search structures support the toolkit.
Seeded obstacle generation checks that every open cell remains reachable. GridVisualizer builds the floor and obstacles from the grid.
Repeated player-rooted path requests let multiple enemies follow the same parent tree. Spawning uses walkable nodes, traversal depth, population limits and increasing difficulty.
Timed dance waves pause pursuit and spawning, switch animation and music states, and propagate floor color changes through BFS.
128-sample FFT analysis, thresholds, beat timing, scale and color synchronizers. The original also includes dual-stick movement/aiming, minigun energy, grenades, health, score, ragdolls and particles.
Four-direction grid movement, swipe input, timed jumps, rotation and landing effects. Ground-height queries and moving placeable grids keep characters attached to their surroundings.
Recycled blocks, weighted land selection and predecessor/successor rules. Simple, arranged, full-row, border, explicit and sequence obstacles combine with accessories.
Traffic, trains, rivers, floating logs, bridges and environmental obstacles. Police use grid paths; ranged cops, SWAT and helicopter controllers add pursuit behaviors.
Coins, score, difficulty progression, character skins and a store. Scriptable tween effects, audio, Cinemachine camera extensions, pause/game-over UI and Unity Ads integrations are present in the original project.
A reusable runtime library with a separate editor layer, custom inspectors, UXML / USS interfaces and scene tools.
Shared neighbor contracts support spatial lookup, traversal, route requests, connectivity checks and enemy navigation.
Animation, collisions, procedural worlds, reactive visuals and mobile controls combine around the grid. Integrations vary by game.
Small graph and game simulations, original character assets, a generated synth beat, and live renderer inspection. Everything runs locally in the browser.
Polymorphic Grid is one of my open-source projects, and the only one with a dedicated experience in this portfolio. I also share the Unity tools below through Theory Team Packages, covering asset preparation, interfaces, animation and the systems behind them.
A Unity toolkit that gives square, hexagonal and triangular grids a shared API for nodes, neighbors, traversal and pathfinding, with editor tools for building and saving layouts.
Unity editor tools for building textures from individual color channels, applying material presets and extracting model materials. Included presets support Standard and HDRP texture workflows.
A reusable Unity UI toolkit for panel groups, temporary panels, fades, tooltips, hover feedback and displaying data. It uses Theory Tween for transitions and shared data-provider interfaces for content.
An extensible framework for custom tween effects, separating reusable ScriptableObject definitions from runtime playback. A shared task manager supports Update, LateUpdate, FixedUpdate and scaled or unscaled time.
A modular inverse-kinematics toolkit with chain solvers, root controls, rotation constraints, pose anchors and finger controls. An orchestrator and editor presets organize complete setups.
Common Unity helpers for geometry and math, weighted random selection, object pooling, collision and trigger events, optional callbacks and inspector-friendly interface references.
Have a similarly specialized problem?