CommunityGames & simulation
Jev Doom Agent
lukaske/jev-doom-agent
A Doom agent driven by structured spatial state, running on Chocolate Doom via WebAssembly.
What problem does it solve?
A Doom agent driven by structured spatial state, running on Chocolate Doom via WebAssembly.
What public sources establish
Provides spatial state for agent decisions.
Displays game controls and decision telemetry.
Where it fits
Environment stateWorld state & legal actions
Jev decisionBehavior or action selection
Game codeExecute, log & replay
An editorial responsibility diagram, not a screenshot or live result from the project.
How to read and try it
Keep level rules, collisions and legal actions in the engine or simulator. Use the model only where judgment is needed, with logs and local fallbacks.
Check before integrating
01
Read the original source
Review the author notes or official docs for current status, dependencies and limitations.
02
Validate the smallest use case
Start with a small test before connecting a real workflow. This directory has not run the project for you.
03
Keep fallbacks and source records
Record the version, configuration and sources used so later updates remain traceable.
Sources & usage boundaries
A game experiment is not a general-purpose game AI or a Unity integration.
Author repository / READMEhttps://github.com/lukaske/jev-doom-agent
Source review: 2026-09-19 · Scope: public pages, author descriptions and resource positioning. No independent execution, performance retesting or security audit.