Expertise 02 / Gameplay & Technical Design

From design intent to playable systems

I work equally comfortably on whole-game architecture and individual gameplay features, translating product intent into explicit rules, reliable code, useful tools, and fast designer iteration.

01 / Approach

Rules before wishes
Systems before special cases

I began independently studying game design in 2007 and have continued through established books on traditional and computer-game design. In lead and CTO roles, that knowledge helped me work directly with game-design departments instead of treating their documents as fixed implementation orders.

I translate design intent into consistent game rules, surface conflicts between requested behaviors, and propose implementations that are technically clean while giving designers more useful control. The resulting code, configuration, UI behavior, and QA cases all describe the same product rather than separate interpretations of it.

Formalize behavior

Replace ambiguous feature wishes with states, rules, transitions, ownership, constraints, and testable outcomes.

Protect designer freedom

Create structured configuration models and reusable systems that expand the useful design space without leaking implementation details.

Design for iteration

Make features independently runnable, quick to enter, easy to inspect, and safe to adjust late in production.

02 / Systems

Gameplay work across
the full career

Cubic Games / Pixel Gun 2

Voxel multiplayer FPS foundations

  • Controllable Photon Fusion simulation and presentation pipelines.
  • Game-mode and map separation with independent reload or replacement.
  • Movement prediction, input latency and precision, gameplay synchronization, and voxel-destruction synchronization.
  • Voxel hanging logic, destruction-driven NavMesh rebuilding, and low-end mobile optimization with Jobs, Burst, algorithms, and DOD.
  • A flexible audio subsystem supporting loops, variation, and randomized playback.
  • Supporting modernization with C# 10 and FEPM.

D.A.W.Studio / Four games

Whole CoreGame and reusable product systems

  • Built the CoreGame on Unity Entities across movement, weapon fire, ballistics, controllable bullet-sprites, network synchronization, and other subsystems.
  • Built reusable profiles, UI windows, battle quests, designer-friendly IAP, bundles, pathing, animation, camera, and level-design tools.
  • Supported two online sniper games, a runner, and a roguelike shooter from common architectural principles rather than a single rigid framework.

Wargaming / REVOLT

Simultaneous-turn battler

  • Players submitted actions independently through an asynchronous request/response structure.
  • The authoritative resolution accounted for unit priorities, buffs, and debuffs.
  • Both clients replayed the same resolved outcome simultaneously, preserving the strategic need to anticipate the opponent.

Alfa Bravo / Combat Master

Networked and player-facing FPS systems

  • Implemented networked moving platforms and a train, alongside vehicle systems.
  • Built perks, fully rebindable gamepad input, a player-profile editor, and client-side ScriptableObject tamper protection.
  • Integrated these systems into a live mobile and PC Battle Royale product using Photon Bolt.

Tellurion / RealmCraft

Voxel-world gameplay

  • Designed extensible, programmer-friendly mob AI and accelerated pathfinding.
  • Rebuilt voxel-world movement for stability, performance, and customization.
  • Created internal working VR versions for Gear VR and HTC Vive with VR-specific camera movement and controls.

Plarium / Motorplanet

Racing iteration tools

  • Implemented network synchronization for the mobile racing game.
  • Built an in-editor track builder that let designers place a car and drive any section of a greybox track before art production.

Early engine and game work

Logic, persistence, editors, and shaders

  • At Sonelly: JSON scene hierarchy and components, scene and player persistence, scene effects and transitions, hidden-object inventory gameplay, match-3 logic, and character recoloring.
  • At GSC: proximity triggers, centralized projectile management, property grid, curve editor, and foundational node editor for S.T.A.L.K.E.R. 2.
  • At 8D Studio: the architecture and part-based character-rendering system central to Sketch Tales.

03 / Design information

Give game rules
a stable technical form

Game Design Information

At D.A.W.Studio I built a dedicated system that translated gameplay rules into structured, reusable configuration models. It was separate from MC-VmV and gave designers clear control over gameplay systems.

Configuration architecture

I have repeatedly redesigned how game settings are represented and edited so configuration remains universal, understandable, compatible with client/server flow, and less dependent on code changes.

My role at the Game Design–Technical Design boundary includes feature ideation, story and mechanic discussions, Value/Time decisions, and checking rule consistency. It does not include claiming specialist ownership of economy curves, progression tuning, or balancing.

04 / UI & UX

Interactions should teach
a consistent product language

I have worked with designers and artists to reduce screen clutter and unnecessary clicks, improve onboarding, and make interaction rules consistent enough for players to learn. A user can adapt to almost any interface eventually; the real goal is to remove the confusion before that adaptation happens.

2 days

A typical complete UI window in the streamlined D.A.W.Studio workflow.

2–3 days

A complex screen such as an arsenal with weapon inspection.

One model

Rules, implementation, configuration, QA acceptance, and documentation describe the same feature.

Fast entry

Direct launch into the exact state makes feature design and verification practical.

05 / Breadth

Genres and product types