So I’m in bed, sick with the flu, trying to preoccupy myself with writing and thinking about what movies I might need to catch up on. I still haven’t seen the new star trek movies which is pretty old now but for me, it will be new.
Until last Friday things were busy as usual.
Another milestone for project DeathSpuds has been completed. This milestone saw the implementations of barriers and doors, the base code for flying enemy AI and persistant level data saving.
The barriers were designed to take into account resistance to certain types of damage. Such as being able to use a flamethrower on a barrier that melts, but is resistant to regular bullets. It’s nothing fancy, but it should pose some interesting challenges for the types of weapons that will be made available and the barriers responses to these weapons.
The Flying enemy is currently a basic implementation. Rather then using the Unity NavMesh, its using a Node Graph which is built as part of the AI System that was used with the Freeplay Demo and prior to us having pro licenses. The node graph is so we can control the navigation of an enemy through 3 dimensions of space which are basically waypoints which contain specific properties. Currently they fly around aimlessly trying to reach a particular node, and the buzz about in the space defined by those nodes. You can also shoot them down. Eventually it will support behaviours much like regular enemies such as attacking and patrolling.
The system for the persistant level data is pretty standard. It correctly writes out an XML data file which we can visually be read and checked of any issues in the writing process. The system is also designed and structured in a way to allow for multiple file formats to be supported, such as reading and writing to generic text or binary. This is something pretty important considering we don’t want people to be able to modify these files and cheat the game as it will also be apart of storing the level information for the player’s save game. And writing out to a file format such as binary is a good way to minimise that.
Since milestone completion, I’ve been mostly in bed, trying to get better and helping Elise with some T-shirt designs for a Minecraft competition. Occassionally doing some typing. And catching up on some games and movies that I’ve been meaning to watch for a long time.
I have also been working on a game and doing some re-work thanks to some recent trends which has been keeping me extremely busy. The jist is that releasing our flash framework as well as providing tutorials for it and other flash components is not what I would consider a viable thing to be doing right now.
In the last few month Adobe has been making a few changes with Flash that don’t necessarily align with the goals of some flash developers. Leaving some of them with a bitter taste in there mouth. Unity has also dropping support for there Flash Add-on which doesn’t signify good news.
The problem stems from the requirement of Stage3D originally being planned to enforce “royalty” payments of the runtime to developers who are also using another service known as Domain Memory, basically these two services together allow for improved performance of Stage3D, apparently. In terms of a business plan this is reasonable, but not when the means of enforcing such a plan is undeterminable. This plan was eventually cancelled in the end because there was a lot of speculation about how it could of possibly have been enforced, when these two services are free to use by themselves but not when together. The general sentiment from a lot of developers was that it’s not possible. The whole thing since then has Flash feeling unloved, and unsupported.
So I will be porting the code out of flash and into another language putting most of the grunt work into a perl script or even C# to handle the majority of the conversion. But sometime in the future, not right now. It’s unfortunate considering that flash has been a very useful language to use to develop a lot of our ideas and we will continue to use it, but it has become an uncertainty in what we would like to deliver in the future, or our grand plan.
But until time permits, I’ll been focusing more energy into developing Unity based games.
I was also sick a few weeks beforehand, not for very long or as exhausting as the current flu is but caused by something moderately humorous. It came about around the time of the live XBox One announcement, which I was watching. Lets just say I was less then pleased with what they were offering, considering where I’m from is Australia and the service they talked about meant nothing to me. Although some of the features I found genuinely interesting and would love to see how it panned out for the future of the device, the whole experience left me feeling literally ill. I ended up in bed with a fever that night, freezing cold, and with burning temperature (of rage!!). Coincidence? Possibly! I was down for a day and back to normal the next! Regardless, hopefully XBox One is not as bad as some of it all sounds, and Microsoft is putting a lot of work into it. So there’s no denying that the release of the XBox One will make for an interesting year. We’ll all see how it goes.
But that’s enough from me I guess, this is gotten to be quite long and I suppose this is what happens when I don’t update regularly. So I’ll leave here.
Hope everyone is looking after themselves!