1163: The Engine

[Sorry I’ve been lax with the cartoons recently — been blogging late and when I’m tired so haven’t felt inclined to do many. They’ll be back soon.]

As I’ve noted a couple of times recently, I’ve been beavering away at the game I’m making with RPG Maker VX Ace and trying to do a little bit each day. It’s slow progress at the rate I’m going, but it is satisfying to see things coming together piece by piece.

One thing that always impresses me with toolsets like RPG Maker is how active the community is, and how willing they are to help each other out. There’s relatively little in the way of insular thinking, with people wanting to keep all their trade secrets to themselves — quite the opposite, in fact. No, the RPG Maker community is filled with people who create graphical, musical, audible and script…able resources for public consumption and are more than happy to share them with other aspiring developers out there in exchange for nothing more than a wee credit in the finished game.

It’s a marked contrast to the ridiculous secrecy in other parts of the games industry, which is infested with embargoes and other bullshit to control the flow of information. I think that’s quite interesting. While I get why it happens, I think it’s starting to lose its impact. I’ve mentioned before on a number of occasions how all the reviews for a particular game hitting simultaneously makes me not want to read any of them (and, more often than not, not want to play the actual game ever) but this also goes for carefully-timed announcements and the like. The trouble is that a lot of these announcements are for things that people are expecting. A new Assassin’s Creed — surprise! A new Call of Duty — HOLY SHIT. A new Grand Theft Auto screenshot — STOP THE PRESSES.

Even the mobile sector has ridiculous embargoes in place. This always strikes me as weird given the sheer volume of mobile apps and games that are released every day. Companies are lucky to get their product covered at all in most cases, and enforcing arbitrary restrictions on said coverage can only be counter-productive, surely.

But I don’t want to get on an embargo rant. I just thought the openness of the amateur development community was an interesting contrast to the OMG TOP SEKRIT nature of mainstream game development.

I guess it’s largely to do with the fact that the majority of people tinkering around with stuff like RPG Maker and its ilk are amateur/bedroom developers putting stuff together in their own time rather than as their job. There are exceptions, of course, but the fact that RPG Maker is so easy to get up and running encourages people to give it a shot a lot more than the rather daunting task of learning a programming language and/or how to use an engine like Unreal Engine 3. The fact that there’s a sense of joyous discovery and entering a strange new world of wondrous creativity helps encourage a pleasing sense of camaraderie — plus the people who develop the more well-known scripts and resource banks become mini-celebrities in their own right, which must be nice for them. It’s also something they can potentially put on their CVs, I guess — saying that you’re the person behind one of the most widely-used battle system Ruby scripts for RPG Maker VX Ace may not have quite the same clout as saying you designed Unreal Engine 3, but it must count for something.

I can’t say I’ve gotten overly involved with the RPG Maker community as a whole yet since keeping up with forums always seems like a whole lot of hassle, but I’m certainly very grateful for the hard work of artists like “Archeia” and “Scinaya” and scripters like “Yanfly”, who are helping my game come together one piece at a time. If and when it ever gets finished, they’ll certainly be getting some love from me.

1159: WAY More Than Seven Days

Back on Day 793, you may recall that I mentioned I was working on a game and that I was quite enthusiastic about it. Well, it stalled somewhat for various reasons — work, general lethargy, moving house, jury service, many other reasons that aren’t really excuses — but this week I’ve started working on it again, and it’s a good feeling.

To be honest, doing what I’m doing was partly spurred on by this painfully accurate article from The Onion. I figured that I’m in a relatively good position right now — financially secure, working in a job which is reasonably challenging at times but which leaves me with plenty of free time — so instead of sleeping until 10-11am (usually unintentionally) I should make use of some of that extra time. As such, I’ve been getting up a bit earlier and, well, making use of some of that extra time.

In the previous post I linked to, I talked about how much I enjoy the world-building aspect of creating a game. Today, I’ve been rediscovering the joy of populating those locales that I’ve created with people. Specifically, the stuff I’ve been working on over the last couple of days has been the first appearance of the story’s main characters, so it’s been an absolute pleasure to see these characters I’ve had in my head (and a Google document) finally appear on screen and act the way I’ve told them to.

I’m going to do that annoying developer thing and not talk in specifics about the project because I’d like some aspects of it to remain a surprise, but I will say a few things about what I’ve achieved so far.

Thus far I’ve got a controllable protagonist and an interactive introduction sequence that introduces her, the setting and the context of the story. I’ve got some sequences where the player is able to make choices and subtly change some of the things that occur next. I’ve laid a few “hooks” for future interactions between the protagonist and other characters, and I’ve put together the story up until the point where the protagonist meets up with the other main characters. And, as I type this, I’ve composed the initial conversations between the protagonist and the other characters — including, again, a few events that change a little bit according to choices that have been made.

I’m deliberately keeping things relatively unambitious with this project, as I would very much like to actually finish it at some point. It’s a concept that I really like and would very much like to carry through to completion, so I’m keen to try and devote some time to it. One thing that was stopping me was a lack of certain art assets that I needed to progress, but now I’ve found those (or at least got some solid placeholders put in) I have, as far as I can make out, everything I need to pick up this project and run with it, motivation and free time permitting. Aside from the art assets I was lacking, most of the other stuff I’m using is either RPG Maker’s built-in content or publicly-available/royalty-free stuff. The somewhat “generic” nature of using built-in and publicly-available assets is entirely deliberate — if and when it’s finished you’ll hopefully see why I chose to go that route. It wasn’t just laziness and/or a desire to get up and running without having to worry about creating custom content — though being able to work with pre-made character sprites and the like certainly makes working on this a bit easier.

I’ll leave it at that for now, and if I make any significant progress that I’m happy to share in the near future, I may drop in a few screenshots here and there. Suffice to say that for the moment, I’m happy with the way things are going and hopefully I’ll have something more to share soon.

1136: Thoughts on RPG Maker

Page_1I read this piece by Robert Boyd of Zeboyd Games earlier. Now, I normally agree with Mr. Werezompire on a lot of things, but I take issue with a few things he says about RPG Maker in this article, which was posted shortly after the latest version RPG Maker VX Ace hit the Steam store a while back.

Boyd is quite right to note that this is the first time a piece of software such as RPG Maker has hit a mainstream digital download storefront for PC — past iterations of the software were sold directly by the publisher via a rather cumbersome e-commerce solution, so to get it on Steam is a big step forward in both accessibility and visibility. Boyd is also right to note that lowering the barrier of entry to creating games through tools such as RPG Maker also encourages everyone to want to have a go — and that this can result in a glut of “incomplete, buggy, generic, or downright awful games”. (It also results in people who are otherwise unable to get their heads around programming becoming empowered to realise their own digital dreams and creativity.)

What I take a certain degree of umbrage to is his assertion that it is a “general RPG maker” and thus ill-suited to producing anything more than the most generic JRPG possible. While it is true that the default art assets and music provided with the game are aimed at people who want to get a fairly generic JRPG up and running quickly, the very nature of the software is that it is completely customisable depending on how much “individuality” you want to give your project. You can have something fairly convincing up and running in a matter of minutes using the default assets… but with a bit of time and artistic talent (or at least creativity), you can completely revamp the default “look” to anything you please. Not only that, but by using its built-in Ruby-based scripting language, you can completely overhaul the way the game works — battle system, menus, method of moving around the game world, anything can be modified or added if you know what you’re doing. And even if you don’t, there’s a lively and active community out there that has put together plenty of free scripts for anyone to make use of.

This isn’t “trying to modify RPG Maker to do things it wasn’t really intended to do,” as Boyd asserts. This is, in fact, using RPG Maker in the manner in which it was intended for power users — and it also aptly demonstrates one of the most admirable things about the application: the fact that it is simple and accessible enough for beginners to use, yet powerful and flexible enough for more advanced users to take complete control of. You only have to look at examples like To The Moon and Cherry Tree High Comedy Club, both of which were created in RPG Maker XP (two versions previous to the current edition) to see what is possible — and to be fair to Boyd, he does at least mention these titles in his post.

Boyd makes some fair points in the article, but what I don’t like much is the underlying tone that “if you’re using RPG Maker rather than programming it yourself, you’re doing it wrong.” While it is undoubtedly more satisfying to program your own engine from scratch and see a complete game come together from literally nothing, not everyone has the time, ability and/or C#-speaking friends to be able to do that. Plus if there’s a perfectly good tool already out there to realise what you want to do… why shouldn’t you use it?

1101: Just Finish the Damn Thing

Page_1I’ve lost count of the number of “make my own game” projects I’ve started and abandoned over the years. I’ve started a new one recently which, theoretically, should be relatively straightforward to finish, so I will keep you all updated on its progress occasionally via this blog.

I’m no programmer, so I tend to gravitate towards solutions that allow you to flex your creative muscles and create interactive entertainment without having to, well, code anything. My weapon of choice for the last few attempts has been the excellent RPG Maker VX Ace, which is an immensely powerful tool capable of doing some really great things while at the same time allowing pretty much anyone to churn out a fairly generic top-down JRPG without too much difficulty.

It’s the “capable of doing some really great things” part that I often find myself struggling with. Y’see, the trouble with being presented with a wealth of possibilities is choosing which ones you want to pursue and which ones you want to ignore. The temptation is to incorporate as many of them as possible in an attempt to make something as awesome as possible, but inevitably if you do that — particularly if you’re working alone — you’ll hit a brick wall where something doesn’t quite work properly with something else, get disheartened and probably give up.

I’m talking vaguely. Let me give some specific examples. The new game I’ve started making as a means of proving I can take a project through from start to finish is simply an adaptation of the quests from MB/Games Workshop’s classic board game Hero Quest. Given that the structure and storyline of the Hero Quest board game is very much a generic sort of dungeon crawler, this shouldn’t be too difficult once I’ve done what I always initially think of as “the annoying bit” — setting up the characters, statistics, skills and whatnot, and finding some appropriate graphics for their sprites. (I call it “the annoying bit” but if I sit down and get on with it, I actually find this part quite fun after a while.)

Anyway, I’m about halfway done with “the annoying bit” — its initial stages, anyway — and already I’m finding myself torn in several directions. Do I stick with RPG Maker’s rather generic first-person battle interface? It doesn’t evoke the feel of Hero Quest that much, but then trying to adapt a board game and sticking too religiously to its rules can often ruin the “computer gaminess” of it. All right then, I thought, I’ll stick with this battle system, but I’ll tweak it so things like damage formulae are a little closer to rolling the dice in the game. Except when I thought I’d done that, I discovered that my ineptitude with composing damage formulae to accurately simulate dice rolls created a number of monsters that were literally impossible to hurt. Not good. I replaced the formula with its original one, which deals with much higher numbers than your average tabletop game. Will that ruin the atmosphere? Is “Rogar does 96 damage” somehow less powerful than “Rogar does 4 damage”? Probably not. That’s a stupid thing to think.

I’m probably overthinking it, I know, and should just get on with it. What I think I really need to do is just make the game with the default systems, and then tweak and fine-tune afterwards. Difficulty balancing and that sort of thing is an important part of testing, so I’ll leave that until there’s actually a game there to test — there’s no point getting hung up on problems that don’t actually exist yet.

So that’s the plan. Over the next few days I will be taking some time to plug in Hero Quest’s various spells and items into the game in a format that will work within RPG Maker’s style of play, then I’ll put the game itself together. Then I’ll show it to some select friends — this project probably won’t get a wide release, unless it actually ends up being surprisingly good — and then, flush with satisfaction at having actually carried something through to completion for once, I can embark on something a little more ambitious.

One step at a time.

#oneaday Day 793: It Takes More Than Seven Days to Build a World

20120322-012449.jpg

I’m making a game. This is not the first time I have said these words, nor will it be the last time, but I have a good feeling about this one. A vision. Only one past amateur development project I worked on (known as Pie-Eater’s Destiny) was ever completed (twice if you count the subsequent “Gold Edition” remake) and a third (The Adventures of Dave Thunder) was going extremely well but then unfortunately lost when an old computer died without warning. (Note to self: BACK THE FUCK UP) This one, though, feels like an idea that has legs, and I’m looking forward to bringing it to life, to mix metaphors for a moment.

No, you won’t be getting any details on what this project is just yet save for the fact that I’m using it as a means of trying out the latest version of Enterbrain’s excellent RPG Maker software, RPG Maker VX Ace. I’ve used several iterations of this package over the years and each has its own quirks and foibles. Previous version RPG Maker VX turned out to be a bit of a misstep which seemingly stripped out features rather than adding them, but from my limited experience so far, VX Ace seems to be an excellent piece of software with plenty of flexibility.

One of my favourite parts of creating a game — or indeed any story, since I typically have aspirations to create narrative-focused games, even if I never finish them — is creating the world and the characters who populate it. When building a map in RPG Maker, I’ll find myself visualising its context in the world — in the case of a village or town, I’ll think to myself “right, this person lives here, this person runs this shop, follow this path and you’ll get to…” and so on. In the case of a dungeon I’ll resist the temptation to use the random map generator and instead design a dungeon which makes some degree of contextual sense, even if it may descend into bizarreness at times. (The lava flow in the opening “wine cellar” dungeon at the beginning of The Adventures of Dave Thunder was a particular highlight, which our hero lampshaded quite nicely at the time he came across it for the first time, as I recall.)

I’ve always been this way with level construction. The earliest instance I can remember was Wolfenstein 3D, whose map editor gave me many, many hours of enjoyment and, thanks to CompuServe, even netted me $200 when ten of my levels were included in the official Apogee “Super Upgrades” expansion pack for the game. When building my selection of maze-like levels for id’s Nazi-bashing shooter, I enjoyed thinking of the “real” context for these rooms and tunnels. As such, I ended up with some memorable “setpiece” confrontations (or as close as you could get to a “setpiece” in Wolf3D’s limited engine, anyway) — the one that sticks in my mind most is the one where you’ve crept through some moss-filled corridors in search of a Nazi secret base and open a door only to discover that a briefing is apparently in progress. One of the “officer” enemies was standing at the front of the room next to a “map” texture, and the rest of the room was full of the standard trooper soldiers all facing him. (I wasn’t a monster for game balancing; I provided the player with a chaingun and plenty of ammo before sending them in to mow down this little gathering. Hey, I was a teenager. Subtlety wasn’t in my vocabulary.)

The point is, I found myself thinking carefully about every block I put down, every object on the map. Everything had a purpose, a place, a story behind it. I enjoyed visualising that world in my mind and then bringing it to life on my computer screen. It was inordinately satisfying to be able to hoon around a world of my own creation and think this came from my BRAIN. I feel the same way every time I create a new map in RPG Maker, every time I make a track in TrackMania, every time I build something in Minecraft. And if I had any clue whatsoever how 3D level editors worked (I’ve tried and failed numerous times) I have no doubt I’d feel the same way there too.

As you may have gathered, today has been about world-building. I’ve only created a tiny, tiny piece of what will eventually become this game’s world, but already it’s bringing those old feelings back. Hopefully they’ll provide the motivation to take me through to actually finishing a game project for once.