Recipe for a failed game: The UI is very awkward, and does not line up well with mouse position. Sprinkle in a mere pinch of very limited starting resources. Stir rapidly with disasters and bad events almost every other turn.
I would not play this game again unless I was paid a lot of money to compensate for damages. At least reduce the frequency of bad events, and/or add in some good ones, and it might make for an amusing "killing time waiting for my conference call" game.
Yes, that is understood.. But hopefully, viewers (whether gamers or other developers) learn from such issues: Bugs (not just coding bugs, but logic bugs and such as well) to look out for; Planning and execution/implementation/interface issues; And other such mistakes and issues. Humans are a silly creature--They learn more from failure than from success.
I've been using this site to help my nephews learn to do more than just write program code, but to actually develop programs from initial concept through to a completed and "polished" program. It's too bad so little software here is "source available", as I can see a lot of potential for others to contribute issue fixes. (I do the same thing with my nephews and Github projects ...)
