5 ms·

To the author: you mention determination as one of the keys to success. Strongly agreed. If you want Flax to be successful, then stick with it and continue prov

by rsbrown 15y ago

To the author: you mention determination as one of the keys to success. Strongly agreed. If you want Flax to be successful, then stick with it and continue providing timely updates and support. Don't waste time worrying about whether each release is perfect. Just make sure that it is well-tested and reliable. For me, the biggest barrier when choosing which HTML5 game engine to use isn't so much "is the feature set perfect?" as it is, "will this thing still be around 6 months from now?"

hebejebelus 15y ago
Don't worry, that's exactly what we'll be doing. We've got a hard deadline of three weeks on each iteration, and a soft one of two weeks. After the soft deadline, we'll bugfix anything and remove non-working features. Hopefully this will keep us on track. Plus, when we put the progress bar in the header, we inadvertently gamified ourselves. Can't help but want to move it up. ;) Don't worry, we've made a pact that Flax.ie will be around for nine more years (ten years from when we started), so as long as the internet doesn't explode, we'll still be there. Thanks for the kind comment, it's appreciated.
- rsbrown 15y ago
  You're welcome. Great work so far, by the way. I really like the interface. A group of friends and I built a small HTML5 game prototype as part of a weekend hackathon a few months ago: http://diluvia.com http://diluvia.com We haven't worked on it since the spring, but I've been on the hunt for a good level editor since then. I will be interested in watching Flax develop.
  - hebejebelus 15y ago
    Well, we certainly hope to not disappoint! Diluvia looks awesome, great mechanic. Did you use node or websockets (or another method?) for the multiplayer aspect? Also, how did you do audio? I'm about to start working on Flax's audio section again (and rewrite it for the fourth time) and I'm still having trouble working around each of the browser-specific quirks. Did you use a flash fallback?
    - rsbrown 15y ago
      Yep, the full stack is all javascript running on node.js and websockets. We used SoundManager 2 for the audio: http://www.schillmania.com/projects/soundmanager2 http://www.schillmania.com/projects/soundmanager2

by rsbrown 15y ago

hebejebelus 15y ago

Don't worry, that's exactly what we'll be doing. We've got a hard deadline of three weeks on each iteration, and a soft one of two weeks. After the soft deadline, we'll bugfix anything and remove non-working features. Hopefully this will keep us on track. Plus, when we put the progress bar in the header, we inadvertently gamified ourselves. Can't help but want to move it up. ;) Don't worry, we've made a pact that Flax.ie will be around for nine more years (ten years from when we started), so as long as the internet doesn't explode, we'll still be there. Thanks for the kind comment, it's appreciated.

rsbrown 15y ago
You're welcome. Great work so far, by the way. I really like the interface. A group of friends and I built a small HTML5 game prototype as part of a weekend hackathon a few months ago: http://diluvia.com http://diluvia.com We haven't worked on it since the spring, but I've been on the hunt for a good level editor since then. I will be interested in watching Flax develop.
- hebejebelus 15y ago
  Well, we certainly hope to not disappoint! Diluvia looks awesome, great mechanic. Did you use node or websockets (or another method?) for the multiplayer aspect? Also, how did you do audio? I'm about to start working on Flax's audio section again (and rewrite it for the fourth time) and I'm still having trouble working around each of the browser-specific quirks. Did you use a flash fallback?
  - rsbrown 15y ago
    Yep, the full stack is all javascript running on node.js and websockets. We used SoundManager 2 for the audio: http://www.schillmania.com/projects/soundmanager2 http://www.schillmania.com/projects/soundmanager2