I’ve had to put down working on games for the past few days to wrap up finals and the spring semester at school. After grinding through all of that, I think I’m going to spend the day relaxing and digging into a game I haven’t played before. You know, have a little fun.
On the Portal Walker front, the breaking news that no one is yet interested in is the fact that I am starting to have concerns about porting the ElectroServer 5 Client API to Haxe, the main concern being that I have no idea what I am doing. However, I still have made a lot of progress in drudging through the grunt work of porting the meat of the code from AS3 to Haxe syntax. I really could use some help from someone who understands the more complex functions of both languages and can look over the code and figure out solutions to port some of the trickier elements. I’ve begun dabbling with this myself (such as replacing AS3 Dictionaries with Haxe Maps, which I’m not even sure works or is a good idea), but the time I’m investing in it is starting to surpass the threshold of confidence I have in myself, so I’ve started the process of trying to get some help.
If it turns out that there is simply no feasible way for me to get a HaxeFlixel client interfacing with an ES5 server on all desired target platforms, my current backup plan is to use ES5 for the server and create the client in Starling and AS3. The huge downside would be losing access to the Flixel framework and having to code a lot of the client game engine from scratch, as well as a higher potential to run into performance issues down the road due to Starling apps running on top of Adobe AIR instead of compiling natively for each platform as they would if I were able to build the client in Haxe. First world problems, man.