// dn_framework

Framework Docs

The DN framework powers every browser game on this site. Independent JavaScript modules — no bundler, no build step, just <script> tags and game logic. Four layers: 2D core, tilemap generation, 3D (Three.js), and the data-driven gameplay layer.

v0.1.0 · Vanilla JS ES6+ · No dependencies · Source on GitHub →
// quick_start

Load Order

Include only what your game needs. Order matters — math first, then core, then gameplay layer. 

<!-- 1. Math (always first — everything depends on Vector2D) -->
<script src="/js/dn/mathUtils.js"></script>

<!-- 2. Core loop + input -->
<script src="/js/dn/gameLoop.js"></script>
<script src="/js/dn/inputHandlers.js"></script>

<!-- 3. Scene system (multi-scene games) -->
<script src="/js/dn/scene.js"></script>
<script src="/js/dn/sceneManager.js"></script>

<!-- 4. Camera (scrolling worlds) -->
<script src="/js/dn/camera.js"></script>

<!-- 5. Tilemap generation (procedural worlds) -->
<script src="/js/dn/tilemap/mapWalkers.js"></script>
<script src="/js/dn/tilemap/noiseMapGen.js"></script>
<script src="/js/dn/tilemap/worldGenUtils.js"></script>
<script src="/js/dn/tilemap/tileMapBitmask.js"></script>

<!-- 6. Gameplay layer (entity/behavior RPG framework) -->
<script src="/js/dn/gameplay/inventory.js"></script>
<script src="/js/dn/gameplay/questState.js"></script>
<script src="/js/dn/gameplay/marketManager.js"></script>
<script src="/js/dn/gameplay/behaviors.js"></script>
<script src="/js/dn/gameplay/popupManager.js"></script>
<script src="/js/dn/gameplay/popupRenderer.js"></script>
<script src="/js/dn/gameplay/areaLoader.js"></script>

<!-- 7. Your game -->
<script src="game.js"></script>
// modules

All Modules

Overview What the framework is and how the pieces fit together.
01
public/js/dn/
DN Framework — Overview
What the DN framework is, how its four layers fit together, and which modules are in v0.1.
→
Core — 2D Game loop, scene management, input, math, camera.
02
gameLoop.js
GameLoop
Fixed-timestep game loop. The heartbeat of every DN game.
→
03
mathUtils.js
Vector2D
2D vector math. Positions, velocities, directions — everything that moves uses this.
→
04
sceneManager.js
SceneManager
State machine for game scenes. Handles transitions between loading, menu, gameplay, and game-over states.
→
05
inputHandlers.js
Input Handlers
Two input handler classes — simple left/right/space for action games, four-dir queue for RPG movement.
→
Tilemap & World Gen Procedural generation — walkers, noise, corridors.
06
tilemap/
Tilemap & World Gen
Procedural map generation — path-guaranteed walkers, seeded noise maps, corridor utilities, and bitmask tile resolving.
→
3D Framework Three.js modules for 3D games and the voxel/GLB pipeline.
10
3d/
3D Framework
Three.js-based 3D modules — scene, camera, lighting, and game loop. Y-up / 1m coordinates matching Decentraland.
→
11
3d/voxelRenderer3D.js
Voxel Renderer & Terrain Gen
Native .vox file parser with InstancedMesh rendering, procedural terrain generation with GLB export, and the shared asset pipeline to Decentraland.
→
Gameplay Layer Data-driven entities, behaviors, quests, dialogue, save/load.
20
gameplay/
Gameplay — Architecture
The entity + behavior pattern, data model, area system, and how the gameplay layer fits on top of the DN 2D core.
→
21
gameplay/behaviors.js
Gameplay — Behaviors
Complete reference for all interaction and world behavior classes — config fields, how they work, and which popup types they use.
→
22
gameplay/questState.js
Gameplay — Quests
QuestManager — multi-phase quest definitions, kill objectives, advancePhase behavior, and the last-phase gotcha.
→
23
gameplay/behaviors.js
Gameplay — Dialogue
Branching dialogue trees — node structure, conditions, side effects, and authoring guide.
→
24
gameplay/inventory.js
Gameplay — Save & Load
Save format v3, what is and isn't persisted, save/load API, and notes on area vs. global state.
→
// philosophy

Design Decisions

Library, not framework

Each module is independent. Use only what you need — a simple arcade game uses gameLoop.js alone. A tile-map RPG adds the gameplay layer on top.

Globals by design

Game objects like canvas, context, and input are intentionally global. For a single-canvas browser game, module imports add complexity with no benefit.

Fixed timestep

GameLoop separates update (fixed rate) from render (fires after update). Physics runs at the same speed on any display — 60Hz or 144Hz.

Data-driven gameplay

The gameplay layer defines games as data — areas, entities, behaviors, quests — rather than code. Swapping a movement module changes the game genre; entity data stays the same.

Shared asset pipeline

The 3D framework uses Y-up / 1m coordinates to match Decentraland. A GLB exported by the terrain builder loads directly in a DCL scene — one tool, two runtimes.

Evolving incrementally

This started as the S3D engine (2020). Each game either uses an existing module or adds a new one. v0.1 is the first formal release — confirmed and documented, building from here.