diff --git a/.cursor/mcp.json b/.cursor/mcp.json
new file mode 100644
index 000000000..a4cd4103f
--- /dev/null
+++ b/.cursor/mcp.json
@@ -0,0 +1,22 @@
+{
+  "mcpServers": {
+    "reva": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": [
+        "--from",
+        "git+https://github.com/bolabaden/agentdecompile",
+        "mcp-agentdecompile"
+      ],
+      "env": {
+        "AGENTDECOMPILE_PROJECT_PATH": "C:/Users/boden/test2.gpr",
+        "GHIDRA_INSTALL_DIR": "C:/Users/boden/Downloads/ghidra_12.0_PUBLIC_20251205/ghidra_12.0_PUBLIC"
+      },
+      "alwaysAllow": [],
+      "disabledTools": [],
+      "disabled": false,
+      "gallery": "https://api.mcp.github.com",
+      "version": "0.1.0"
+    }
+  }
+}
diff --git a/.cursorrules b/.cursorrules
new file mode 100644
index 000000000..3f886ab19
--- /dev/null
+++ b/.cursorrules
@@ -0,0 +1,13 @@
+# KotOR.js Cursor Rules
+
+## Comments
+- Leave TODO/HACK/FIXME comments unmodified, ONLY modify them when you've completely and utterly implemented exhaustively the functionality. Even then this should only be done if you've access to AgentDecompile to triple-check with the reverse engineered Code.
+
+
+## Agents
+- If `reva` or `agentdecompile` is available, start EVERY response by opening the project. Use EXCLUSIVLEY this tool to start with and nothing else until you see the output. Read it to the user then continue with their task. Do this every time.
+```json
+{
+  "path": "C:\\Users\\boden\\KotOR.js.gpr"
+}
+```
diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 000000000..44abff969
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,43 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 2
+
+# TypeScript and JavaScript files
+[*.{ts,tsx,js,jsx}]
+indent_size = 2
+
+# JSON files
+[*.json]
+indent_size = 2
+
+# YAML files
+[*.{yml,yaml}]
+indent_size = 2
+
+# Markdown files
+[*.md]
+trim_trailing_whitespace = false
+indent_size = 2
+
+# Package files
+[package.json]
+indent_size = 2
+
+# Webpack config
+[webpack.config.js]
+indent_size = 2
+
+# Makefile
+[Makefile]
+indent_style = tab
+
diff --git a/.eslintignore b/.eslintignore
new file mode 100644
index 000000000..607d62d9b
--- /dev/null
+++ b/.eslintignore
@@ -0,0 +1,10 @@
+node_modules/
+dist/
+release/
+coverage/
+wiki/
+*.min.js
+*.bundle.js
+build/
+.cache/
+
diff --git a/.eslintrc.yml b/.eslintrc.yml
index c46cae141..ca0bcf79f 100644
--- a/.eslintrc.yml
+++ b/.eslintrc.yml
@@ -1,11 +1,51 @@
 extends:
   - eslint:recommended
   - plugin:import/recommended
-# the following lines do the trick
   - plugin:import/typescript
+parser: '@typescript-eslint/parser'
+parserOptions:
+  ecmaVersion: 2022
+  sourceType: module
+  ecmaFeatures:
+    jsx: true
+plugins:
+  - '@typescript-eslint'
+  - import
+env:
+  node: true
+  browser: true
+  es2022: true
 settings:
   import/resolver:
-    # You will also need to install and configure the TypeScript resolver
-    # See also https://github.com/import-js/eslint-import-resolver-typescript#configuration
     typescript: true
-    node: true
\ No newline at end of file
+    node: true
+rules:
+  # TypeScript specific rules
+  '@typescript-eslint/no-unused-vars':
+    - error
+    - argsIgnorePattern: '^_'
+        varsIgnorePattern: '^_'
+  '@typescript-eslint/explicit-function-return-type': off
+  '@typescript-eslint/no-explicit-any': warn
+
+  # General code quality
+  no-console: warn
+  no-debugger: error
+  no-unused-vars: off  # Use TypeScript version instead
+
+  # Import rules
+  import/order:
+    - error
+    - groups:
+        - builtin
+        - external
+        - internal
+        - parent
+        - sibling
+        - index
+      newlines-between: always
+      alphabetize:
+        order: asc
+        caseInsensitive: true
+  import/no-unresolved: error
+  import/no-duplicates: error
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 000000000..e9e634a96
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,51 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Bug Description
+
+<!-- A clear and concise description of what the bug is -->
+
+## Steps to Reproduce
+
+1.
+2.
+3.
+
+## Expected Behavior
+
+<!-- A clear and concise description of what you expected to happen -->
+
+## Actual Behavior
+
+<!-- A clear and concise description of what actually happened -->
+
+## Screenshots
+
+<!-- If applicable, add screenshots to help explain your problem -->
+
+## Environment
+
+- **OS**: [e.g., Windows 10, macOS 13.0, Ubuntu 22.04]
+- **Node.js Version**: [e.g., 18.17.0]
+- **npm Version**: [e.g., 9.6.7]
+- **KotOR.js Version/Commit**: [e.g., 2.0.0 or commit hash]
+- **Game**: [KotOR I / KotOR II (TSL) / Both]
+- **Browser** (if applicable): [e.g., Chrome 120]
+
+## Additional Context
+
+<!-- Add any other context about the problem here -->
+
+## Logs
+
+<!-- If applicable, paste relevant logs or error messages -->
+
+```
+Paste logs here
+```
+
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 000000000..b3524a6b5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,36 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Feature Description
+
+<!-- A clear and concise description of the feature you'd like to see -->
+
+## Motivation
+
+<!-- Why is this feature needed? What problem does it solve? -->
+
+## Proposed Solution
+
+<!-- Describe how you envision this feature working -->
+
+## Alternatives Considered
+
+<!-- Describe any alternative solutions or features you've considered -->
+
+## Use Cases
+
+<!-- Provide specific examples of how this feature would be used -->
+
+## Additional Context
+
+<!-- Add any other context, mockups, or examples about the feature request -->
+
+## Implementation Notes (Optional)
+
+<!-- If you have ideas about how this could be implemented, share them here -->
+
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000..16416b446
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,56 @@
+## Description
+
+<!-- Provide a brief description of your changes -->
+
+## Type of Change
+
+<!-- Mark the relevant option with an 'x' -->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Code refactoring
+- [ ] Performance improvement
+- [ ] Test addition or update
+
+## Related Issues
+
+<!-- Link related issues using #issue_number -->
+
+Fixes #
+Closes #
+Related to #
+
+## Testing
+
+<!-- Describe the tests you ran and provide instructions so reviewers can reproduce -->
+
+- [ ] Tests pass locally
+- [ ] Added tests for new functionality
+- [ ] Tested in Electron application
+- [ ] Tested in browser (if applicable)
+- [ ] Tested with KotOR I
+- [ ] Tested with KotOR II (TSL)
+
+## Checklist
+
+<!-- Mark completed items with an 'x' -->
+
+- [ ] My code follows the project's style guidelines
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have updated the documentation accordingly
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published
+
+## Screenshots (if applicable)
+
+<!-- Add screenshots to help explain your changes -->
+
+## Additional Notes
+
+<!-- Add any additional information that reviewers should know -->
+
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 000000000..bf1456e02
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,163 @@
+# KotOR.js AI Coding Assistant Instructions
+
+## Project Overview
+
+KotOR.js is a TypeScript reimplementation of the Odyssey Game Engine (from Star Wars: Knights of the Old Republic I & II). It uses THREE.js for rendering, Electron for desktop app distribution, and includes an NWScript interpreter for game scripting.
+
+## Core Architecture
+
+### Major Components & Their Relationships
+
+**1. Game Initialization & State**
+- `GameInitializer` - Bootstraps the engine, loads game archives (KEY, BIF, RIM, ERF files)
+- `CurrentGame` - Active game state container holding references to all managers
+- `Module` - Level/area representation with terrain, objects, scripts, and time management
+- `ModuleArea` - Individual areas within a module (rooms, outdoor sections)
+
+**2. Manager System (Singleton Pattern)**
+Located in `src/managers/`, these manage specific game systems:
+- `ModuleObjectManager` - Creature/placeable/item lifecycle
+- `DialogMessageManager` - Conversation system
+- `InventoryManager` - Item management
+- `PartyManager` - Party composition and NPC management
+- `TwoDAManager` - Caches 2DA data files (game rules, appearance, items)
+- Other managers: TLKManager (dialog text), ConfigManager, AudioEngine, ShaderManager, etc.
+
+Accessed globally via static properties: `CurrentGame.<Manager>.method()`.
+
+**3. Action & Combat System**
+- `Action` (base class) + 30+ action types - Discrete behaviors (move, attack, cast spell, dialog)
+- `ActionQueue` - Per-object action queue supporting grouping and clearing
+- `CombatRound`, `CombatAttackData` - Turn-based combat mechanics
+- Actions read from GFF structs (.utc files for creatures)
+
+**4. Resource System**
+Handles binary file format parsing:
+- `GFFObject`/`GFFStruct`/`GFFField` - GFF (generic file format) parsing, base for .utc/.uti/.are files
+- Archive types: `KEYObject` (index), `BIFObject` (data), `RIMObject` (RIM archives), `ERFObject` (ERF/MOD archives)
+- Data types: `TwoDAObject` (2D arrays), `TLKObject` (dialog strings), `TGAObject`/`TPCObject` (images)
+- Dialog: `DLGObject` for conversation trees
+
+**5. Rendering & Odyssey System**
+- `OdysseyController` - Node hierarchy for game objects in scene
+- `OdysseyWalkMesh` - Collision/movement surfaces
+- Node types: Mesh, Light, Emitter, Dangly (animated), Skin (character), Saber, Reference
+- THREE.js integration in `src/three/odyssey/`
+
+**6. Scripting**
+- `NWScript` - Compiled script loader/executor (.ncs bytecode files)
+- `NWScriptInstance` - Runtime script execution environment
+- `NWScriptDefK1`/`NWScriptDefK2` - Action definitions for each game version
+- Decompiler in `NWScript.decompiler` for debugging
+
+## Developer Workflows
+
+### Development Setup
+```bash
+npm install
+npm run webpack:dev-watch     # Terminal 1: Watch mode build
+npm start                     # Terminal 2: Launch Electron app with hot-reload
+```
+
+### Testing & Quality
+```bash
+npm test                      # Run Jest tests (testMatch: **/*.test.ts)
+npm run test:coverage         # Generate coverage report
+npm run lint                  # ESLint check
+npm run lint:fix              # Auto-fix lint issues
+npm run format                # Prettier formatting
+npm run typedoc               # Generate API docs in wiki/
+```
+
+### Build Variants
+- `tsconfig.electron.json` - Electron main process (tsc target)
+- `tsconfig.game.json` - Game code (webpack/esbuild target)
+- `tsconfig.json` - Base config
+- `webpack.config.js` - Bundles with SCSS/CSS support
+
+## Project-Specific Patterns
+
+### 1. Manager Access Pattern
+```typescript
+// Managers are globally accessible via CurrentGame singleton
+import { CurrentGame } from './engine/CurrentGame';
+
+CurrentGame.moduleObjectManager.getObjectByTag(tag);
+CurrentGame.partyManager.getPartyMembers();
+```
+
+### 2. Action System Pattern
+```typescript
+// Create and queue actions (see ActionFactory)
+const action = ActionFactory.CreateAction(ActionType.ActionMoveToPoint);
+action.SetParameter(0, ActionParameterType.Location, targetLocation);
+creature.actionQueue.Add(action);
+```
+
+### 3. GFF Parsing Pattern
+```typescript
+// GFF structs are hierarchical: GFFObject > GFFStruct > GFFField
+const struct = gffObject.getTopLevelObject();
+const name = struct.getFieldByLabel('FirstName')?.getValue();
+const type = field.getFieldType();  // Returns GFFDataType enum
+```
+
+### 4. Script Execution Pattern
+```typescript
+// Scripts are compiled bytecode files executed per NWScriptDef
+const script = await NWScript.LoadScript('modulename_onenter');
+const instance = new NWScriptInstance(script, owner);
+instance.execute();
+```
+
+## Critical Cross-Component Flows
+
+**Loading a Module:**
+GameInitializer → Module.Load(ifoFile) → ModuleArea.Load() → Creates ModuleObjects → Loads NWScripts → Executes Mod_OnModLoad event
+
+**Executing an Action:**
+Action.Update() checks ActionStatus → Calls subclass virtual methods → May queue follow-up actions → Triggers game events
+
+**Loading a Resource:**
+ResourceLoader.demand() → Checks archives (KEY→BIF lookup, or RIM/ERF) → Parses format-specific handler (GFF, TPC, etc.) → Caches result
+
+## Key Files to Reference
+
+| Task | File(s) |
+|------|---------|
+| Add new action type | `src/actions/Action.ts` (extend), `ActionFactory.ts` (register) |
+| Add game manager | `src/managers/` + export in `index.ts` |
+| Parse new GFF-based format | `src/resource/GFFObject.ts` + create handler |
+| Add NWScript instruction | `NWScriptDefK1.ts` or `NWScriptDefK2.ts` |
+| Add rendering node type | `src/odyssey/OdysseyModelNode*.ts` |
+| Game rules/data | `src/engine/rules/SWRuleSet.ts`, `TwoDAObject.ts` |
+
+## Conventions
+
+- **File naming**: PascalCase for classes, camelCase for utils
+- **Test files**: `*.spec.ts` or `*.test.ts` (Jest looks for `**/*.test.ts`)
+- **Indentation**: 2 spaces
+- **Async patterns**: Use async/await with ResourceLoader (returns Promises)
+- **Error handling**: Type guards preferred over try/catch for resource loading
+- **Enums**: Organize by category in `src/enums/` mirroring src structure
+- **Comments**: JSDoc style with @file, @author, @license headers for major classes
+
+## Important Context
+
+- **No game files included** - Project requires valid KotOR I/II installation for testing
+- **Multi-platform** - Windows, macOS, Linux; browser support via HTTPS only
+- **Hot-reload ready** - Webpack watch mode auto-refreshes Electron during dev
+- **TypeScript strict mode** - Target ES2020+, strict null checks enabled
+- **Version-specific differences** - K1 vs K2 scripts, models, rules managed via NWScriptDefK1/K2
+
+## Debugging Tips
+
+1. **Electron DevTools**: Available in runtime, use console.log and debugger
+2. **Type checking**: `npx tsc --noEmit` for full project type check
+3. **Performance**: `PerformanceMonitor` utility in codebase for profiling
+4. **Script decompilation**: NWScript has built-in decompiler for .ncs files
+5. **Resource issues**: Check archive loading order (KEY→BIF→RIM→ERF) in GameFileSystem
+
+---
+
+For detailed architecture, see [PROJECT_STRUCTURE.md](../PROJECT_STRUCTURE.md). For setup help, see [SETUP.md](../SETUP.md).
diff --git a/.gitignore b/.gitignore
index 5dfbf99eb..4c636ab66 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,18 +1,66 @@
+# Dependencies
 node_modules/
+package-lock.json
+
+# Build outputs
+dist/
 release/
-settings.json
+build/
+*.tsbuildinfo
+
+# Logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
 crash.log
-npm-debug.log
-*.gypi
-backup/
+debug.log
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Coverage directory used by tools like istanbul
+coverage/
+*.lcov
+.nyc_output
+
+# Documentation
+docs/
+wiki/
 
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+.DS_Store
 .ds_store
+
+# OS
+Thumbs.db
+Desktop.ini
+
+# Project specific
+settings.json
 projects/
 Saves/
 tests/
-# src/**/*.js
-dist/
-debug.log
-docs/
-coverage/
-scratch/
\ No newline at end of file
+backup/
+scratch/
+*.gypi
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# Temporary files
+*.tmp
+*.temp
+.cache/
+.history/
diff --git a/.markdownlint.json b/.markdownlint.json
new file mode 100644
index 000000000..7540d4dc1
--- /dev/null
+++ b/.markdownlint.json
@@ -0,0 +1,14 @@
+{
+  "default": true,
+  "MD033": false,
+  "MD024": {
+    "allow_different_nesting": true,
+    "siblings_only": true
+  },
+  "MD060": false,
+  "MD055": false,
+  "MD056": false,
+  "line_length": false,
+  "no-inline-html": false
+}
+
diff --git a/.nvmrc b/.nvmrc
new file mode 100644
index 000000000..0cd525d8c
--- /dev/null
+++ b/.nvmrc
@@ -0,0 +1,2 @@
+18
+
diff --git a/.prettierignore b/.prettierignore
new file mode 100644
index 000000000..c7cd7b518
--- /dev/null
+++ b/.prettierignore
@@ -0,0 +1,9 @@
+node_modules/
+dist/
+release/
+coverage/
+wiki/
+*.min.js
+*.bundle.js
+package-lock.json
+
diff --git a/.prettierrc b/.prettierrc
new file mode 100644
index 000000000..15b52de3a
--- /dev/null
+++ b/.prettierrc
@@ -0,0 +1,14 @@
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 120,
+  "tabWidth": 2,
+  "useTabs": false,
+  "arrowParens": "always",
+  "endOfLine": "lf",
+  "bracketSpacing": true,
+  "jsxSingleQuote": false,
+  "jsxBracketSameLine": false
+}
+
diff --git a/.vscode/extensions.json b/.vscode/extensions.json
new file mode 100644
index 000000000..edd533979
--- /dev/null
+++ b/.vscode/extensions.json
@@ -0,0 +1,8 @@
+{
+  "recommendations": [
+    "dbaeumer.vscode-eslint",
+    "esbenp.prettier-vscode",
+    "ms-vscode.vscode-typescript-next",
+    "orta.vscode-jest"
+  ]
+}
diff --git a/.vscode/launch.json b/.vscode/launch.json
index b648b19c9..c9e195782 100644
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@@ -6,7 +6,7 @@
       "request": "launch",
       "name": "KotOR Launcher",
       "url": "http://localhost:8080/launcher/index.html",
-      "webRoot": "${workspaceFolder}/dist",
+      "webRoot": "${workspaceFolder}/dist"
     },
     {
       "type": "chrome",
@@ -21,6 +21,12 @@
       "name": "TSL",
       "url": "http://localhost:8080/game/index.html?key=tsl",
       "webRoot": "${workspaceFolder}/dist"
+    },
+    {
+      "type": "chrome",
+      "name": "http://127.0.0.1:3000/dist/launcher/index.html",
+      "request": "launch",
+      "url": "http://127.0.0.1:3000/dist/launcher/index.html"
     }
   ]
-}
\ No newline at end of file
+}
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 000000000..772bcb578
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at <https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>
+
+For answers to common questions about this code of conduct, see <https://www.contributor-covenant.org/faq>
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 000000000..2f1916ad5
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,701 @@
+# Contributing to KotOR.js
+
+Thank you for your interest in contributing to KotOR.js! This document provides comprehensive guidelines and instructions for contributing to the project. Please read through this document before submitting contributions.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Quick Start](#quick-start)
+- [Getting Started](#getting-started)
+- [Development Setup](#development-setup)
+- [Project Structure](#project-structure)
+- [Development Workflow](#development-workflow)
+- [Documentation and Configuration Overview](#documentation-and-configuration-overview)
+- [Debugging](#debugging)
+- [Coding Standards](#coding-standards)
+- [Testing](#testing)
+- [Documentation](#documentation)
+- [Submitting Changes](#submitting-changes)
+- [Pull Request Process](#pull-request-process)
+- [Issue Reporting](#issue-reporting)
+- [Common Issues](#common-issues)
+- [Getting Help](#getting-help)
+
+## Code of Conduct
+
+This project adheres to a Code of Conduct that all contributors are expected to follow. Please read [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) before participating.
+
+## Quick Start
+
+```bash
+npm install
+
+# Terminal 1: build in watch mode
+npm run webpack:dev-watch
+
+# Terminal 2: run the app
+npm start
+```
+
+For auto-restart when main-process code changes, use `npm run start-watch` in the second terminal. See [Development Workflow](#development-workflow) and [DEVELOPMENT.md](DEVELOPMENT.md) for all scripts and debugging.
+
+## Getting Started
+
+### Prerequisites
+
+Before you begin, ensure you have the following installed:
+
+- **Node.js**: Version 18.x or higher (LTS recommended)
+  - Check your version: `node --version`
+  - Download: [nodejs.org](https://nodejs.org/)
+- **npm**: Version 9.x or higher (comes with Node.js)
+  - Check your version: `npm --version`
+- **Git**: Latest version
+  - Check your version: `git --version`
+  - Download: [git-scm.com](https://git-scm.com/)
+- **A valid copy of KotOR I or KotOR II** (for testing game functionality)
+  - No game files are distributed with this project
+
+### Recommended Tools
+
+While not required, these tools can improve your development experience:
+
+- **Visual Studio Code** (recommended IDE)
+  - Extensions:
+    - ESLint
+    - Prettier
+    - TypeScript and JavaScript Language Features
+    - Jest Runner
+- **Git GUI Client** (optional): GitHub Desktop, SourceTree, or GitKraken
+- **Chrome DevTools** (for web debugging)
+
+## Development Setup
+
+> **Note**: For detailed setup instructions, including troubleshooting, see [SETUP.md](SETUP.md).
+
+### 1. Fork and Clone the Repository
+
+1. Fork the repository on GitHub
+2. Clone your fork locally:
+
+```bash
+git clone https://github.com/YOUR_USERNAME/KotOR.js.git
+cd KotOR.js
+```
+
+1. Add the upstream repository:
+
+```bash
+git remote add upstream https://github.com/KobaltBlu/KotOR.js.git
+```
+
+### 2. Install Dependencies
+
+Install all project dependencies:
+
+```bash
+npm install
+```
+
+This will install all required packages listed in `package.json`, including:
+
+- TypeScript and type definitions
+- Webpack and build tools
+- React and UI libraries
+- THREE.js for rendering
+- Electron for desktop packaging
+- Testing frameworks (Jest)
+- And many more...
+
+### 3. Verify Installation
+
+Run the test suite to verify everything is set up correctly:
+
+```bash
+npm test
+```
+
+If all tests pass, your development environment is ready!
+
+## Project Structure
+
+```sh
+KotOR.js/
+├── src/                    # Source code
+│   ├── actions/            # Game action system
+│   ├── apps/               # Application entry points
+│   │   ├── debugger/       # Debugger application
+│   │   ├── forge/          # KotOR Forge modding suite
+│   │   ├── game/           # Game client application
+│   │   └── launcher/       # Launcher application
+│   ├── audio/              # Audio engine
+│   ├── combat/             # Combat system
+│   ├── controls/           # Input handling
+│   ├── effects/            # Game effects
+│   ├── electron/           # Electron main process
+│   ├── engine/             # Core engine systems
+│   ├── enums/              # TypeScript enumerations
+│   ├── events/             # Event system
+│   ├── game/                # Game-specific data
+│   ├── gui/                 # GUI system
+│   ├── interface/           # Type definitions
+│   ├── loaders/             # Resource loaders
+│   ├── managers/            # Game managers
+│   ├── module/              # Module system
+│   ├── nwscript/            # NWScript interpreter
+│   ├── odyssey/             # Odyssey format parsers
+│   ├── resource/            # Resource file formats
+│   ├── shaders/             # Shader code
+│   ├── talents/             # Talent/feat system
+│   ├── three/               # THREE.js utilities
+│   ├── utility/             # Utility functions
+│   └── worker/               # Web workers
+├── dist/                    # Build output (generated)
+├── images/                   # Project images and screenshots
+├── wiki/                    # Generated documentation
+├── main.js                  # Electron entry point
+├── package.json             # Project configuration
+├── tsconfig.json            # TypeScript configuration
+├── webpack.config.js        # Webpack configuration
+└── jest.config.js           # Jest test configuration
+```
+
+For more detailed information, see [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md).
+
+## Development Workflow
+
+### npm Scripts
+
+All scripts are defined in `package.json`. Webpack builds every target (KotOR library, launcher, game, Forge, debugger) in one run; there is no script to build a single target.
+
+| Script | Description |
+|--------|-------------|
+| `npm start` | Compile main-process TypeScript once and launch Electron. |
+| `npm run start-watch` | Watch main-process sources; on success, launch Electron (restarts on change). |
+| `npm run start:debug` | Same as `npm start` with `ELECTRON_ENABLE_LOGGING=1` and `NODE_OPTIONS=--trace-warnings`. |
+| `npm run start-watch:debug` | Same as `npm run start-watch` with the same debug/trace environment. |
+| `npm run start:inspect` | Run Electron with `--inspect=5858`; attach via Chrome at `chrome://inspect`. |
+| `npm run webpack:dev` | Single development build. Output under `dist/`. |
+| `npm run webpack:dev-watch` | Development build in watch mode. |
+| `npm run webpack:prod` | Single production build. |
+| `npm run webpack:dev:verbose` | Development build with `--progress` and `--stats verbose`. |
+| `npm run electron:compile` | Compile `tsconfig.electron.json` once; output in `dist/electron/`. |
+| `npm run electron:watch` | Watch main-process TypeScript; does not start Electron. |
+| `npm run electron:build` | Production Webpack + main-process compile + electron-builder (distributable). |
+| `npm test` | Jest: verbose, coverage, no cache (`./src/tests`). |
+| `npm run test:watch` | Jest in watch mode. |
+| `npm run test:verbose` | Jest verbose, no coverage. |
+| `npm run typedoc` | Generate API docs from `./src/KotOR.ts` into `./wiki`. |
+
+Type checking (not in `package.json`): `npx tsc --noEmit` for full project; `npx tsc --noEmit -p tsconfig.forge.json` (or `tsconfig.game.json`, etc.) for a single app.
+
+### File Locations
+
+| Purpose | Location |
+|---------|----------|
+| Source code | `src/` |
+| Main entry | `src/KotOR.ts` |
+| Game init | `src/GameInitializer.ts` |
+| Module system | `src/module/Module.ts` |
+| Build output | `dist/` |
+| Tests | `src/tests/` (match: `**/*.test.ts`) |
+| Config | Root (`package.json`, `tsconfig.*.json`, `webpack.config.js`, `jest.config.js`) |
+
+### Typical Development Session
+
+1. **Start the development build** (in one terminal):
+
+```bash
+npm run webpack:dev-watch
+```
+
+This will watch for file changes and automatically rebuild the project.
+
+1. **Start the Electron application** (in another terminal):
+
+```bash
+npm start
+```
+
+Or use the watch mode for automatic restarts:
+
+```bash
+npm run start-watch
+```
+
+1. **Make your changes** in the `src/` directory
+
+2. **Test your changes** by running the application
+
+3. **Run tests** before committing:
+
+```bash
+npm test
+```
+
+1. **Check code quality**: If ESLint/Prettier are configured in the repo, run `npm run lint` and `npm run format:check` (or equivalent) before committing.
+
+## Documentation and Configuration Overview
+
+### Core documentation
+
+| File | Purpose |
+|------|---------|
+| [README.md](README.md) | Project overview, features, quick start. |
+| [SETUP.md](SETUP.md) | Setup instructions, troubleshooting. |
+| [CONTRIBUTING.md](CONTRIBUTING.md) | Contribution guidelines (this file). |
+| [DEVELOPMENT.md](DEVELOPMENT.md) | Build, run, test, and debug in detail. |
+| [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md) | Project structure and organization. |
+| [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) | Community guidelines. |
+
+### Configuration files
+
+| File | Purpose |
+|------|---------|
+| `.editorconfig` | Editor formatting. |
+| `.gitignore` | Git ignore patterns. |
+| `package.json` | Dependencies and npm scripts. |
+| `tsconfig.json`, `tsconfig.*.json` | TypeScript configuration. |
+| `webpack.config.js` | Webpack build configuration. |
+| `jest.config.js` | Jest test configuration. |
+
+### GitHub
+
+| Path | Purpose |
+|------|---------|
+| `.github/PULL_REQUEST_TEMPLATE.md` | Pull request template. |
+| `.github/ISSUE_TEMPLATE/*.md` | Issue templates. |
+| `.github/workflows/*.yml` | CI (e.g. webpack-dev, webpack-prod). |
+
+### API documentation
+
+Run `npm run typedoc` to generate API docs from `./src/KotOR.ts` into `./wiki/`.
+
+### External resources
+
+- **Discord**: [OpenKotOR Discord Server](https://discord.gg/QxjqVAuN8T)
+- **Forum**: [DeadlyStream – KotOR.js thread](https://deadlystream.com/topic/6608-wip-kotor-js-a-game-engine-for-k1-k2-written-in-javascript/)
+- **GitHub Issues**: [Issue tracker](https://github.com/KobaltBlu/KotOR.js/issues)
+- **TypeScript**: [typescriptlang.org/docs](https://www.typescriptlang.org/docs/)
+- **React**: [react.dev](https://react.dev/)
+- **THREE.js**: [threejs.org/docs](https://threejs.org/docs/)
+- **Electron**: [electronjs.org/docs](https://www.electronjs.org/docs/)
+- **Webpack**: [webpack.js.org](https://webpack.js.org/)
+- **Jest**: [jestjs.io/docs](https://jestjs.io/docs/getting-started)
+
+## Debugging
+
+### Main process (Electron)
+
+- **Logging and trace**: Use `npm run start:debug` or `npm run start-watch:debug` to run with `ELECTRON_ENABLE_LOGGING=1` and `NODE_OPTIONS=--trace-warnings` (output in the terminal).
+- **Inspector**: Use `npm run start:inspect`, then in Chrome open `chrome://inspect` and connect to the Node target.
+- **Manual env (PowerShell)**: `$env:ELECTRON_ENABLE_LOGGING=1; $env:NODE_OPTIONS="--trace-warnings"; npm run start-watch`
+- **Manual env (Bash/zsh)**: `ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings npm run start-watch`
+
+### Renderer (Launcher, Game, Forge)
+
+- Open DevTools from inside the app (e.g. enable `openDevTools()` in `src/electron/LauncherWindow.ts` or `src/electron/ApplicationWindow.ts`).
+- Or run `npx electron --remote-debugging-port=9222 ./main` and in Chrome open `http://localhost:9222` to attach to the renderer.
+
+## Coding Standards
+
+### TypeScript
+
+- Use TypeScript for all new code
+- Enable strict type checking where possible
+- Avoid `any` types; use proper types or `unknown`
+- Use interfaces for object shapes, types for unions/intersections
+- Export types and interfaces that may be used elsewhere
+
+### Code Style
+
+- **Indentation**: 2 spaces (no tabs)
+- **Line Endings**: LF (Unix-style)
+- **Quotes**: Single quotes for strings, double quotes for JSX attributes
+- **Semicolons**: Always use semicolons
+- **Trailing Commas**: Use in multi-line arrays/objects
+- **Max Line Length**: 120 characters (soft limit)
+
+### Naming Conventions
+
+- **Files**: PascalCase for classes/components (e.g., `GameState.ts`), camelCase for utilities (e.g., `binaryReader.ts`)
+- **Classes**: PascalCase (e.g., `GameInitializer`)
+- **Functions/Methods**: camelCase (e.g., `initializeGame`)
+- **Constants**: UPPER_SNAKE_CASE (e.g., `MAX_HEALTH`)
+- **Interfaces**: PascalCase, often prefixed with `I` (e.g., `IGameState`)
+- **Enums**: PascalCase (e.g., `GameEngineType`)
+
+### File Organization
+
+- One class/interface per file
+- Use `index.ts` files for barrel exports
+- Group related files in directories
+- Keep files focused and under 500 lines when possible
+
+### Comments and Documentation
+
+- Use JSDoc comments for public APIs:
+
+```typescript
+/**
+ * Initializes the game engine and loads necessary resources.
+ *
+ * @param gamePath - Path to the game installation directory
+ * @param gameType - Type of game (KotOR I or II)
+ * @returns Promise that resolves when initialization is complete
+ * @throws {Error} If the game path is invalid
+ */
+async function initializeGame(gamePath: string, gameType: GameEngineType): Promise<void> {
+  // Implementation
+}
+```
+
+- Add inline comments for complex logic
+- Keep comments up-to-date with code changes
+
+### Import Organization
+
+Organize imports in this order:
+
+1. External dependencies (React, THREE.js, etc.)
+2. Internal modules (from `src/`)
+3. Relative imports
+4. Type-only imports (use `import type`)
+
+Example:
+
+```typescript
+import * as THREE from 'three';
+import React from 'react';
+
+import { GameState } from '../GameState';
+import { Module } from './Module';
+
+import type { GameEngineType } from '../enums/engine';
+```
+
+### Error Handling
+
+- Use try-catch blocks for async operations
+- Throw meaningful error messages
+- Use custom error classes when appropriate
+- Log errors appropriately (console.error for development)
+
+### Performance Considerations
+
+- Avoid unnecessary re-renders in React components
+- Use Web Workers for heavy computations
+- Cache expensive operations
+- Lazy load resources when possible
+
+## Testing
+
+### Writing Tests
+
+- Write tests for new features
+- Place test files next to source files with `.spec.ts` or `.test.ts` extension
+- Use descriptive test names: `describe('GameState', () => { it('should initialize with default values', () => { ... }) })`
+- Aim for good test coverage, especially for critical paths
+
+### Running Tests
+
+```bash
+# Run all tests (verbose, with coverage)
+npm test
+
+# Run tests in watch mode
+npm run test:watch
+
+# Run tests verbose, no coverage
+npm run test:verbose
+```
+
+Single file: `npx jest --runInBand path/to/file.test.ts`
+
+### Test Structure
+
+```typescript
+import { GameState } from './GameState';
+
+describe('GameState', () => {
+  let gameState: GameState;
+
+  beforeEach(() => {
+    gameState = new GameState();
+  });
+
+  it('should initialize with default values', () => {
+    expect(gameState.isInitialized).toBe(false);
+  });
+
+  it('should throw error when accessing uninitialized state', () => {
+    expect(() => gameState.getCurrentModule()).toThrow();
+  });
+});
+```
+
+## Documentation
+
+### Code Documentation
+
+- Document all public APIs with JSDoc
+- Include parameter types, return types, and exceptions
+- Add usage examples for complex functions
+- Keep documentation in sync with code
+
+### API Documentation
+
+Generate API documentation:
+
+```bash
+npm run typedoc
+```
+
+This creates documentation in the `wiki/` directory.
+
+### README Updates
+
+- Update README.md when adding major features
+- Keep installation instructions current
+- Add examples for new functionality
+
+## Submitting Changes
+
+### Before Submitting
+
+1. **Update your fork**:
+
+```bash
+git fetch upstream
+git checkout main
+git merge upstream/main
+```
+
+1. **Create a feature branch**:
+
+```bash
+git checkout -b feature/your-feature-name
+```
+
+Or for bug fixes:
+
+```bash
+git checkout -b fix/bug-description
+```
+
+1. **Make your changes** following the coding standards
+
+2. **Run tests**:
+
+```bash
+npm test
+```
+
+1. **Check code quality**: If the repo defines `lint` or `format` scripts, run them (e.g. `npm run lint`, `npm run format:check`).
+
+1. **Fix any issues**: Address test failures and, if applicable, run `npm run lint:fix` or `npm run format`.
+
+1. **Commit your changes**:
+
+```bash
+git add .
+git commit -m "feat: add new feature description"
+```
+
+### Commit Message Guidelines
+
+Follow [Conventional Commits](https://www.conventionalcommits.org/) format:
+
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `docs:` - Documentation changes
+- `style:` - Code style changes (formatting, etc.)
+- `refactor:` - Code refactoring
+- `test:` - Test additions/changes
+- `chore:` - Build process or auxiliary tool changes
+- `perf:` - Performance improvements
+
+Examples:
+
+```sh
+feat: add support for KotOR II save game format
+fix: resolve memory leak in resource loader
+docs: update contributing guidelines
+refactor: simplify module loading logic
+test: add tests for combat system
+```
+
+### Commit Best Practices
+
+- Make atomic commits (one logical change per commit)
+- Write clear, descriptive commit messages
+- Reference issue numbers when applicable: `fix: resolve crash (#123)`
+- Avoid committing generated files (`dist/`, `node_modules/`, etc.)
+
+## Pull Request Process
+
+### Creating a Pull Request
+
+1. **Push your branch**:
+
+```bash
+git push origin feature/your-feature-name
+```
+
+1. **Create a Pull Request** on GitHub:
+   - Use a clear, descriptive title
+   - Reference related issues: `Fixes #123` or `Closes #456`
+   - Provide a detailed description of changes
+   - Include screenshots for UI changes
+   - List any breaking changes
+
+### Pull Request Template
+
+```markdown
+## Description
+Brief description of changes
+
+## Type of Change
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Testing
+- [ ] Tests pass locally
+- [ ] Added tests for new functionality
+- [ ] Tested in Electron
+- [ ] Tested in browser (if applicable)
+
+## Checklist
+- [ ] Code follows project style guidelines
+- [ ] Self-review completed
+- [ ] Comments added for complex code
+- [ ] Documentation updated
+- [ ] No new warnings generated
+- [ ] Tests added/updated
+- [ ] All tests pass
+```
+
+### Review Process
+
+- Maintainers will review your PR
+- Address any feedback promptly
+- Make requested changes in new commits (don't force-push unless asked)
+- Keep discussions constructive and respectful
+
+### After Approval
+
+- A maintainer will merge your PR
+- Your contribution will be included in the next release
+- Thank you for contributing! 🎉
+
+## Issue Reporting
+
+### Before Creating an Issue
+
+1. Search existing issues to avoid duplicates
+2. Check if the issue is already fixed in the latest version
+3. Verify the issue is reproducible
+
+### Creating a Good Issue Report
+
+Include:
+
+- **Clear title**: Brief, descriptive summary
+- **Description**: Detailed explanation of the issue
+- **Steps to reproduce**: Exact steps to trigger the issue
+- **Expected behavior**: What should happen
+- **Actual behavior**: What actually happens
+- **Environment**:
+  - OS and version
+  - Node.js version
+  - npm version
+  - KotOR.js version/commit
+- **Screenshots/Logs**: If applicable
+- **Additional context**: Any other relevant information
+
+### Issue Labels
+
+- `bug` - Something isn't working
+- `enhancement` - New feature or improvement
+- `documentation` - Documentation improvements
+- `question` - Questions or discussions
+- `help wanted` - Extra attention needed
+- `good first issue` - Good for newcomers
+
+## Common Issues
+
+| Issue | What to try |
+|-------|--------------|
+| Build fails | `rm -rf node_modules && npm install` (or equivalent on Windows). |
+| Type errors | `npx tsc --noEmit`. |
+| Lint/format | Use repo lint/format scripts if defined; otherwise fix reported issues manually. |
+
+## Getting Help
+
+### Resources
+
+- **Discord**: [OpenKotOR Discord Server](https://discord.gg/QxjqVAuN8T)
+- **Discussion Thread**: [DeadlyStream Forum](https://deadlystream.com/topic/6608-wip-kotor-js-a-game-engine-for-k1-k2-written-in-javascript/)
+- **GitHub Issues**: For bug reports and feature requests
+- **Documentation**: Check the `wiki/` directory for API docs
+
+### Asking Questions
+
+When asking for help:
+
+1. Be specific about your problem
+2. Include relevant code snippets
+3. Share error messages (if any)
+4. Describe what you've already tried
+5. Be patient and respectful
+
+## Additional Guidelines
+
+### Game File Handling
+
+- Never commit game files or assets
+- Use `.gitignore` to exclude game directories
+- Document any file system requirements
+
+### Browser Compatibility
+
+- Test in Chrome (primary target)
+- Note any browser-specific issues
+- Use feature detection when needed
+
+### Performance
+
+- Profile before optimizing
+- Use Chrome DevTools Performance tab
+- Monitor memory usage
+- Test with large modules/files
+
+### Security
+
+- Never commit API keys or secrets
+- Use environment variables for sensitive data
+- Follow secure coding practices
+- Report security issues privately
+
+## Recognition
+
+Contributors will be:
+
+- Listed in the project's contributors
+- Credited in release notes (for significant contributions)
+- Appreciated by the community!
+
+Thank you for contributing to KotOR.js! Your efforts help make this project better for everyone.
+
+### VS Code (optional)
+
+- `Ctrl+Shift+P` — Command palette  
+- `` Ctrl+` `` — Toggle terminal  
+- `F5` — Start debugging  
+- `Ctrl+Shift+B` — Run build task  
+
+---
+
+**Questions?** Open an issue or ask on [Discord](https://discord.gg/QxjqVAuN8T).
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
new file mode 100644
index 000000000..308a0aeb0
--- /dev/null
+++ b/DEVELOPMENT.md
@@ -0,0 +1,147 @@
+# Development
+
+This document describes how to build, run, and test KotOR.js from the repository. For environment setup and prerequisites, see [SETUP.md](SETUP.md).
+
+## Application (Electron)
+
+The desktop app runs in Electron. It compiles TypeScript for the main process, then launches the launcher window (from which you can start the game or Forge).
+
+| Script | Description |
+|--------|--------------|
+| `npm start` | Compile main-process TypeScript once and launch Electron. |
+| `npm run start-watch` | Watch main-process sources; on successful compile, launch Electron (process restarts on change). |
+
+### Running with npx
+
+You can run any npm script via `npx` without cloning or installing the repo first. This works whether the package is published to the npm registry or not (e.g. from a GitHub URL).
+
+**From npm (if published):** use the package name as the command. **From GitHub:** you must use `-p` (or `--package`) to specify the package, then the command name `kotor-js` and the script. The first run from GitHub clones the repo and runs `npm install`, which can take several minutes for this repo.
+
+| Equivalent | From npm (if published) | From GitHub (no publish) |
+|------------|--------------------------|---------------------------|
+| `npm run start:electron` | `npx -y kotor-js start:electron` | `npx -y -p git+https://github.com/KobaltBlu/KotOR.js.git kotor-js start:electron` |
+| `npm run start:web` | `npx -y kotor-js start:web` | `npx -y -p git+https://github.com/KobaltBlu/KotOR.js.git kotor-js start:web` |
+| `npm test` | `npx -y kotor-js test` | `npx -y -p git+https://github.com/KobaltBlu/KotOR.js.git kotor-js test` |
+
+- **`-y`** skips the “install?” prompt.
+- **From repo root (local development):** `node bin/cli.js <script>` or `npx -y -p . kotor-js <script>` (e.g. `npx -y -p . kotor-js start:electron`). Do not use `npx -y . kotor-js …` — that runs the project script named `kotor-js`, not the CLI.
+- **Git shorthand:** `npx -y -p github:KobaltBlu/KotOR.js kotor-js start:electron` is equivalent to the `git+https://...` form.
+- To list all scripts: `npx -y kotor-js --help` or, from GitHub, `npx -y -p git+https://github.com/KobaltBlu/KotOR.js.git kotor-js --help`.
+
+### Debugging the main process
+
+To get Chromium and Node warning stack traces in the terminal:
+
+| Script | Description |
+|--------|--------------|
+| `npm run start:debug` | Same as `npm start` with `ELECTRON_ENABLE_LOGGING=1` and `NODE_OPTIONS=--trace-warnings`. |
+| `npm run start-watch:debug` | Same as `npm run start-watch` with the same environment (for ongoing development with logging). |
+
+To attach a debugger to the main process, use Node’s inspector:
+
+| Script | Description |
+|--------|--------------|
+| `npm run start:inspect` | Compile once and run Electron with `--inspect=5858`. In Chrome, open `chrome://inspect`, then "Open dedicated DevTools for Node" and connect to the target. |
+
+Setting the environment manually (when not using the debug scripts):
+
+- **PowerShell:** `$env:ELECTRON_ENABLE_LOGGING=1; $env:NODE_OPTIONS="--trace-warnings"; npm run start-watch`
+- **CMD:** `set ELECTRON_ENABLE_LOGGING=1 && set NODE_OPTIONS=--trace-warnings && npm run start-watch`
+- **Bash/zsh:** `ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings npm run start-watch`
+
+### Debugging the renderer (Launcher, Game, Forge)
+
+Renderer DevTools can be opened from inside the app (e.g. by enabling `openDevTools()` in `src/electron/LauncherWindow.ts` or `src/electron/ApplicationWindow.ts`). To use Chrome against a remote-debugging endpoint:
+
+1. Compile and run with a fixed port: `npx electron --remote-debugging-port=9222 ./main`
+2. In Chrome, open `http://localhost:9222` and attach to the desired target.
+
+---
+
+## Build (Webpack)
+
+The project uses a single Webpack configuration file that exports multiple configs (KotOR library, launcher, game, Forge, debugger). One `webpack` run builds all of them; there is no npm script to build a single target.
+
+| Script | Description |
+|--------|--------------|
+| `npm run webpack:dev` | Single development build (`NODE_ENV=development`). Output under `dist/`. |
+| `npm run webpack:dev-watch` | Development build in watch mode (rebuilds on file changes). |
+| `npm run webpack:prod` | Single production build (`NODE_ENV=production`). |
+| `npm run webpack:dev:verbose` | Development build with `--progress` and `--stats verbose`. |
+
+### TypeScript typecheck
+
+Full-project type checking (no emit) is available separately from the Webpack build:
+
+| Script | Description |
+|--------|--------------|
+| `npm run typecheck:build` | Type-check all `src` with `tsconfig.buildcheck.json` (strict null checks off). Use before or after changes to catch type errors without strict null/undefined. |
+| `npm run typecheck` | Strict type-check with `tsconfig.check.json` (strict null checks and strict property init off). Use to find null/undefined and other strict issues. |
+
+Webpack uses esbuild-loader, which transpiles TypeScript but does not run the full type checker. Run `npm run typecheck:build` (or `npm run typecheck`) to fail fast on type errors at the command line.
+
+---
+
+## Main-process TypeScript only
+
+If you only need to recompile the Electron main process without running Webpack or Electron:
+
+| Script | Description |
+|--------|--------------|
+| `npm run electron:compile` | Compile `tsconfig.electron.json` once. Output in `dist/electron/`. |
+| `npm run electron:watch` | Watch main-process TypeScript and recompile on change. Does not start Electron; use another terminal to run `npm start` or `electron ./main` when needed. |
+
+---
+
+## Packaged build
+
+| Script | Description |
+|--------|--------------|
+| `npm run electron:build` | Production Webpack build, main-process compile, then `electron-builder build --publish=never` to produce the distributable application. |
+
+---
+
+## Tests
+
+Tests are in `./src/tests` and run with Jest.
+
+| Script | Description |
+|--------|--------------|
+| `npm test` | Run tests with verbose output and coverage. Disables cache. |
+| `npm run test:watch` | Run tests in watch mode. |
+| `npm run test:verbose` | Run tests with verbose output, no coverage. |
+
+To run a single test file: `npx jest --runInBand path/to/file.test.ts`
+
+---
+
+## API documentation
+
+| Script | Description |
+|--------|--------------|
+| `npm run typedoc` | Generate API documentation from `./src/KotOR.ts` into `./wiki`. |
+
+---
+
+## Type checking
+
+These are not defined as npm scripts; run when needed:
+
+- `npx tsc --noEmit` — full project (uses root `tsconfig.json`).
+- `npx tsc --noEmit -p tsconfig.forge.json` — Forge app only.
+- `npx tsc --noEmit -p tsconfig.game.json` — Game app only.
+- Similarly for `tsconfig.launcher.json`, `tsconfig.electron.json`, and other project files.
+
+---
+
+## CI
+
+- **`.github/workflows/webpack-dev.yml`** — On-demand: install dependencies and run `npm run webpack:dev`.
+- **`.github/workflows/webpack-prod.yml`** — Production Webpack build (see workflow for trigger).
+
+---
+
+## Typical development workflow
+
+1. **Terminal 1:** `npm run webpack:dev-watch` — keep front-end bundles (launcher, game, Forge) rebuilding on change.
+2. **Terminal 2:** `npm run start-watch` — run the app and restart the main process on change. For extra logging and trace output, use `npm run start-watch:debug` instead.
diff --git a/PROJECT_STRUCTURE.md b/PROJECT_STRUCTURE.md
new file mode 100644
index 000000000..d969996d2
--- /dev/null
+++ b/PROJECT_STRUCTURE.md
@@ -0,0 +1,395 @@
+# KotOR.js Project Structure
+
+This document provides a detailed overview of the KotOR.js project structure, explaining the purpose and organization of directories and key files.
+
+## Overview
+
+KotOR.js is a TypeScript-based reimplementation of the Odyssey Game Engine. The project is organized into several major components:
+
+- **Core Engine**: Game engine systems and logic
+- **Applications**: Multiple Electron-based applications (Launcher, Game, Forge, Debugger)
+- **Resource System**: File format parsers and loaders
+- **Rendering**: THREE.js-based rendering system
+- **Scripting**: NWScript interpreter
+
+## Root Directory
+
+```sh
+KotOR.js/
+├── src/              # Source code (see below)
+├── dist/             # Build output (generated, gitignored)
+├── release/          # Electron builds (generated, gitignored)
+├── wiki/             # Generated API documentation
+├── images/           # Project images and screenshots
+├── node_modules/     # npm dependencies (gitignored)
+├── main.js           # Electron entry point
+├── package.json      # Project configuration and dependencies
+├── package-lock.json # Dependency lock file
+├── tsconfig.json     # Base TypeScript configuration
+├── tsconfig.*.json   # TypeScript configs for specific builds
+├── webpack.config.js # Webpack build configuration
+├── jest.config.js    # Jest test configuration
+├── electron-builder.json # Electron build configuration
+├── .eslintrc.yml     # ESLint configuration
+├── .editorconfig     # Editor configuration
+├── .prettierrc       # Prettier configuration
+├── .gitignore        # Git ignore rules
+└── README.md         # Project readme
+```
+
+## Source Directory (`src/`)
+
+### Core Modules
+
+#### `actions/` - Action System
+
+Game actions that can be queued and executed (movement, combat, item usage, etc.).
+
+- `Action.ts` - Base action class
+- `ActionQueue.ts` - Action queue management
+- `ActionFactory.ts` - Action creation
+- Individual action types (e.g., `ActionMoveToPoint.ts`, `ActionCombat.ts`)
+
+#### `audio/` - Audio Engine
+
+Audio playback, decoding, and effects system.
+
+- `AudioEngine.ts` - Main audio engine
+- `AudioLoader.ts` - Audio file loading
+- `ADPCMDecoder.ts` - ADPCM audio decoding
+- `ReverbEngine.ts` - Reverb effects
+
+#### `combat/` - Combat System
+
+Combat mechanics, damage calculation, and combat rounds.
+
+- `CombatData.ts` - Combat state
+- `CombatRound.ts` - Combat round management
+- `CombatAttackData.ts` - Attack information
+- `SpellCastInstance.ts` - Spell casting
+
+#### `controls/` - Input Handling
+
+Keyboard, mouse, and gamepad input management.
+
+- `Keyboard.ts` - Keyboard input
+- `Mouse.ts` - Mouse input
+- `GamePad.ts` - Gamepad support
+- `KeyMapper.ts` - Key mapping system
+- `IngameControls.ts` - In-game control handling
+
+#### `effects/` - Game Effects
+
+Game effects system (spells, abilities, item properties).
+
+- Various effect types (damage, healing, stat modifications, etc.)
+- Effect application and management
+
+#### `engine/` - Core Engine Systems
+
+Core game engine functionality.
+
+- `CurrentGame.ts` - Current game state
+- `EngineContext.ts` - Engine context
+- `SaveGame.ts` - Save game handling
+- `rules/` - Game rules (SWRuleSet, etc.)
+- `pathfinding/` - Pathfinding system
+- `menu/` - Menu systems
+
+#### `enums/` - TypeScript Enumerations
+
+Type-safe enumerations for game constants.
+
+- Organized by category (actions, audio, combat, etc.)
+- `index.ts` - Barrel export
+
+#### `events/` - Event System
+
+Game event handling and dispatching.
+
+- Event types and handlers
+- Event factory
+
+#### `gui/` - GUI System
+
+Game GUI components and rendering.
+
+- `GUIControl.ts` - Base GUI control
+- `GUIButton.ts`, `GUILabel.ts`, etc. - Specific controls
+- `GameMenu.ts` - Game menu system
+
+#### `interface/` - Type Definitions
+
+TypeScript interfaces and type definitions.
+
+- Organized by category
+- Type definitions for game objects
+
+#### `loaders/` - Resource Loaders
+
+Resource loading and caching system.
+
+- Various loader types
+- Resource caching
+
+#### `managers/` - Game Managers
+
+High-level game state managers.
+
+- `ModuleObjectManager.ts` - Module object management
+- `DialogMessageManager.ts` - Dialog system
+- `InventoryManager.ts` - Inventory management
+- `PartyManager.ts` - Party management
+- And many more...
+
+#### `module/` - Module System
+
+Module loading and management (IFO files, areas, etc.).
+
+- `Module.ts` - Main module class
+- Module-related utilities
+
+#### `nwscript/` - NWScript Interpreter
+
+NWScript bytecode interpreter and execution.
+
+- `NWScript.ts` - Main interpreter
+- `NWScriptInstance.ts` - Script instance
+- `NWScriptDefK1.ts`, `NWScriptDefK2.ts` - Script definitions
+
+#### `odyssey/` - Odyssey Format Parsers
+
+Parsers for Odyssey engine file formats.
+
+- Model formats (MDL, MDX)
+- Animation formats
+- Texture formats
+- `controllers/` - Animation controllers
+
+#### `resource/` - Resource File Formats
+
+Parsers for game resource formats.
+
+- `GFFObject.ts` - GFF file format
+- `ERFObject.ts` - ERF archive format
+- `KEYObject.ts` - KEY file format
+- `BIFObject.ts` - BIF archive format
+- `RIMObject.ts` - RIM archive format
+- And more...
+
+#### `shaders/` - Shader Code
+
+GLSL shaders for rendering.
+
+- Various shader files
+
+#### `talents/` - Talent System
+
+Feats, skills, and spells system.
+
+- `TalentObject.ts` - Base talent
+- `TalentFeat.ts` - Feats
+- `TalentSkill.ts` - Skills
+- `TalentSpell.ts` - Spells
+
+#### `three/` - THREE.js Utilities
+
+THREE.js helper utilities and extensions.
+
+- THREE.js integration code
+
+#### `utility/` - Utility Functions
+
+General-purpose utility functions.
+
+- `binary/` - Binary reading/writing
+- `GameFileSystem.ts` - File system abstraction
+- `ConfigClient.ts` - Configuration management
+- And more...
+
+#### `worker/` - Web Workers
+
+Web worker scripts for background processing.
+
+- `server.ts` - Worker server
+- `worker-tex.ts` - Texture processing worker
+
+### Application Entry Points (`apps/`)
+
+#### `apps/launcher/` - Launcher Application
+
+Main launcher UI for selecting and launching games.
+
+- `index.tsx` - Main launcher component
+- React components for launcher UI
+- SCSS styles
+
+#### `apps/game/` - Game Client Application
+
+Main game client application.
+
+- `index.tsx` - Game client entry point
+- `app.tsx` - Main game app component
+- React components for game UI
+
+#### `apps/forge/` - KotOR Forge Modding Suite
+
+Modding tool suite for creating and editing KotOR content.
+
+- `index.tsx` - Forge entry point
+- `App.tsx` - Main Forge application
+- `Project.ts` - Project management
+- `EditorFile.ts` - File editing
+- Various editor components
+- Monaco Editor integration
+
+#### `apps/debugger/` - Debugger Application
+
+Development debugger for inspecting game state.
+
+- `index.tsx` - Debugger entry point
+- Debugger UI components
+
+#### `apps/common/` - Shared Application Code
+
+Code shared between applications.
+
+- Common components and utilities
+
+### Electron (`electron/`)
+
+Electron main process code.
+
+- `Main.ts` - Main Electron process
+- `ApplicationWindow.ts` - Application window management
+- `LauncherWindow.ts` - Launcher window
+- `WindowManager.ts` - Window management
+- `preload.ts` - Preload scripts
+
+### Game-Specific Data (`game/`)
+
+Game-specific data and definitions.
+
+- `kotor/` - KotOR I specific data
+- `tsl/` - KotOR II (TSL) specific data
+- `CharGenClasses.ts` - Character generation classes
+
+### Root Source Files
+
+- `KotOR.ts` - Main library entry point and exports
+- `GameInitializer.ts` - Game initialization logic
+- `GameState.ts` - Game state management
+- `LoadingScreen.ts` - Loading screen
+- `index.d.ts` - TypeScript declaration file
+
+## Build Configuration
+
+### TypeScript Configurations
+
+- `tsconfig.json` - Base configuration
+- `tsconfig.electron.json` - Electron build
+- `tsconfig.launcher.json` - Launcher build
+- `tsconfig.game.json` - Game client build
+- `tsconfig.forge.json` - Forge build
+- `tsconfig.debugger.json` - Debugger build
+- `tsconfig.kotorjs.json` - Library build
+
+### Webpack Configuration
+
+`webpack.config.js` defines multiple build configurations:
+
+- Library build (KotOR.js)
+- Launcher build
+- Game client build
+- Forge build
+- Debugger build
+
+Each build has its own entry point, output directory, and specific settings.
+
+## Output Directories
+
+### `dist/` - Build Output
+
+Generated by webpack, contains:
+
+- `KotOR.js` - Main library bundle
+- `server.js` - Worker server bundle
+- `launcher/` - Launcher application
+- `game/` - Game client
+- `forge/` - Forge application
+- `debugger/` - Debugger application
+- Assets (icons, fonts, etc.)
+
+### `release/` - Electron Builds
+
+Generated by electron-builder, contains platform-specific builds:
+
+- Windows portable executables
+- macOS DMG files
+- Linux AppImages
+
+## Development Workflow
+
+1. **Source Code**: Edit files in `src/`
+2. **Build**: Webpack compiles to `dist/`
+3. **Run**: Electron loads from `dist/`
+4. **Test**: Jest tests in `src/tests/` or `*.spec.ts` files
+5. **Document**: TypeDoc generates `wiki/`
+
+## Key Concepts
+
+### Module System
+
+Modules represent game areas/levels. Each module has:
+
+- IFO file (module info)
+- ARE file (area data)
+- GIT file (game instance template)
+- Associated resources (models, textures, scripts)
+
+### Resource System
+
+Resources are loaded from:
+
+- BIF archives (game data)
+- ERF archives (mods)
+- RIM files (module-specific)
+- KEY files (resource index)
+
+### Rendering Pipeline
+
+- THREE.js for 3D rendering
+- Custom shaders for game-specific effects
+- Odyssey format models and animations
+- GUI overlay system
+
+## File Naming Conventions
+
+- **Classes**: PascalCase (e.g., `GameState.ts`)
+- **Utilities**: camelCase (e.g., `binaryReader.ts`)
+- **Interfaces**: PascalCase, often prefixed with `I` (e.g., `IGameState.ts`)
+- **Enums**: PascalCase (e.g., `GameEngineType.ts`)
+- **Tests**: `*.spec.ts` or `*.test.ts`
+- **Index files**: `index.ts` for barrel exports
+
+## Dependencies
+
+Major dependencies (see `package.json`):
+
+- **TypeScript**: Language and type system
+- **React**: UI framework for applications
+- **THREE.js**: 3D rendering
+- **Electron**: Desktop application framework
+- **Webpack**: Build system
+- **Jest**: Testing framework
+- **Monaco Editor**: Code editor (Forge)
+
+## Getting Started
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed setup instructions.
+
+## Additional Resources
+
+- [API Documentation](wiki/) - Generated TypeDoc documentation
+- [README.md](README.md) - Project overview
+- [CONTRIBUTING.md](CONTRIBUTING.md) - Contribution guidelines
diff --git a/README.md b/README.md
index cd3892f93..439661044 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,5 @@
 # KotOR.js
+
 ![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?style=for-the-badge&logo=typescript&logoColor=white)
 ![JavaScript](https://img.shields.io/badge/JavaScript-323330?style=for-the-badge&logo=javascript&logoColor=F7DF1E)
 ![THREE JS](https://img.shields.io/badge/ThreeJs-black?style=for-the-badge&logo=three.js&logoColor=white)
@@ -13,58 +14,162 @@
 
 KotOR.js is a TypeScript-based reimplementation of the Odyssey Game Engine that powered the original Star Wars: Knights of the Old Republic (KotOR) and its sequel, KotOR II: The Sith Lords (TSL). The project aims to support the complete feature set of the original engine. While still in the early stages of development, many systems are already online in some form or fashion.
 
-In addition to the game engine, the project includes an early attempt at a modding suite called KotOR Forge. 
+In addition to the game engine, the project includes an early attempt at a modding suite called KotOR Forge.
 
 ## Technologies
-- The code has been re-written in TypeScript and compiles down into JavaScript. 
-- THREE.js is used for the base of the rendering engine. 
-- Electron is used to package and publish a desktop application. 
 
-[Discussion Thread](https://deadlystream.com/topic/6608-wip-kotor-js-a-game-engine-for-k1-k2-written-in-javascript/)  
+- The code has been re-written in TypeScript and compiles down into JavaScript.
+- THREE.js is used for the base of the rendering engine.
+- Electron is used to package and publish a desktop application.
+
+[Discussion Thread](https://deadlystream.com/topic/6608-wip-kotor-js-a-game-engine-for-k1-k2-written-in-javascript/)
 [KotOR.js Youtube Channel](https://www.youtube.com/channel/UC7b4RL2mj0WJ7fEvbJePDbA)
 
 [![OpenKotOR Discord](https://discordapp.com/api/guilds/739590575359262792/widget.png?style=banner2)](https://discord.gg/QxjqVAuN8T)
 
 ## Supported Games
+
 The following games are currently supported:
+
 - [x] [Star Wars: Knights of the Old Republic (PC)](https://en.wikipedia.org/wiki/Star_Wars:_Knights_of_the_Old_Republic)
 - [x] [Star Wars: Knights of the Old Republic II The Sith Lords (PC)](https://en.wikipedia.org/wiki/Star_Wars_Knights_of_the_Old_Republic_II:_The_Sith_Lords)
 
 ## Requirements
+
 You will need a valid copy of either KotOR I or KotOR II installed on your system if you want to use KotOR.js to interface with the files of either game. No game files are distributed with this project.
 
 ## Web Compatibility (NEW)
 
 The recent transition to TypeScript has brought many improvements to the codebase, including Chrome support. When the project is compiled, the contents of the `dist` folder can be uploaded to a web server. The only requirement is that the site must be accessed from behind a valid SSL certificate. Using the latest version of Chrome is recommended.
 
-
 [![Demo Icon]][Demo Link]
 
 [Demo Link]: https://play.swkotor.net/ 'Online Playable Demo'
 [Demo Icon]: https://img.shields.io/badge/Online_Playable_Demo-37a779?style=for-the-badge&logoColor=white&logo=google-chrome
 
-## Getting Started (Developer)
-To get started as a developer, follow these steps:
+## Getting Started
+
+### Prerequisites
+
+Before you begin, ensure you have the following installed:
+
+- **Node.js**: Version 18.x or higher (LTS recommended)
+  - Check your version: `node --version`
+  - Download: [nodejs.org](https://nodejs.org/)
+- **npm**: Version 9.x or higher (comes with Node.js)
+  - Check your version: `npm --version`
+- **Git**: Latest version
+  - Check your version: `git --version`
+  - Download: [git-scm.com](https://git-scm.com/)
+- **A valid copy of KotOR I or KotOR II** (for testing game functionality)
+  - No game files are distributed with this project.  No BioWare, LucasArts, nor Disney trademarked content will ever be distributed with this project.
+
+### Quick Start (Developer)
+
+1. **Clone the repository**:
 
-1. Download and install [npm (Node Package Manager)](https://www.npmjs.com/get-npm).
-2. Clone the KotOR.js repository.
-3. Install the npm dependencies.
+```bash
+git clone https://github.com/KobaltBlu/KotOR.js.git
+cd KotOR.js
+```
+
+1. **Install dependencies**:
 
 ```bash
 npm install
 ```
-4. Run the build command
+
+1. **Start development build** (in one terminal):
 
 ```bash
 npm run webpack:dev-watch
 ```
-5. Run the start command in a separate console/shell window
+
+1. **Start the application** (in another terminal):
 
 ```bash
-npm run start
+npm start
 ```
 
-6. Enjoy
+1. **Enjoy!** The Electron application should launch automatically.
+
+### Available Scripts
+
+#### Development
+
+- `npm start` - Compile and start Electron application
+- `npm run start-watch` - Start with auto-reload on changes
+- `npm run webpack:dev` - Build once in development mode
+- `npm run webpack:dev-watch` - Build in watch mode (auto-rebuild on changes)
+
+#### Building
+
+- `npm run webpack:prod` - Build for production
+- `npm run electron:compile` - Compile Electron TypeScript files
+- `npm run electron:build` - Build complete Electron application
+
+#### Testing
+
+- `npm test` - Run all tests with coverage
+- `npm run test:watch` - Run tests in watch mode
+- `npm run test:coverage` - Generate coverage report
+
+#### Code Quality
+
+- `npm run lint` - Run ESLint
+- `npm run lint:fix` - Fix ESLint issues automatically
+- `npm run format` - Format code with Prettier
+- `npm run format:check` - Check code formatting
+
+#### Documentation
+
+- `npm run typedoc` - Generate API documentation
+
+### Development Workflow
+
+For a typical development session:
+
+1. **Terminal 1**: Run `npm run webpack:dev-watch` to automatically rebuild on file changes
+2. **Terminal 2**: Run `npm start` to launch the Electron application
+3. **Make changes** in the `src/` directory
+4. **Test your changes** - the application will reload automatically
+5. **Run tests** before committing: `npm test`
+6. **Check code quality**: `npm run lint && npm run format:check`
+
+### Project Structure
+
+The project is organized into several major components:
+
+- **Core Engine** (`src/engine/`, `src/module/`) - Game engine systems
+- **Applications** (`src/apps/`) - Launcher, Game, Forge, Debugger
+- **Resource System** (`src/resource/`, `src/loaders/`) - File format parsers
+- **Rendering** (`src/three/`, `src/shaders/`) - THREE.js rendering system
+- **Scripting** (`src/nwscript/`) - NWScript interpreter
+
+For detailed information, see [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md).
+
+### Contributing
+
+We welcome contributions! Please read:
+
+- **[CONTRIBUTING.md](CONTRIBUTING.md)** - Contribution guidelines, quick start, scripts, and documentation overview
+- **[SETUP.md](SETUP.md)** - Detailed setup instructions and troubleshooting
+- **[DEVELOPMENT.md](DEVELOPMENT.md)** - Build, run, test, and debug in detail
+
+Key topics covered:
+
+- Development setup and workflow
+- Coding standards and best practices
+- Testing requirements
+- Pull request process
+- Code of conduct
+
+### Getting Help
+
+- **Discord**: [OpenKotOR Discord Server](https://discord.gg/QxjqVAuN8T)
+- **Discussion Thread**: [DeadlyStream Forum](https://deadlystream.com/topic/6608-wip-kotor-js-a-game-engine-for-k1-k2-written-in-javascript/)
+- **GitHub Issues**: For bug reports and feature requests
+- **Documentation**: Check the `wiki/` directory for API docs (generate with `npm run typedoc`)
 
 ## Screenshots
 
@@ -84,20 +189,28 @@ npm run start
 
 | **KotOR.js (2023) - In Browser Demo** | **KotOR JS - Combat Animations Progress Jan 2021** | **KotOR Forge - WIP: Lip Sync Editor Jan 2019** |
 |:---:|:---:|:---:|
-| [![KotOR.js (2023) - In Browser Demo](https://img.youtube.com/vi/ZT_9vKRC1t8/0.jpg)](https://www.youtube.com/watch?v=ZT_9vKRC1t8) | [![KotOR JS - Combat Animations Progress Jan 2021](https://img.youtube.com/vi/4oQ8nj_zO-w/0.jpg)](https://www.youtube.com/watch?v=4oQ8nj_zO-w) | [![KotOR Forge - WIP: Lip Sync Editor Jan 2019](https://img.youtube.com/vi/4s4uTyP5yqA/0.jpg)](https://www.youtube.com/watch?v=4s4uTyP5yqA) 
-| **KotOR JS - Lighting & Lipsync Progress Nov 2018** | **KotOR JS : TSL - Gameplay Compilation Sep 2018** | **KotOR JS: The Endar Spire Sep 2018** 
+| [![KotOR.js (2023) - In Browser Demo](https://img.youtube.com/vi/ZT_9vKRC1t8/0.jpg)](https://www.youtube.com/watch?v=ZT_9vKRC1t8) | [![KotOR JS - Combat Animations Progress Jan 2021](https://img.youtube.com/vi/4oQ8nj_zO-w/0.jpg)](https://www.youtube.com/watch?v=4oQ8nj_zO-w) | [![KotOR Forge - WIP: Lip Sync Editor Jan 2019](https://img.youtube.com/vi/4s4uTyP5yqA/0.jpg)](https://www.youtube.com/watch?v=4s4uTyP5yqA)
+| **KotOR JS - Lighting & Lipsync Progress Nov 2018** | **KotOR JS : TSL - Gameplay Compilation Sep 2018** | **KotOR JS: The Endar Spire Sep 2018**
 | [![KotOR JS - Lighting & Lipsync Progress Nov 2018](https://img.youtube.com/vi/2SATn5W2sb4/0.jpg)](https://www.youtube.com/watch?v=2SATn5W2sb4) | [![KotOR JS : TSL - Gameplay Compilation Sep 2018](https://img.youtube.com/vi/IpP6BQJ5ZBQ/0.jpg)](https://www.youtube.com/watch?v=IpP6BQJ5ZBQ) | [![KotOR JS: The Endar Spire](https://img.youtube.com/vi/y2UzOH5bcAQ/0.jpg)](https://www.youtube.com/watch?v=y2UzOH5bcAQ)
 
 </div>
 
 ## Influences & Credits
 
-Without these people below I couldn't have gotten this far.  
-[xoreos](https://xoreos.org/)  
-[The KotOR Modding Community](https://deadlystream.com/)   
-  
+Without these people below I couldn't have gotten this far.
+[xoreos](https://xoreos.org/)
+[The KotOR Modding Community](https://deadlystream.com/)
+
 And many many more!
 
+## Documentation
+
+- [CONTRIBUTING.md](CONTRIBUTING.md) - Contribution guidelines and development workflow
+- [SETUP.md](SETUP.md) - Detailed setup instructions
+- [DEVELOPMENT.md](DEVELOPMENT.md) - Build, run, test, and debug
+- [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md) - Project structure overview
+- [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) - Code of conduct
+
 ## License
 
 [GPL 3.0 (GNU General Public License)](LICENSE.md)
diff --git a/SETUP.md b/SETUP.md
new file mode 100644
index 000000000..0980173a5
--- /dev/null
+++ b/SETUP.md
@@ -0,0 +1,410 @@
+# KotOR.js Setup Guide
+
+This guide provides detailed setup instructions for getting KotOR.js running on your development machine.
+
+## Table of Contents
+
+- [System Requirements](#system-requirements)
+- [Installing Prerequisites](#installing-prerequisites)
+- [Project Setup](#project-setup)
+- [Verifying Installation](#verifying-installation)
+- [Troubleshooting](#troubleshooting)
+- [Next Steps](#next-steps)
+
+## System Requirements
+
+### Operating System
+
+KotOR.js supports the following operating systems:
+
+- **Windows**: Windows 10 or later
+- **macOS**: macOS 10.15 (Catalina) or later
+- **Linux**: Most modern distributions (Ubuntu 20.04+, Fedora 32+, etc.)
+
+### Software Requirements
+
+- **Node.js**: Version 18.x or higher (LTS recommended)
+- **npm**: Version 9.x or higher (comes with Node.js)
+- **Git**: Latest version
+- **A valid copy of KotOR I or KotOR II** (for testing)
+
+### Hardware Requirements
+
+- **RAM**: 8GB minimum, 16GB recommended
+- **Disk Space**: At least 2GB free for dependencies and build output
+- **Graphics**: Any modern graphics card (for testing rendering)
+
+## Installing Prerequisites
+
+### Node.js and npm
+
+#### Windows
+
+1. Visit [nodejs.org](https://nodejs.org/)
+2. Download the LTS version (recommended)
+3. Run the installer and follow the prompts
+4. Verify installation:
+
+   ```powershell
+   node --version
+   npm --version
+   ```
+
+#### macOS
+
+**Using Homebrew (recommended):**
+
+```bash
+brew install node
+```
+
+**Or download from nodejs.org:**
+
+1. Visit [nodejs.org](https://nodejs.org/)
+2. Download the macOS installer
+3. Run the installer
+
+**Verify installation:**
+
+```bash
+node --version
+npm --version
+```
+
+#### Linux
+
+**Ubuntu/Debian:**
+
+```bash
+curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
+sudo apt-get install -y nodejs
+```
+
+**Fedora/RHEL:**
+
+```bash
+curl -fsSL https://rpm.nodesource.com/setup_18.x | sudo bash -
+sudo yum install -y nodejs
+```
+
+**Or use your distribution's package manager:**
+
+```bash
+# Ubuntu/Debian
+sudo apt update
+sudo apt install nodejs npm
+
+# Fedora
+sudo dnf install nodejs npm
+```
+
+**Verify installation:**
+
+```bash
+node --version
+npm --version
+```
+
+### Git
+
+#### Windows
+
+1. Visit [git-scm.com](https://git-scm.com/)
+2. Download the Windows installer
+3. Run the installer with default settings
+4. Verify installation:
+
+   ```powershell
+   git --version
+   ```
+
+#### macOS
+
+Git comes pre-installed. If you need to update:
+
+```bash
+# Using Homebrew
+brew install git
+
+# Verify
+git --version
+```
+
+#### Linux
+
+```bash
+# Ubuntu/Debian
+sudo apt update
+sudo apt install git
+
+# Fedora
+sudo dnf install git
+
+# Verify
+git --version
+```
+
+### Visual Studio Code (Recommended IDE)
+
+1. Visit [code.visualstudio.com](https://code.visualstudio.com/)
+2. Download for your platform
+3. Install recommended extensions:
+   - ESLint
+   - Prettier
+   - TypeScript and JavaScript Language Features
+   - Jest Runner
+
+## Project Setup
+
+### 1. Clone the Repository
+
+```bash
+# Clone the repository
+git clone https://github.com/KobaltBlu/KotOR.js.git
+cd KotOR.js
+```
+
+### 2. Install Dependencies
+
+```bash
+npm install
+```
+
+This will:
+
+- Install all npm packages listed in `package.json`
+- Create `node_modules/` directory
+- May take several minutes depending on your internet connection
+
+**Note**: If you encounter errors, try:
+
+```bash
+# Clear npm cache
+npm cache clean --force
+
+# Delete node_modules and package-lock.json
+rm -rf node_modules package-lock.json  # Linux/macOS
+# or
+rmdir /s /q node_modules & del package-lock.json  # Windows
+
+# Reinstall
+npm install
+```
+
+### 3. Verify Node Version (Optional)
+
+If you're using `nvm` (Node Version Manager), you can use the project's specified version:
+
+```bash
+# Install/use the correct Node version
+nvm install
+nvm use
+```
+
+The project includes a `.nvmrc` file specifying Node.js 18.
+
+## Verifying Installation
+
+### Run Tests
+
+Verify that everything is set up correctly:
+
+```bash
+npm test
+```
+
+All tests should pass. If tests fail, check the error messages and refer to [Troubleshooting](#troubleshooting).
+
+### Check Code Quality Tools
+
+Verify linting and formatting tools:
+
+```bash
+# Check linting
+npm run lint
+
+# Check formatting
+npm run format:check
+```
+
+### Build the Project
+
+Test the build process:
+
+```bash
+# Development build
+npm run webpack:dev
+
+# Production build (takes longer)
+npm run webpack:prod
+```
+
+The build output will be in the `dist/` directory.
+
+### Start the Application
+
+1. **Start the development build** (in one terminal):
+
+   ```bash
+   npm run webpack:dev-watch
+   ```
+
+   This will watch for file changes and automatically rebuild.
+
+2. **Start the Electron application** (in another terminal):
+
+   ```bash
+   npm start
+   ```
+
+The Electron application should launch. If it doesn't, check the terminal for error messages.
+
+## Troubleshooting
+
+### Common Issues
+
+#### "Command not found: node" or "Command not found: npm"
+
+**Problem**: Node.js/npm is not installed or not in your PATH.
+
+**Solution**:
+
+1. Verify Node.js is installed: `node --version`
+2. If not installed, follow [Installing Prerequisites](#installing-prerequisites)
+3. If installed but not found, add Node.js to your PATH:
+   - Windows: Restart your terminal or add Node.js to system PATH
+   - macOS/Linux: Check your shell profile (`.bashrc`, `.zshrc`, etc.)
+
+#### "EACCES" or Permission Errors
+
+**Problem**: npm doesn't have permission to write to certain directories.
+
+**Solution**:
+
+```bash
+# Fix npm permissions (Linux/macOS)
+mkdir ~/.npm-global
+npm config set prefix '~/.npm-global'
+echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc  # or ~/.zshrc
+source ~/.bashrc  # or source ~/.zshrc
+
+# Or use sudo (not recommended)
+sudo npm install -g npm
+```
+
+#### "Module not found" Errors
+
+**Problem**: Dependencies are not installed correctly.
+
+**Solution**:
+
+```bash
+# Delete and reinstall
+rm -rf node_modules package-lock.json
+npm install
+```
+
+#### TypeScript Compilation Errors
+
+**Problem**: TypeScript configuration issues or type errors.
+
+**Solution**:
+
+1. Check TypeScript version: `npx tsc --version`
+2. Verify `tsconfig.json` exists
+3. Check for type errors: `npx tsc --noEmit`
+4. Update TypeScript if needed: `npm install typescript@latest --save-dev`
+
+#### Webpack Build Errors
+
+**Problem**: Webpack configuration or dependency issues.
+
+**Solution**:
+
+1. Clear webpack cache: `rm -rf node_modules/.cache`
+2. Rebuild: `npm run webpack:dev`
+3. Check for circular dependencies (webpack will warn)
+4. Verify all dependencies are installed: `npm install`
+
+#### Electron Won't Start
+
+**Problem**: Electron application fails to launch.
+
+**Solution**:
+
+1. Check that webpack build completed successfully
+2. Verify `dist/` directory exists and contains files
+3. Check terminal for error messages
+4. Try rebuilding: `npm run webpack:dev && npm start`
+5. On Linux, you may need additional dependencies:
+
+   ```bash
+   # Ubuntu/Debian
+   sudo apt install libnss3 libatk-bridge2.0-0 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2
+   ```
+
+#### Port Already in Use
+
+**Problem**: Port is already in use by another process.
+
+**Solution**:
+
+1. Find the process using the port:
+
+   ```bash
+   # Linux/macOS
+   lsof -i :PORT_NUMBER
+
+   # Windows
+   netstat -ano | findstr :PORT_NUMBER
+   ```
+
+2. Kill the process or use a different port
+
+### Getting Help
+
+If you're still having issues:
+
+1. **Check the logs**: Look for error messages in the terminal
+2. **Search existing issues**: Check [GitHub Issues](https://github.com/KobaltBlu/KotOR.js/issues)
+3. **Ask on Discord**: [OpenKotOR Discord Server](https://discord.gg/QxjqVAuN8T)
+4. **Create an issue**: Include:
+   - Your operating system and version
+   - Node.js and npm versions
+   - Error messages
+   - Steps to reproduce
+
+## Next Steps
+
+Once setup is complete:
+
+1. **Read the documentation**:
+   - [README.md](README.md) - Project overview
+   - [CONTRIBUTING.md](CONTRIBUTING.md) - Contribution guidelines
+   - [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md) - Project structure
+
+2. **Explore the codebase**:
+   - Start with `src/KotOR.ts` - Main entry point
+   - Check `src/GameInitializer.ts` - Game initialization
+   - Look at `src/module/Module.ts` - Module system
+
+3. **Run the application**:
+   - Use `npm run webpack:dev-watch` and `npm start`
+   - Explore the launcher, game, and forge applications
+
+4. **Start contributing**:
+   - Find a [good first issue](https://github.com/KobaltBlu/KotOR.js/labels/good%20first%20issue)
+   - Read [CONTRIBUTING.md](CONTRIBUTING.md)
+   - Make your first contribution!
+
+## Additional Resources
+
+- **Node.js Documentation**: [nodejs.org/docs](https://nodejs.org/docs/)
+- **TypeScript Handbook**: [typescriptlang.org/docs](https://www.typescriptlang.org/docs/)
+- **React Documentation**: [react.dev](https://react.dev/)
+- **THREE.js Documentation**: [threejs.org/docs](https://threejs.org/docs/)
+- **Electron Documentation**: [electronjs.org/docs](https://www.electronjs.org/docs/)
+
+---
+
+**Happy coding!** 🚀
diff --git a/bin/cli.js b/bin/cli.js
new file mode 100644
index 000000000..dc89e1b3c
--- /dev/null
+++ b/bin/cli.js
@@ -0,0 +1,76 @@
+#!/usr/bin/env node
+"use strict";
+
+/**
+ * KotOR.js CLI – run npm scripts from package root.
+ * Enables: npx kotor-js <script> and npx github:user/KotOR.js <script>
+ */
+
+const path = require("path");
+const fs = require("fs");
+const { spawnSync } = require("child_process");
+
+function findPackageRoot(startDir) {
+  let dir = path.resolve(startDir);
+  const root = path.parse(dir).root;
+  while (dir !== root) {
+    const pkgPath = path.join(dir, "package.json");
+    if (fs.existsSync(pkgPath)) return dir;
+    dir = path.dirname(dir);
+  }
+  return null;
+}
+
+function main() {
+  const packageRoot = findPackageRoot(__dirname);
+  if (!packageRoot) {
+    console.error("kotor-js: could not find package root (no package.json).");
+    process.exit(1);
+  }
+
+  const args = process.argv.slice(2);
+  const isHelp = args.length === 0 || args[0] === "--help" || args[0] === "-h";
+
+  if (isHelp) {
+    let pkg;
+    try {
+      pkg = JSON.parse(fs.readFileSync(path.join(packageRoot, "package.json"), "utf8"));
+    } catch {
+      console.error("kotor-js: could not read package.json.");
+      process.exit(1);
+    }
+    const scripts = pkg.scripts || {};
+    const names = Object.keys(scripts).sort();
+    console.log("Usage: npx kotor-js <script> [-- <script-args>]");
+    console.log("       npx -y -p <pkg> kotor-js <script>   (from GitHub: use -p and explicit command)");
+    console.log("");
+    console.log("Scripts:");
+    for (const name of names) {
+      console.log("  " + name);
+    }
+    console.log("");
+    console.log("Examples (from npm, if published):");
+    console.log("  npx -y kotor-js start:electron");
+    console.log("  npx -y kotor-js test -- --watch");
+    console.log("");
+    console.log("Examples (from GitHub; -p is required, first run can take several minutes):");
+    console.log("  npx -y -p git+https://github.com/KobaltBlu/KotOR.js.git kotor-js start:electron");
+    console.log("  npx -y -p github:KobaltBlu/KotOR.js kotor-js start:electron");
+    return;
+  }
+
+  const scriptName = args[0];
+  const extraArgs = args.slice(1);
+  const npmArgs = ["run", scriptName];
+  if (extraArgs.length > 0) npmArgs.push("--", ...extraArgs);
+
+  const result = spawnSync("npm", npmArgs, {
+    cwd: packageRoot,
+    stdio: "inherit",
+    shell: true,
+  });
+
+  process.exit(result.status ?? result.signal ? 128 + result.signal : 0);
+}
+
+main();
diff --git a/jest.config.js b/jest.config.js
index e1c24902c..3d26c2903 100644
--- a/jest.config.js
+++ b/jest.config.js
@@ -3,7 +3,12 @@ module.exports = {
   preset: 'ts-jest',
   testEnvironment: 'node',
   transform: {
-    "^.+.ts?$": ["ts-jest",{}],
+    '^.+\\.(ts|tsx)$': [
+      'ts-jest',
+      {
+        tsconfig: 'tsconfig.jest.json',
+      },
+    ],
   },
   testMatch: ['**/*.test.ts'],
   coverageDirectory: './coverage',
diff --git a/package-lock.json b/package-lock.json
index bfa5b4b96..8cb2fbcb2 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -2057,6 +2057,258 @@
         "@parcel/watcher-win32-x64": "2.5.1"
       }
     },
+    "node_modules/@parcel/watcher-android-arm64": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-android-arm64/-/watcher-android-arm64-2.5.1.tgz",
+      "integrity": "sha512-KF8+j9nNbUN8vzOFDpRMsaKBHZ/mcjEjMToVMJOhTozkDonQFFrRcfdLWn6yWKCmJKmdVxSgHiYvTCef4/qcBA==",
+      "cpu": [
+        "arm64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "android"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-darwin-arm64": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-darwin-arm64/-/watcher-darwin-arm64-2.5.1.tgz",
+      "integrity": "sha512-eAzPv5osDmZyBhou8PoF4i6RQXAfeKL9tjb3QzYuccXFMQU0ruIc/POh30ePnaOyD1UXdlKguHBmsTs53tVoPw==",
+      "cpu": [
+        "arm64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-darwin-x64": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-darwin-x64/-/watcher-darwin-x64-2.5.1.tgz",
+      "integrity": "sha512-1ZXDthrnNmwv10A0/3AJNZ9JGlzrF82i3gNQcWOzd7nJ8aj+ILyW1MTxVk35Db0u91oD5Nlk9MBiujMlwmeXZg==",
+      "cpu": [
+        "x64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-freebsd-x64": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-freebsd-x64/-/watcher-freebsd-x64-2.5.1.tgz",
+      "integrity": "sha512-SI4eljM7Flp9yPuKi8W0ird8TI/JK6CSxju3NojVI6BjHsTyK7zxA9urjVjEKJ5MBYC+bLmMcbAWlZ+rFkLpJQ==",
+      "cpu": [
+        "x64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "freebsd"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-linux-arm-glibc": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-linux-arm-glibc/-/watcher-linux-arm-glibc-2.5.1.tgz",
+      "integrity": "sha512-RCdZlEyTs8geyBkkcnPWvtXLY44BCeZKmGYRtSgtwwnHR4dxfHRG3gR99XdMEdQ7KeiDdasJwwvNSF5jKtDwdA==",
+      "cpu": [
+        "arm"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-linux-arm-musl": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-linux-arm-musl/-/watcher-linux-arm-musl-2.5.1.tgz",
+      "integrity": "sha512-6E+m/Mm1t1yhB8X412stiKFG3XykmgdIOqhjWj+VL8oHkKABfu/gjFj8DvLrYVHSBNC+/u5PeNrujiSQ1zwd1Q==",
+      "cpu": [
+        "arm"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-linux-arm64-glibc": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-linux-arm64-glibc/-/watcher-linux-arm64-glibc-2.5.1.tgz",
+      "integrity": "sha512-LrGp+f02yU3BN9A+DGuY3v3bmnFUggAITBGriZHUREfNEzZh/GO06FF5u2kx8x+GBEUYfyTGamol4j3m9ANe8w==",
+      "cpu": [
+        "arm64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-linux-arm64-musl": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-linux-arm64-musl/-/watcher-linux-arm64-musl-2.5.1.tgz",
+      "integrity": "sha512-cFOjABi92pMYRXS7AcQv9/M1YuKRw8SZniCDw0ssQb/noPkRzA+HBDkwmyOJYp5wXcsTrhxO0zq1U11cK9jsFg==",
+      "cpu": [
+        "arm64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-linux-x64-glibc": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-linux-x64-glibc/-/watcher-linux-x64-glibc-2.5.1.tgz",
+      "integrity": "sha512-GcESn8NZySmfwlTsIur+49yDqSny2IhPeZfXunQi48DMugKeZ7uy1FX83pO0X22sHntJ4Ub+9k34XQCX+oHt2A==",
+      "cpu": [
+        "x64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-linux-x64-musl": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-linux-x64-musl/-/watcher-linux-x64-musl-2.5.1.tgz",
+      "integrity": "sha512-n0E2EQbatQ3bXhcH2D1XIAANAcTZkQICBPVaxMeaCVBtOpBZpWJuf7LwyWPSBDITb7In8mqQgJ7gH8CILCURXg==",
+      "cpu": [
+        "x64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-win32-arm64": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-win32-arm64/-/watcher-win32-arm64-2.5.1.tgz",
+      "integrity": "sha512-RFzklRvmc3PkjKjry3hLF9wD7ppR4AKcWNzH7kXR7GUe0Igb3Nz8fyPwtZCSquGrhU5HhUNDr/mKBqj7tqA2Vw==",
+      "cpu": [
+        "arm64"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
+    "node_modules/@parcel/watcher-win32-ia32": {
+      "version": "2.5.1",
+      "resolved": "https://registry.npmjs.org/@parcel/watcher-win32-ia32/-/watcher-win32-ia32-2.5.1.tgz",
+      "integrity": "sha512-c2KkcVN+NJmuA7CGlaGD1qJh1cLfDnQsHjE89E60vUEMlqduHGCdCLJCID5geFVM0dOtA3ZiIO8BoEQmzQVfpQ==",
+      "cpu": [
+        "ia32"
+      ],
+      "dev": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": ">= 10.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/parcel"
+      }
+    },
     "node_modules/@parcel/watcher-win32-x64": {
       "version": "2.5.1",
       "resolved": "https://registry.npmjs.org/@parcel/watcher-win32-x64/-/watcher-win32-x64-2.5.1.tgz",
@@ -3361,14 +3613,6 @@
         "url": "https://github.com/sponsors/jonschlinkert"
       }
     },
-    "node_modules/arg": {
-      "version": "4.1.3",
-      "resolved": "https://registry.npmjs.org/arg/-/arg-4.1.3.tgz",
-      "integrity": "sha512-58S9QDqG0Xx27YwPSt9fJxivjYl432YCwfDMfZ+71RAqUrZef7LrKQZ3LHLOwCS4FLNBplP533Zx895SeOCHvA==",
-      "license": "MIT",
-      "optional": true,
-      "peer": true
-    },
     "node_modules/argparse": {
       "version": "1.0.10",
       "resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz",
@@ -4290,14 +4534,6 @@
       "dev": true,
       "license": "MIT"
     },
-    "node_modules/create-require": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/create-require/-/create-require-1.1.1.tgz",
-      "integrity": "sha512-dcKFX3jn0MpIaXjisoRvexIJVEKzaq7z2rZKxf+MSr9TkdmHmsU4m2lcLojrj/FHl8mk5VxMmYA+ftRkP/3oKQ==",
-      "license": "MIT",
-      "optional": true,
-      "peer": true
-    },
     "node_modules/cross-env": {
       "version": "10.1.0",
       "resolved": "https://registry.npmjs.org/cross-env/-/cross-env-10.1.0.tgz",
@@ -4678,17 +4914,6 @@
       "license": "MIT",
       "optional": true
     },
-    "node_modules/diff": {
-      "version": "4.0.2",
-      "resolved": "https://registry.npmjs.org/diff/-/diff-4.0.2.tgz",
-      "integrity": "sha512-58lmxKSA4BNyLz+HHMUzlOEpg09FV+ev6ZMe3vJihgdxzgcwZ8VoEEPmALCZG9LmqfVoNMMKpttIYTVG6uDY7A==",
-      "license": "BSD-3-Clause",
-      "optional": true,
-      "peer": true,
-      "engines": {
-        "node": ">=0.3.1"
-      }
-    },
     "node_modules/doctrine": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/doctrine/-/doctrine-2.1.0.tgz",
@@ -11869,46 +12094,6 @@
         "node": ">= 12"
       }
     },
-    "node_modules/ts-node": {
-      "version": "9.1.1",
-      "resolved": "https://registry.npmjs.org/ts-node/-/ts-node-9.1.1.tgz",
-      "integrity": "sha512-hPlt7ZACERQGf03M253ytLY3dHbGNGrAq9qIHWUY9XHYl1z7wYngSr3OQ5xmui8o2AaxsONxIzjafLUiWBo1Fg==",
-      "license": "MIT",
-      "optional": true,
-      "peer": true,
-      "dependencies": {
-        "arg": "^4.1.0",
-        "create-require": "^1.1.0",
-        "diff": "^4.0.1",
-        "make-error": "^1.1.1",
-        "source-map-support": "^0.5.17",
-        "yn": "3.1.1"
-      },
-      "bin": {
-        "ts-node": "dist/bin.js",
-        "ts-node-script": "dist/bin-script.js",
-        "ts-node-transpile-only": "dist/bin-transpile.js",
-        "ts-script": "dist/bin-script-deprecated.js"
-      },
-      "engines": {
-        "node": ">=10.0.0"
-      },
-      "peerDependencies": {
-        "typescript": ">=2.7"
-      }
-    },
-    "node_modules/ts-node/node_modules/source-map-support": {
-      "version": "0.5.21",
-      "resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.21.tgz",
-      "integrity": "sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==",
-      "license": "MIT",
-      "optional": true,
-      "peer": true,
-      "dependencies": {
-        "buffer-from": "^1.0.0",
-        "source-map": "^0.6.0"
-      }
-    },
     "node_modules/tsc-watch": {
       "version": "7.2.0",
       "resolved": "https://registry.npmjs.org/tsc-watch/-/tsc-watch-7.2.0.tgz",
@@ -12938,17 +13123,6 @@
         "fd-slicer": "~1.1.0"
       }
     },
-    "node_modules/yn": {
-      "version": "3.1.1",
-      "resolved": "https://registry.npmjs.org/yn/-/yn-3.1.1.tgz",
-      "integrity": "sha512-Ux4ygGWsu2c7isFWe8Yu1YluJmqVhxqK2cLXNQA5AcC3QfbGNpM7fu0Y8b/z16pXLnFxZYvWhd3fhBY9DLmC6Q==",
-      "license": "MIT",
-      "optional": true,
-      "peer": true,
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/yocto-queue": {
       "version": "0.1.0",
       "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
diff --git a/package.json b/package.json
index d3519223c..abc7bac59 100644
--- a/package.json
+++ b/package.json
@@ -2,18 +2,50 @@
   "name": "kotor-js",
   "version": "2.0.0",
   "description": "KotOR JS - A remake of the Odyssey Game Engine that powered KotOR I & II",
+  "bin": {
+    "kotor-js": "./bin/cli.js",
+    "KotOR.js": "./bin/cli.js"
+  },
   "main": "dist/KotOR.js",
   "scripts": {
-    "start": "tsc --project tsconfig.electron.json && electron ./main",
-    "start-watch": "tsc-watch --project tsconfig.electron.json --onSuccess \"electron ./main\"",
-    "webpack:dev": "cross-env NODE_ENV=development webpack",
-    "webpack:dev-watch": "cross-env NODE_ENV=development webpack --watch",
-    "webpack:prod": "cross-env NODE_ENV=production webpack",
-    "electron:watch": "tsc-watch --project tsconfig.electron.json",
+    "build:electron": "tsc --project tsconfig.electron.json",
+    "build:web:prod": "cross-env NODE_ENV=production webpack",
+    "build:web": "cross-env NODE_ENV=development webpack",
+    "build": "npm run typecheck:build && npm run webpack:dev && npm run electron:compile",
+    "clean": "node -e \"require('fs').rmSync('dist', { recursive: true, force: true })\"",
+    "electron:build": "npm run typecheck:build && npm run webpack:prod && npm run electron:compile && electron-builder build --publish=never",
     "electron:compile": "tsc --project tsconfig.electron.json",
-    "electron:build": "npm run webpack:prod && electron:compile && electron-builder build --publish=never",
+    "electron:watch": "tsc-watch --project tsconfig.electron.json",
+    "rebuild": "npm run clean && npm run build",
+    "serve:electron:debug": "cross-env ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings tsc-watch --project tsconfig.electron.json --onSuccess \"electron ./main\"",
+    "serve:electron": "tsc-watch --project tsconfig.electron.json --onSuccess \"electron ./main\"",
+    "serve:web": "cross-env NODE_ENV=development webpack --watch",
+    "start-watch:debug": "cross-env ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings tsc-watch --project tsconfig.electron.json --onSuccess \"electron ./main\"",
+    "start-watch": "tsc-watch --project tsconfig.electron.json --onSuccess \"electron ./main\"",
+    "start:debug:full": "npm run build && cross-env ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings electron ./main",
+    "start:debug": "cross-env ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings npm run electron:compile && electron ./main",
+    "start:electron:debug:full": "npm run build && cross-env ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings electron ./main",
+    "start:electron:debug": "cross-env ELECTRON_ENABLE_LOGGING=1 NODE_OPTIONS=--trace-warnings npm run build:electron && electron ./main",
+    "start:electron:full": "npm run build && electron ./main",
+    "start:electron:inspect:full": "npm run build && electron --inspect=5858 ./main",
+    "start:electron:inspect": "npm run build:electron && electron --inspect=5858 ./main",
+    "start:electron": "npm run build:electron && electron ./main",
+    "start:full": "npm run build && electron ./main",
+    "start:inspect:full": "npm run build && electron --inspect=5858 ./main",
+    "start:inspect": "npm run electron:compile && electron --inspect=5858 ./main",
+    "start:web:full": "npm run build && echo Open dist/launcher/index.html or use a static server",
+    "start:web": "npm run build:web",
+    "start": "npm run electron:compile && electron ./main",
+    "test:verbose": "jest --verbose --no-cache ./src/tests",
+    "test:watch": "jest --watch ./src/tests",
+    "test": "jest --verbose --coverage --no-cache ./src/tests",
+    "typecheck": "tsc --project tsconfig.check.json --noEmit",
+    "typecheck:build": "tsc --project tsconfig.buildcheck.json --noEmit",
     "typedoc": "typedoc --out ./wiki ./src/KotOR.ts",
-    "test": "jest --verbose --coverage --no-cache ./src/tests"
+    "webpack:dev-watch": "cross-env NODE_ENV=development webpack --watch",
+    "webpack:dev:verbose": "cross-env NODE_ENV=development webpack --progress --stats verbose",
+    "webpack:dev": "cross-env NODE_ENV=development webpack",
+    "webpack:prod": "cross-env NODE_ENV=production webpack"
   },
   "author": "KobaltBlu",
   "license": "GPL-3.0",
diff --git a/tsconfig.buildcheck.json b/tsconfig.buildcheck.json
new file mode 100644
index 000000000..5842185fe
--- /dev/null
+++ b/tsconfig.buildcheck.json
@@ -0,0 +1,18 @@
+{
+  "extends": "./tsconfig.json",
+  "compilerOptions": {
+    "noEmit": true,
+    "strictNullChecks": false,
+    "types": ["node", "react", "react-dom", "@types/wicg-file-system-access", "user-agent-data-types", "offscreencanvas"]
+  },
+  "include": [
+    "src/**/*.ts",
+    "src/**/*.tsx",
+    "src/index.d.ts"
+  ],
+  "exclude": [
+    "node_modules",
+    "src/**/*.spec.ts",
+    "src/**/*.test.ts"
+  ]
+}
diff --git a/tsconfig.check.json b/tsconfig.check.json
new file mode 100644
index 000000000..8aa4f596e
--- /dev/null
+++ b/tsconfig.check.json
@@ -0,0 +1,18 @@
+{
+  "extends": "./tsconfig.json",
+  "compilerOptions": {
+    "noEmit": true,
+    "strictNullChecks": true,
+    "strictPropertyInitialization": false
+  },
+  "include": [
+    "src/**/*.ts",
+    "src/**/*.tsx",
+    "src/index.d.ts"
+  ],
+  "exclude": [
+    "node_modules",
+    "src/**/*.spec.ts",
+    "src/**/*.test.ts"
+  ]
+}
diff --git a/tsconfig.debugger.json b/tsconfig.debugger.json
index 11c6ee5fb..4235eda41 100644
--- a/tsconfig.debugger.json
+++ b/tsconfig.debugger.json
@@ -12,7 +12,7 @@
     "listFiles": false,
     "newLine": "LF",
     "noEmitOnError": true,
-    "strictNullChecks": false,
+    "strictNullChecks": true,
     "esModuleInterop": true,
     "skipLibCheck": true,
     "jsx": "react",
diff --git a/tsconfig.forge.json b/tsconfig.forge.json
index 1564f38ea..8baa44d9d 100644
--- a/tsconfig.forge.json
+++ b/tsconfig.forge.json
@@ -12,7 +12,7 @@
     "listFiles": false,
     "newLine": "LF",
     "noEmitOnError": true,
-    "strictNullChecks": false,
+    "strictNullChecks": true,
     "esModuleInterop": true,
     "skipLibCheck": true,
     "jsx": "react",
diff --git a/tsconfig.game.json b/tsconfig.game.json
index 5a910f93a..bc87b55a3 100644
--- a/tsconfig.game.json
+++ b/tsconfig.game.json
@@ -12,7 +12,7 @@
     "listFiles": false,
     "newLine": "LF",
     "noEmitOnError": true,
-    "strictNullChecks": false,
+    "strictNullChecks": true,
     "esModuleInterop": true,
     "skipLibCheck": true,
     "jsx": "react",
diff --git a/tsconfig.jest.json b/tsconfig.jest.json
new file mode 100644
index 000000000..a5efac12e
--- /dev/null
+++ b/tsconfig.jest.json
@@ -0,0 +1,29 @@
+{
+  "extends": "./tsconfig.json",
+  "compilerOptions": {
+    "noEmit": true,
+    "listFiles": false,
+    "jsx": "react",
+    "lib": [
+      "ESNext",
+      "dom"
+    ],
+    "types": [
+      "jest",
+      "node",
+      "@types/wicg-file-system-access",
+      "react",
+      "react-dom"
+    ]
+  },
+  "include": [
+    "src/tests/**/*.ts",
+    "src/apps/forge/helpers/**/*.ts",
+    "src/types/**/*.d.ts"
+  ],
+  "exclude": [
+    "node_modules",
+    "dist",
+    "release"
+  ]
+}
diff --git a/tsconfig.json b/tsconfig.json
index 852f04019..cb67e1f40 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -1,35 +1,44 @@
 {
   "compilerOptions": {
-    "moduleResolution": "node",
-    "target": "ESNext",
-    "module": "commonjs",
+    "allowJs": true,
     "declaration": false,
-    "noImplicitAny": true,
-    "removeComments": true,
+    "esModuleInterop": true,
     "experimentalDecorators": true,
-    "rootDir": ".",
-    "sourceMap": false,
+    "forceConsistentCasingInFileNames": true,
+    "jsx": "react",
+    "lib": [
+      "ESNext",
+      "dom",
+      "WebWorker"
+    ],
     "listFiles": true,
+    "module": "commonjs",
+    "moduleResolution": "node",
     "newLine": "LF",
     "noEmitOnError": true,
-    "strictNullChecks": false,
-    "esModuleInterop": true,
+    "noImplicitAny": true,
+    "outDir": "dist",
+    "removeComments": true,
+    "rootDir": ".",
     "skipLibCheck": true,
-    "allowJs": true,
-    "jsx": "react",
+    "sourceMap": false,
+    "strict": true,
+    "strictNullChecks": true,
+    "target": "ESNext",
     "types": [
       "@types/wicg-file-system-access",
       "user-agent-data-types",
       "node",
       "offscreencanvas",
-    ],
-    "lib": [
-      "ESNext",
-      "dom",
-      "WebWorker"
-    ],
-    "outDir": "dist",
+    ]
   },
-  "include": ["src/KotOR.ts", "src/types", "src/index.d.ts"],
-  "exclude": ["node_modules", "src/**/*.spec.ts"]
+  "exclude": [
+    "node_modules",
+    "src/**/*.spec.ts"
+  ],
+  "include": [
+    "src/KotOR.ts",
+    "src/types",
+    "src/index.d.ts"
+  ]
 }
\ No newline at end of file
diff --git a/tsconfig.launcher.json b/tsconfig.launcher.json
index 69db73e09..8b7d30354 100644
--- a/tsconfig.launcher.json
+++ b/tsconfig.launcher.json
@@ -12,7 +12,7 @@
     "listFiles": false,
     "newLine": "LF",
     "noEmitOnError": true,
-    "strictNullChecks": false,
+    "strictNullChecks": true,
     "esModuleInterop": true,
     "skipLibCheck": true,
     "jsx": "react",