rot.js VS cavernos

I can recommend rot.js. It offers both ascii and tileset support.

ROT.JS is a great library for making quick roguelikes and being in javascript means you can inspect the code. It has a number of map generation algorithms that you can mess around with to make interesting dungeons. https://ondras.github.io/rot.js/hp/

Lost Gardens of the Stone Heart is a browser game in traditional ASCII style, written in Javascript with the ROT.js and Tracery libraries. Or, at least, it will be when it reaches that magic critial mass of features and things actually happening and coalesces into something deserving the adjective.

- https://github.com/ondras/rot.js

The code is Open Source (like everything on CodePen) and anyone can modify the game to add more features. I just want to share it here so someone maybe will create something more fun with it. It uses ROT.js library. Note that the code was created quite some time ago and it's written in ES5 version of JavaScript.

I've been looking through the rot.js source, but it doesn't seem like it's currently possible to change the border color of a hex. Does anyone have experience with this?

Surprising. I've not used rot.js but I haven't found Canvas too bad for a real time game I'm working on (60 fps with 50x25 onscreen tilemap on my phone). ROT also has a WebGL backend available.

Thanks! I am using [rot.js](https://ondras.github.io/rot.js/hp/) map generation primitives and then layering stuff on top of that. I'll probably introduce an "outside" at some point with caves and forests you can explore.

I used ClojureScript and ROT.js to build it.

It sounds like you want something high scope. However, if you're asking what engine you should use then it sounds like you haven't got a prototype yet. Which would be faster to make in Javascript - there's libraries like ROT.jd to speed things up.

> It's written in JS which means that it's way smaller

There's nothing inherently large about WebAssembly, it's just that most practical wasm demos bundle emscripten (essentially an entire OS's standard library) or another very heavy layer in order to interop between the JS and WASM world.

As a bit of an experiment to see how small wasm could practically be with a minimal interop layer, I built this little project - the web demo is 90KB of JS + 70KB of wasm:

https://github.com/jordwest/cavernos

It was heavily inspired by this article which manages even smaller builds:

http://cliffle.com/blog/bare-metal-wasm/

There's a lot of room for improvement in terms of size optimisation in most projects, but it's still early days and for now most of them just bundle an OS compatibility layer to get things working quickly.

- Cavernos (https://github.com/jordwest/cavernos)