Skip to main content

XBOX ONE Game Dev is supposed to be hard.

So I recently took the plunge and joined the Xbox One Creators Program with Microsoft. It turns out that it's supposed to be incredibly hard to build these little games we see all the time, and for the most part, it is. Not only do we have to deal with the fact that the XBOX One does not use the stripped down PowerPC architecture that the Xbox360's used to run on, we now have to contend with the fact that it's basically running Windows 10. I remember the good old days when win32 and GDI (Graphics Device Interface) were sufficient to get a decent game running on a Windows PC - especially if the game wasn't too resource intensive. Then came Direct(X/3D/2D/11/12) with all its COM (Component Object Model) Glory -> which, perhaps most asinine of all -> is still being used today. Getting into the creators program costs a little bit of money, and that's mostly to keep the chancers out and cover administration fees. After that you really only need to abide by the store policies and be able to write a little bit of code, then you're sorted. With the advent of Xbox One-Friendly game engines, it's easier than ever to build an app that runs on a Windows 10 PC as well as the beloved Xbox One. I remember the good old days where things needed to be rewritten and recompiled to be able to run on different platforms . .when developing for a console required the teams to purchase a Dev-Kit (Development Kit containing an unlocked piece of console hardware) in order to be able to write their code. I remember when the costs were prohibitively expensive, and a simple guy - like myself - would never be able to justify spending that kind of cash on a hobby. I remember when it took teams of people to build an idea, a game, a concept, a business with big-budget marketing, in order to break-even on the Xbox Live Marketplace. I remember when NDA's (Non-Disclosure Agreement) had to be signed so as not to divulge the inner workings of the console. I remember . .. . These days it's stupidly easy to publish an app to the Microsoft Store, and by extension the Xbox Live Marketplace -> Step 1) Sign up for the creators program (this requires a small sum of money) Step 2) Peruse the numerous tutorials and reference materials Microsoft makes available online. Step 3) Build your desired game Step 4) Publish to the store Those are literally the steps, and Step 3 is simplified vastly if you use the Unity Game Engine with the Xbox Live plugin -> this abstracts away all the tedium of setting up your project keys to be included in your application. All in all, one could go from 0 all the way to Step 4 in a little under a week if they were motivated and had lots of spare time. So, yeah . . . I think I've found something that was supposed to be hard, that's been made incredibly easy along the way.

Comments

Popular posts from this blog

A few thoughts on Game Development

For those of you who follow my blog, you'll notice that I talk about building games, but I never really release anything useful or fully playable. I'm more interested in studying the individual parts of game development, without really caring about building a game as a whole. Well, for the most part this is perfectly acceptable, as I'm not a game developer by trade, and my bread and butter comes from being a utility developer. I've defined utility developer as someone who codes a variety of things without specializing in any specific discipline. As a self-taught developer, it's been hard for me to pivot into a role where I'm classed as a game developer by trade. This is all good and well, but I still want to talk about game development as a whole - specifically how to get a game off the ground. If you've been following any blog about game development, or any programming course which walks you through the process, you've most likely heard of all the jar

Typescript is Hard

So, for a work-project, the language choice handed down by the Overlords-Of-Jobbing has been TypeScript. You see - where I work, we build websites, and we build the infrastructure to support those websites. We also build platforms to support the website-supporting-infrastructure . . . so we like to iterate quickly and be as agile as possible in our workflow. For the current clientele we're servicing it has been decided that TypeScript on the Babel toolchain would be the most productivity-boosting language we could use, and as a result I've had to learn this new-fangled language with all its idiosyncrasies. Now, TypeScript is awesome, it supports both static and dynamic typing, lambdas, the entirety of JavaScript and all the associated libraries and frameworks which come with JS. TypeScript is awesome. TypeScript: - will mend fences - paint your garage - spay your cat - neuter your dog - rent Clerks II on DVD - run you a nice hot bath after a long day But, the m

Letters to my wife in case I don't make it part 1

 My dearest wife, The world has been so cruel to us. First the world was hateful towards you in your youth, it hated me too in my teens. Next, the world took its sweet time keeping us apart for all those years. When we finally found each other, we were both already well spent from a lifetime of struggle. As if to add insult to injury, we've barely had the shortest decade together and now the world is ending. The world sits on the brink of war, while our beloved homeland sits on the brink of economic collapse and starvation. The sweet fragrance of the flowers of our youth has been replaced with masks as disease ravages our world. No more flowers will bloom when the last bee dies. Through all this, I've found you, and it's been fun. If the world takes me before I can say it: "I don't know what comes next, but I promise to find you in every lifetime. I'm so sorry that you might live this lifetime without me, I'll make it up to you in the next one, pinky swear.