That's interesting, I like that everyone's code has to be public on github so if you get relentlessly destroyed you will at least have the chance to learn from how your opponent works.
I haven't yet tried the game itself, but the testing page mentioned on the frontpage seems rather important, and I think I'll hold off on trying the game until that is implemented.
Also I think it would be good to mention at what time (in which timezone) each day the code is pulled and the battles are run.
That the code is public could easily be manipulated, by commiting minified code instead. It doesn't make it non-copyable but mostly unreadable.
There is a small testing utility (called " test_your_hero_code.js") in the repository where you can make sure your hero is working as it should. But I'm also looking forward to a proper testing page where I can see the battle.
Interesting idea however, looking forward to having some free time to trying it out fully.
Thanks so much for the feedback. As you said, we do have a temporary testing utility for users while we finish up our testing site. Hope to see you soon!
That's really good feedback, thank you. We are currently running the game at close to midnight, Pacific Time.
As far as the testing site, that should be coming soon, but feel free to try out our temporary testing suite in the meantime. The hero-starter repo has all the instructions for that.
Thanks so much for your comments and feedback!
I haven't yet tried the game itself, but the testing page mentioned on the frontpage seems rather important, and I think I'll hold off on trying the game until that is implemented.
Also I think it would be good to mention at what time (in which timezone) each day the code is pulled and the battles are run.