Alright, I’ll admit it, I haven’t updated my blog in far too long. Every time this happens, I feel like I need some epic post in order to make up for it, but Zorba told me to just update the damn thing anyway because there’s no excuse. I’m going to have to write multiple entries though, because there’s a lot to talk about. So here we are.
Anyway, to the point.
This year has already been big for multiboxers, with new multiboxable games that have come out out and even some older games going Free-to-Play. And multiboxers have confirmed with various MMORPG publishers this year that, as long as you’re not actually cheating while playing (like watching a program play for you — which is not something we multiboxers do), they are not going to ban you for playing the games this way. And World of Warcraft’s latest expansion Mists of Pandaria is looking more multiboxing-friendly to me than Cataclysm was.
But I haven’t had that much time recently, myself, to actually multibox. I’ve been holed up in the lab since the start of summer preparing for awesome things to come.
Among other projects, what I am most excited about working on right now is a new scripting engine to replace LavishScript. Currently, the parts of ISBoxer that actually operate while you play the game are developed in LavishScript, and therefore any development of those parts is restricted to the limitations of the LavishScript engine. Simply put, the in-game features of ISBoxer are not living up to their potential, and a new scripting engine is going to help take us there in many ways.
So before taking on any project like a scripting engine, it’s best to look for an existing alternative. A World of Warcraft player might say “HEY U NEEDZ SCRIPTING ENGINE? USE LUA, IT R THE BEST.” It’s certainly not bad, but having used a few different versions of it before, I’ve never been a huge fan of Lua’s syntax, nor the API I would be using to integrate it into my products. Eventually after doing plenty of research on scripting languages and APIs, licensing on the engines, considering how the features would apply through Inner Space, etc., I settled on developing a custom Virtual Machine (LavishScript 2.0), an Intermediate Language for the VM (LS2 IL), and a C# Compiler targeting LS2 IL. An early version of the VM is already integrated into Inner Space, and the C# compiler is already usable, is open source, and is moving forward seemingly by leaps and bounds thanks to Microsoft’s new “Roslyn” C# Compiler API!
That might not excite you now, but I expect these efforts will begin to bear fruit for multiboxers within the next couple of months. There are new features to be had.
I have other topics to cover as well, so keep an eye out for further updates!