about Do Rounds

so...what is this thing, anyway?

Do Rounds is a tool that I developed after a weekend of Tabletop Roleplaying with my friends. We were playing Dungeons & Dragons 5th Edition, and I was the Dungeon Master. I had put together an adventure that had several very large encounters between the players and monsters.

I found that I was spending great amounts of time managing the details of the combat using pen and paper. It was time-consuming and error-prone, and it raised my programmer hackles; why was I doing all of this on paper when I could easily envision a simple application that would handle all of the tedious parts for me?

Three days later, here it is. Simple, to-the-point, and functional. Just the way that I like things.

is this free?

Yes, it is 100% free from any obligation to the user.

what about privacy?

I'm glad that you asked. I purposefully built this application such that -- to the best of my knowledge -- it contains zero infringements on the privacy of those who use it. There are no logins. All of the user's data is stored in the browser, on their computer. There are no cookies of any kind. Nothing that you do here is tracked in any way. The server doesn't log IP addresses. The application makes no network connections other than to load its CSS and JS files.

There are no ads. I just don't care about making money off of this, and it costs me next to nothing to run.

is it open source?

It certainly is. Check out the repo on GitHub. It is UnLicensed. Fork it, make changes, host it yourself; it's all good as far as I am concerned.

does it use any external libraries?

Yes. It uses Spectre.css as well as Vue.js. Both, in my opinion, are excellent.

can it work while my computer is offline?

Yes! I am sometimes called upon to DM in locations that have poor or no network connectivity, so I have made it an installable Progressive Web App. The first time that you load it -- with a network connection -- it makes itself available for offline use.

will it work in a mobile browser?

I suppose that it will. There's nothing stopping it from doing so, but it would probably be a pretty bad experience. It might layout well enough on a tablet, but using it without a physical keyboard would be challenging.

how can i make suggestions for improvement or report bugs?

The best way is to raise an issue on github, but you could also send me an email: adam at crossland dot dev.