Skip to content
GDE
Explore

Game Development Environment Windows · Alpha

The game in your head.
The project in view.

Write the design. Connect the world. Follow the work into implementation. GDE brings it together in a native Windows workspace, over your own project files.

Explore the manual About this alpha
One project. Three places to work.
GDE Design shows a collection of creatures beside the selected Cinder Stag page.
Select a subject, read beside the collection, and open it when you need more room.

Current GDE interface · editable sample project · concept art shown as design material

01 / Design

Give the game a shape.

Pages, collections and visual plans share the same project. A rough idea can stay rough until you are ready to develop it.

Explore Design
02 / Work

Know what is happening.

Read issues, follow Runs, inspect changes and review results. A place on the board never stands in for evidence.

Explore Work
03 / Project

Keep the context close.

Open an existing project or start with writing. Bring in engine bindings and tooling when the work needs them.

Explore Project

A place for the world

Move between the page
and the bigger picture.

Write a location, place it on a map, connect it to other subjects, or arrange an alternative on a canvas. The linked page stays the same page.

Compare routes, floors and plans without turning design sketches into claims about a running game.

Plan a location
The Saltroot spatial plan with a ferry landing, low-tide crossing, route and flood region linked to the map.
A spatial plan with routes and regions, using the example project's original artwork.
GDE's native markup tools above concept art annotated with arrows, a rectangle and design notes.
Markup records your notes separately from the original image.

Make the intent visible

Point to the thing
you mean.

Sketch over a reference, mark an interaction, or put two ideas side by side. Share the actual view with Director when you want help discussing it.

The image, its annotations and the captured context keep their own identities.

Review concept art

Numbers with their working

Keep the comparison.
Keep the assumptions.

Run a configured calculation, inspect its table and chart, and compare two retained results. Keep the script, inputs and output close to the question you were exploring.

Explore experiments
A GDE numerical experiment compares two lantern-cost curves in a retained A/B chart.
An illustrative local calculation. It is not an engine performance benchmark.

Your project stays yours

Ordinary files.
Useful connections.

GDE works with Markdown, local artwork and inspectable authored views. Git keeps the history; GitHub owns production issues; Codex supplies the connected runtime; your engine owns the game.

Unreal, Godot and Unity have bundled integration paths. A project without an engine or account is still a place to write and build knowledge.

See the engine capability matrix
Development alpha

A workbench taking shape.

This manual describes the implemented alpha. There is no public download or Store release yet. Connected workflows still need evaluation with real providers and engines.

Read the documentation Current scope and limitations