I’m currently designing levels for the campaign/story mode of my tower defensish game Def. There are various approaches that tower defence (TD) or RTS games take in progressively introducing new tower types and enemy types. It’s not uncommon to have a kind of tech tree, or a store where new tower types can be unlocked. As the player progresses through levels and gains more money or experience points, a greater variety of towers become available. These open up new strategies which usually need to be exploited immediately to deal with new enemy types. Continue reading…
I just pushed a small update for Chomper Deluxe to the OUYA marketplace – it should go live soon. I’ve updated the input framework so that it should happily support wireless XBox, PS3, and several less common controllers. Minor bugfixes and performance improvements. Tweaked graphics. Added a donate button, where you can become a member of the SSoACS.
Arriving in Damascus is an on-rails first-person hypertext interactive fiction (ORFPHIF), made as my One Game A Month, and produced to help battle-test “uTwine”, a Twine for Unity implementation I’ve been working on.
I started out planning to make a Dear Esther parody, but as I went along, I discovered that (1) not surprisingly, it had already been done, and (2) I was finding it difficult to make light of the original, given the subject matter surrounding grief and loss. So, I went for some parallel universe ‘fanfic’ instead, and tried to capture some of the atmosphere, extending the story in another direction. Here are a bunch of things I learned along the way.
Unity Pro has a nice feature for baking and navigating via NavMeshes. In Unity Pro (4.x), a baked NavMesh is associated with a saved “Scene”. Most of the time, this is all well and good, but as others have discovered, sometimes this simplification / limitation poses a problem when you want to use LoadLevelAdditive or LoadLevelAdditiveAsync. The current NavMesh is always the one from the last scene that was loaded via LoadLevel or LoadLevelAsync. This poses a problem if you say, have a fast loading title screen (scene A) which then uses LoadLevelAdditiveAsync to load the main level (scene B) containing the guts of the game, including the baked NavMesh you want to use. The NavMesh in scene B won’t be loaded.
To solve this, I discovered a (hackish) workaround that involves associating a single baked NavMesh with two scenes, via editing the Scene file in text mode (TLDR; the NavMeshSettings section in .unity Scene files defines the NavMesh for that scene. It appears two scenes can point to the same NavMesh. Gentlemen, start your Vim’s & Emacsen !).
As is tradition, here is an occasional summary of “What Andrew is Playing(tm)”, consisting of nondescript single line reviews of zero depth, and the odd dive into an element of game design that interested me.