Get it? It's a play on words of dungeon and engine... 😐
See it in action here!
Finally, the raycasting you've been waiting for!
An in-engine screenshot from version 0.3.3.
Did somebody say "lightweight, retro-themed, easy-to-understand, easier-to-learn, dungeon crawler engine"?
N-no?
Anyway, this is all of those things. First and foremost, it is a dungeon crawler game I am building in vanilla JS. That's right! No node, and no rendering libraries! Just good old fashioned JS and HTML Canvas. The entire engine is built from the ground up to maximize efficieny while running at a constant 60fps (on any mid-range computer hardware)
Being HTML you can easily export this to an NW.js desktop application, mobile app, or anything else that can run an HTML page.
There isn't official documentation yet, but everything is thoroughly commented and easy to read. The engine itself is relatively simple, and the game loop follows the common-
- User input.
- Game logic.
- Game rendering.
-game loop methodology. Every object in the game utilizes these three functions at their core, meaning implementing brand new functionality into the engine is easy.
-
Player with attacking, inventory, and health.
-
Modifiable UI with a built in minimap.
-
Efficient, complex spritesheet-based image rendering system.
- One for rendering static objects from a spritesheet. (faster than having thousands of images that have to be loaded in individually)
- The other, for rendering an animation, or animations from a spritestrip.
-
Tile based rooms with events and triggers.
-
A robust, but simple, object-focused collision system. (meaning each object can handle its own collisions differently, and handle what objects it will collide with)
-
(Potentially) infinite room generation using simplex noise and custom template-built rooms. (capped at a certain amount of rooms (default 25, but tested up to 500) but could theoretically go on forever, given enough memory...)
-
Multi-source RAYTRACED lighting system. (employs raytracing methods, does not require an RTX GPU)
-
Enemies with AI.
- Raycasting/tracing.
- A fully posable camera with smart rendering. (only renders what is on-screen)
- Fully customizable item/loot system.
- Fully customizable entity system.
Newest changes on top. Once a major version change is completed all of its sub-version changes are compiled under one heading.
- Added camera shaking.
- Gave enemies the ability to attack the player at intervals.
- Made animation functionality a global class for less repetative code.
- Fixed bug where some game objects would have their render code run while they were off-screen.
- Added raycasted lighting.
- Added multiple light sources.
- Added room generation.
- Changed room textures.
- Improved rendering efficiency.
- Added simple player-focused "lighting."
- Added enemies.
- Added perlin noise to improve room randomness.
- Removed projectiles.
- Began file layout and imported common canvas properties.
- Added a player object and rooms with tiles.
- Added a collision system.
- Added player animation control.
- Added textures.
- Added player animations.
- Added items.
- Added collisions.
- Added projectiles.
By building the crawler out as a full game, I am able to implement features that are useful for people building their own game in the engine. Here are just a few of the big things I plan on adding:
- More enemies.
- Different size/shape rooms.
- True 2.5d rendering.
- Levels with increasing difficulty.
- A boss room.
- Better collision system that is global-focused rather than object-focused and more efficient.
- Player dying/respawning.
- Sound effects.
- Move all spritesheets to new spritesheet loading system.
- Doom-like 3D rendering with raycasting.
- Chest room.
- More kinds of loot.
- Enemy drops.