# Construct 3 + event sheets
URL: https://wwadd.dev/stacks/construct3-event-sheets
Last verified: 2026-09-30

An event-led 2D workflow for teams that want to build gameplay visually in a browser-based editor, with scripting available when needed.

## When to use it
- The game is 2D and visual event authoring suits the team
- Designers need to prototype without writing every system in code
- The team accepts proprietary subscription terms and will test its export targets early

## How the pieces fit
Construct layouts organize scenes and objects; event sheets define conditions, actions, and reusable functions. Built-in behaviors handle common movement and interactions. Keep shared rules in reusable events rather than duplicating sheets across layouts. Add JavaScript when a custom integration needs it. Test an exported build early: editing in a browser does not remove platform packaging and performance constraints.

## The tech and its role
- Construct 3: Layouts, objects, behaviors, preview, and exports
- Event sheets: Visual conditions, actions, and reusable gameplay functions
- JavaScript: Optional custom scripting and integrations

## Real-world examples
- Old Guard Game: The official Construct showcase lists this promotional game for Netflix. Construct-family example; the showcase does not establish its engine version or private event-sheet structure. (source: https://www.construct.net/en/make-games/showcase)
- Small Saga: The official showcase includes Small Saga. Construct-family example, not evidence that this title used Construct 3 or the exact workflow described here. (source: https://www.construct.net/en/make-games/showcase)

## Skip if
Skip if an open-source engine is required, advanced 3D is central, or a code-first Lua workflow is the goal.