WWX News Part 3 - The Slides

These are the slides from the Kha presentation at WWX2015. The comments are new but mostly similar to the talk (the actual talk will be on YouTube later this month).

Read this article

WWX News Part 2 - Networking

Writing networked multiplayer games is a tough task, even when using some of the bigger game engines (for example Unity really doesn’t provide much support for that at all unless you buy some additional third-party plugin). To make a game session robust in the face of potentially unreliable connections and even cheating the complete game should be able to run on a separate server which has final say about the game state. To avoid a game feeling sluggish because of a potentially large distance aka signal travel time to the server the complete game should be able to run on the client to enable proper client side prediction of the game state. So, let’s just implement the game twice? Probably not a good idea and therefore Kha can now automatically export a client and a server version of a game after a little bit of necessary metadata has been added.

Read this article

WWX News Part 1 - Export to Unity

I did a little talk at WWX 2015 which showed a bunch of new stuff. That talk will be on YouTube later this month, but meanwhile I’ll try to detail all the new features right here in a series of blog posts.

Read this article

Breaking News 5

The Kha repository has been restructured to minimize download sizes. Where possible submodules have been replaced with binary only repositories - of course all the corresponding source repositories are still easily accessible on Github and updates to the binary repositories will always mention the corresponding revision of the source archives in new commits. Your git client might get confused by this - when in doubt just redownload Kha.

Read this article

khamake & koremake

hake and kake have recently been replaced with khamake and koremake. Those are ports of the original tools to node.js so you’ll need to install that to use them from the command line. You don’t need to install node.js when you use Kit because that itself is based on node-webkit (which is now called NW.js) which basically includes node.js. The tools still support all the same options and Kha and Kore include shortcut scripts - a typical call is now node Kha/make or node Kore/make. The switch to node makes it easier to provide updates of the tools and in the long term will provide a deeper integration with Kit.

Read this article