How mitallast/diablo-js works
Main Components
A. Resource Extraction Layer
• DTTool Component (Java-based)
• DS1 Parser (level data)
• DT1 Parser (tile data)
• Palette Reader
• ShadowMaker Component (Java-based)
• Shadow calculation for sprites
B. Asset Management Layer
• Texture Management
• Monster Sprites
• Level Data
• Palette Data
C. Game Engine Layer (JavaScript)
• Renderer Component
• Isometric View Handler
• Canvas Management
• System
• Layer Management (walls, floors, objects)
• Input Handler
• Tab key for map toggle
D. Web Interface
• HTML5 Canvas
• JavaScript Runtime
• [DTTool] -----> [Processed Assets]
• [ShadowMaker] -> [Processed Sprites]
• [Textures] [Sprites] [Level Data] [Palettes]
• /
• /
• /
• [Asset Management System]
• [Game Engine (diablo.js)]
• [HTML5 Canvas Renderer]
Important Relationships
• Data flow from original Diablo 2 assets through DTTool to processed assets
• Sprite processing pipeline through ShadowMaker
• Asset loading path into the game engine
• Rendering pipeline from game engine to canvas
Technical Details
• File format transformations (DS1, DT1, PL2)
• Asset organization structure (ACT1-5 folders)
• Monster sprite categories (BA, FS, SI, SK)
• Shadow processing workflow
Implementation Notes
• The separation between asset processing tools and runtime engine
• The isometric rendering system
• The layer-based map system
• Asset management and loading pipeline