C.J. Kimberlin wrote:
There’s a couple timing issues that will occur on Chrome (and I believe on others as well) around death, especially during the escape section, all good things to learn.
For tools, this is what we used:
Source control: git using BitBucket to host our repot
IDE: IntelliJ IDEA
Art: Photoshop CC
Level Editing: Tiled
Sound Effects (post-comp): bfxr
Music (post-comp): autotracker.py
bfxr and autotracker.py are awesome!
Have you tried cgMusic? http://codeminion.com/blogs/maciek/2008/05/cgmusic-computers-create-music/
BTW, what’s the deal with IntelliJ IDEA? Is it free? I thought it was just for Java, does it have some sort of auto-complete features for JS?
I didn’t try to check for the code because I assumed you’d had compiled it wih closure or something like that. Right click save file it is!
Luis - wrote:
Sebastián, you have to finish the sprint in EXACTLY ten seconds! No more, no less.
Tools I’ve used:
* Otomata (for the music)
* Sublime Text
* Bash (one script to make a release version of the game)
* Google Closure compiler
You can see the whole development in the timelapse video: http://youtu.be/2Nchhh\_IwtQ>
As for sharing the code, I was thinking of maybe creating a github repo for it but haven’t decided yet if I will release it.
Suerte con el final!
Otomata is great, I discovered last year during my cellular-automata-obsession phase and just forgot all about it later ’\^
Y\ gracias,\ me\ fue\ para\ el\ ojete!\ ’\^