Global Game Jam 2015 - Mahou Shoujo Idol Strike!

It's that time of the year again! This was my fifth GGJ in as many years. Although I have gotten lazier when it comes to other jams organized by our game dev club, I have at least consistently participated in the biggest and baddest. Results may have varied... Anyway. Let's get into this. This is divided into a few sections - the first one is a bit more self-reflective, and it's about game ideas in a jam environment. The rest are about this year's project - which I'm sure you are dying to read about after reading that title.

1. About ideas

Let me just start by reminding that this section is kinda self-reflective and massively opinionated. So keep in mind that the most important thing when it comes to game ideas at jams is to do whatever the fuck you want - you are there to have fun after all. However, I'll be a bit more philosophical. Game jams are learning experiences and to that end, you may have some kind of a learning goal. Maybe it's to become better at your chosen profession, or maybe it's to try something new. I'm a decent programmer, but when I go to jams, I go there to work on something that has a fresh design. Therefore it is incredibly difficult for me to understand why anyone would want to spend their weekend making an underdeveloped version of a game mechanic that has already been developed by actual studios or indie developers. I do realize of course that it may be an interesting technical challenge just to see if you can get it done. Likewise if it's your first jam, simply getting any game done at all can be exhilarating.

It may be a pessimistic to way to look at things, but really, after too many jams, I seriously don't expect a jam game to be good. Like, at all. If your goal is to make a great game in 30 hours, prepare for a lot of failed jams. For me, personally, the measure of success is whether I got to try out something different or not. Probably this is why I have worked on my own idea in every jam so far - it's usually some mechanic that simply intrigues me too much. That, and a lot of the ideas of others have generally failed to inspire me. Again, this doesn't mean they are bad (indeed, the outcomes have often been more fun to play than mine) - I just feel like their owners have different goals for the project than I have. That, or I don't really see the game from the pitch. I think I actually found a way to work on the latter this year. Normally I would just think about some ideas by myself, or even leave the entire site to get some food or whatever.

This year, I was originally supposed to lead an "idea hotspot" - kind of a brainstorming table. We kinda failed at organization tho so we ended up not having them. Instead I just rotated around, asking people to throw their ideas at me and gave them some additional questions to chew on. I found this a nice approach actually. It gave me more insight into what others were thinking, and also may have helped them get a bit better grasp of their concepts. So this year there actually were a few other projects I might have joined. I'll have to admit, I kinda cheated this year. Literally three hours before the jam I was struck by an obnoxiously sticky game idea and I was unable to get rid of it. It prevented me from coming up with any new ideas of my own during the brainstorming time. I guess talking constantly about other people's ideas also kind of hindered my own thought process. So, anyway, after a lot of consideration I did pitch that idea... I felt a little guilty about it, but at least it was an idea I got on the first jamming day. Even if it was before the event started.

There was another reason too. Let me sidetrack a bit to say that the theme this year was absolutely fucking horrible. "What do we do now?" is a non-theme if I ever saw one. Either you come up with some incredibly bonkers artsy crap (not that I mind, I like those), or, well, you can pretty much encompass every single game ever made within this theme with very little mental gymnastics. The games made at our site this year didn't really connect in any way. It was just literally a bunch of random games - not take anything away of course, some of them very really good. Anyway, I wanted to bring this up because - like every single idea in the universe - my sticky idea from a few hours ago actually fit this non-theme. It even included the plural "we" in form of four characters. It still felt a bit stupid to fit an idea into a theme, not the other way around. So yeah, I decided to just throw it out there. And for the record my pitch was effing horrible.

I generally fail to attract workers to my cause because my games are described through their mechanics. I guess that's a bit unattractive, and they don't sound all that wild on paper. It's actually quite hard to see an abstract mechanic if it's being described to you - you can try this by reading a board game rulebook without access to any game components. This time my idea was inspired by two sources that typically get reactions one way or another: Asian pop music girl groups and the "magic girl" manga/anime trope. So even though I did a terrible job with my rambling pitch, I got the interest of one artist and one sound guy (who, curiously enough, hated j/kpop). Coincidentally that was just what I needed, so once again I ended up developing my own idea but this time with a team. So, just a casual takeaway: even though I mostly care about mechanics, I shouldn't rely so much on appealing to everyone else's inner designer. Instead, I should work more on sticking a crazy theme on top of my mechanical idea.

2. The game

I got the idea entirely from listening to kpop. More precisely, I was listening to Kara at the time and my tired mind wandered back to some recollections of their music videos. Suddenly I found myself wanting to make a JRPG battle system where all characters would move as a group, abiding to a dance choreography. In my mind it was more like a tactical RPG, even though the pop music connection might make most people think rhythm game. However, for me the core concept was careful selection of dance move patterns for the group as a whole. I also played around with ideas about having kpop-inspired roles for the characters (leader, lead singer, lead dancer etc.)  and the fact that the singer alternates frequently. Again, as my mind was already racing towards an RPG, I needed some connection between that and kpop. Probably as an indirect result of exposing my mind to too much Persona 4, it went straight towards "witches who use pop performances to fight evil" - there's probably a legion of animes about that already.

Since it was to be made into a game jam concept, some chopping down had to be involved. I kept the essential parts: there would be a group of characters and they would move in unison; each turn the player would choose from a handful of available patterns. The girls would need to move over specific tiles to activate their magical powers - this was intended to form the puzzle element of the game. Ghosts were added to the concept too. In the first iteration, the concept was like this: the girls would try to avoid ghosts while picking up power-ups; after doing so, they can cast magic to banish nearby ghosts. The interactions were quite simple, which made the basic game code very quick to write - a boon if you want to work on complicated mechanics that need a lot of rethinking. Most of the design complexity came from juggling two things: what happens on the board, and what moves the player has available at each moment. A bit of a rematch with problems I had when working on Pulselight Steampunk.

For once I even came up with a relatively straightforward way to make a tutorial: the first set of actions was a preset, and the player would see the key interactions by performing them in the given order. So at least in theory you could just tell players to press 1, 2 and 3 in succession and watch what happens. In practice the game is a bit harder to understand because the player has to follow four different characters at the same time. That in itself is fine, and gives the game a healthy dose of cognitive challenge. It became a bit problematic because for most of the development time the game felt insanely random. Only four actions were available to the player at a time, while there were like 40 actions total. The chances of having only useless (or worse) actions was staggeringly high. It didn't help that everything spawned on the board in random locations. Often, after just a couple of moves, the player was stuck with no way out.

Figuring out solutions for this problem became the essence of my game jam this year. I quickly changed some of the interactions; primarily, the girls were now able to defeat ghosts by running into them in addition to casting spells, and the ghosts could only spawn at the borders. This called for a new lose condition, and I ended up with "defend the center". So the ghosts would try to conquer the center of the board. I also fiddled around with how moves were offered to the player. I divided them into a few different categories and then made the game rotate between categories, basically guaranteeing different kinds of actions regularly. The end result feels mostly like a game where the player can actually control stuff. Still, the feeling of getting screwed over by the game is too frequent. I'll outline some next level ideas to improve the game in the next section. Before that, just a few words about its development.

Our team of three people worked quite well. Which, of course, is quite simple to do when everyone has a clearly specified set of tasks. The game's core was also really fast and easy to implement - it was pretty much done in like four hours. This is something that I highly prefer because it leaves a lot of time for fiddling around with design concepts. I also had time to code all kinds of luxury functions like support for animated visual effects. We were initially going to include a tilted perspective instead of a straight top-down approach, but improving the design took priority in the end. That, and one arcane bug that I managed to include in the code. Despite locating and fixing two different instances it, it's still present somewhere in the code. As usual I only have myself to blame for that. It's just one of those "what could possibly go wrong" things when writing game jam code.

I have found CraftyJS to be an amazing library for jam development - if you have learned it beforehand that is. There are two reasons for this: its component-entity model, and its event model. Crafty keeps track of all created game objects, and allows the developer to query them based on their components. Which means there is never a need to keep track of references, because you can always fetch them from the core object. I hate passing references so much in object-oriented programming. Passing a new reference down a few function calls already requires modifying code all over the place. Using events handlers over method calls has the same advantage. You just register a handler, and then can trigger the event from wherever you want instead of - once again - messing with annoying shit like references. Overall, not giving a damn about references speeds up development and makes it generally more relaxed.

I do think there is a downside to sticking with CraftyJS though. It only does 2D, which is a bit of a hindrance these days. Not that I'm particularly interested in making 3D games, but I should at least be able to do so just in case. Of course another problem with the library is its horrible documentation, which makes it hard to learn - definitely not ideal if you work with other programmers. So yeah, one day I should really learn how to use Unity3D.

3. Idol Strike! Next!

After the jam I thought of some ideas to make the game feel less random. Having too many random things in jam games is one of my personal faults. It's just really tempting to generate stuff randomly because actually designing levels takes a lot of time and it's not exactly as exciting as creating new game mechanics. However, I don't really see a way to make this year's game better without seriously chopping down on the randomness. Furthermore, if it were to find its way into its original role - to become a battle system for an RPG - it needs to incorporate way more customization options for the player. First of all, instead of being an endless score attack, the game needs to have clearly defined levels with specific challenges. Moreover, things like power-ups should be in fixed locations to incorporate any sort of actual planning into playing the game. Probably the same should be done to enemy spawns.

Something definitely needs to be done about randomizing available actions too. I want to stick with the idea of dance routines on this one. Instead of offering random patterns, there would be four different dance routines, each with its own fixed sequence of moves. Each turn, the player would choose one dance routine to follow, and could then choose to follow another on the next turn. The key here is that there would be a way for the player to see ahead at least a few moves or the entire routine (which could actually be just four moves actually, and then loop). To encourage further planning ahead, there could be some bonus for sticking with one dance routine for an extended period. Overall the key to making this game better is to a) provide the player more reasons to try to move to specific parts of the board; b) provide the player better means to get the girls to go where they want them to.

This way would eventually turn it into a puzzle game where the player would try to complete levels. Once the basic mechanics are neatly fixed, the concept can easily be expanded. More types of enemies are a no-brainer. Likewise, there could be more than one spell available in the game. For instance, there could be other banishment patterns than just the present "surrounding tiles" approach. After that, it's not a huge leap to make the girls individual by giving them different advantages. Thinking about extensions too much is generally detrimental though, so we might as well stop here. This section was just a short demonstration how exploring a game mechanic in a game jam game can lead to further discoveries and may, in the end, be a more valuable result than a more complete, more conventional game would have been. Contrast this to my "easiest" jam game Umbrella Dream (simple platformer) - sure it was easy to understand and kinda enjoyable to play, but I gained nothing at all from making that game.

Conclusion

So, there's one more game jam under my belt. Once again I worked on something that deviated from standard genre conventions and as a result had my hands full trying to juggle everything into a game. Success in making an actual game was partial. The jam itself on the other hand was fully successful. We were able to bring a new mechanic into light and see how it worked - which it did. This time the game around the mechanic just fell a bit short - but that is also a success because I was able to pinpoint how it went wrong and at the same time understand better why I've experienced similar failures in the past. That said, the chances of actually continuing development are kinda low based on prior experience. I do consider this particular project to be among the more interesting ones in that regard though. Nevertheless, just thinking about game experiments I have made in a reflective fashion at least keeps me in the right mindset.

Anyway, I think that's enough about this year's GGJ. It's time to get back to the side of games I am more comfortable with: playing them, and writing about them. Thanks once again to Stage for setting up the jam site, and of course to everyone who was there contributing to the atmosphere. This year's jam site had just enough space and people filling that space.

Dragon Age: Origins - Part 2

It's finally time to continue where we left off some months ago. After bashing Dragon Age from several angles, we were wondering why on earth I chose to plow my way through the game. This post answers that question. Once again a lot of the things I'm going to say could be said of Mass Effect. I will be talking about my character a lot. Cath was a female city elf rogue. I wanted to play a rogue as it has been a while since I have played one; I wanted to play as an elf because for me it's always either elf or human, and once again it had been a while; I chose the city background to give my character a bit of cynical and practical flavor; finally, I chose female because that's my usual preference when choosing a virtual identity.

1. The roleplaying appeal

This is pretty much the main talking point of this post. I want to use an interesting description by James Paul Gee about the relationship "real person as a virtual character", or in this case, "me as Cath", as the basis of this discussion. The key point is that this relationship has three identities, not two. The first two are relatively straightforward: obviously there is myself as the player, and there is Cath as the character - we both bring possibilities and limitations to the gameplay experience. For myself, this means my mechanical and cognitive ability to play the game; for Cath this means her stats and other things that describe her in the game world. It's the third identity - the projective identity - that makes roleplaying games interesting. This projective identity is my interpretation of Cath's personality. It is not simply me, nor it is simply Cath - it's more like me making decisions for Cath based on what I know about Cath. If that doesn't make all too much sense, worry not - just read on.

This is bread and butter for those with experience in tabletop roleplaying games. You play as a character and in most cases it's not yourself. However, neither is she or he completely fictional - the end product is a combination of both the player and the character. The same can be said of acting. What you see on the screen is not the actor nor is it the character - it's always the actor's projection of the character. A different actor would portray the character differently - within the freedom they have been given. This freedom to interpret is also highly important when we talk about digital games. In tabletop RPGs the degree of freedom with which players interpret their characters is huge and they also typically have more agency in writing their character. The game master typically sets certain limits that are necessary for his campaign to work but beyond that, characters are created by the players themselves. When the game master and all the other players are replaced by bytes of code, upholding the illusion is much more difficult.

The ability to uphold a strong sense of roleplaying is BioWare's strength. This sense is particularly strong in Dragon Age, much more so than it was in Mass Effect. What I mean by that is, the game inspires me to think about things from Cath's perspective by providing me the freedom to do so. One important part of this is the way choices are framed - or rather, the way they are not. All kinds of value judgments about the choices are left to the player. Cath's companions did often chime in with their opinion, and that is fine - more than fine actually, because they *are* people, and people have opinions. What's important is that the game itself did not. Mass Effect has this problem with its bipolar morality scale - the game is disrupting my roleplay by explicitly telling me which actions are "good" and which are "bad". Note, again, that games definitely can tell things like this, but they have to do so implicitly, by showing consequences.

When choices are framed in one way or another, the decision-making drifts away from the projective identity to the player identity. This happens because the game is telling the player something the character cannot know. The extra information can cause conflicts that break immersion, especially if there are explicit game-mechanical consequences involved. For instance, if I - based on the projective identity - make a choice that I (the projective identity) deem "good", and then the game explicitly tells me that it was actually "bad", and punishes me for it (by moving my character to the wrong direction in a morality scale), it is severely inhibiting my ability to roleplay. The conflict here is that my character thinks the choice was "good", but me as the player is given information that it was "bad" and as a result my character is also now more "bad" by a bit even though I had her projected as "good". As you can see, this is a huge problem that comes with explicit morality scales.

On the other hand if choices aren't explicitly labeled and outcomes are only revealed later through consequences, it just becomes another opportunity for reflecting upon the projective identity when things end up going south. Choices can also inhibit roleplaying if they are too limited. This is the more difficult thing to avoid in digital games, because you would need one hell of an AI to truly abide to all sorts of projective identities. The general problem is that if none of the offered choices feel satisfactory to the projective identity, the player's agency in constructing that identity is taken away and put into the hands of the game's writers. Dragon Age generally upheld the illusion that I was able to make choices that seemed sensible to Cath. At the same time, choices made during the game - especially choices concerning companions - contributed to the growth of Cath as a character. This is no small achievement for a digital game. It is, indeed, more than enough reason to enjoy the game despite its shortcomings.

It is worth noting that while being able to create Cath myself (partly anyway - her background had to be chosen from a limited number of options), it is not necessary to have free character creation to provide a strong roleplaying experience. Even if the protagonist is pre-written, a game that supports roleplaying still easily allows the player to develop a strong projective identity. Case in point: The Witcher - especially the first one. Although the character is Geralt of Rivia with predetermined background and abilities, what I experience is my interpretation of Geralt of Rivia, and the game allows me to make choices based on that identity. In a way, even if you can freely create your character at the start of the game, the game itself still dictates a lot about what your character can become - in this sense, starting with a predetermined character is not actually all that different. In fact - to my knowledge - it's actually very common to have pre-written characters in live action roleplaying games. It's not unheard of in tabletop RPGs either.

2. Virtual relatedness 

We already know that I place a lot of emphasis on character writing in games. I know it's a bit silly, but I don't have that high expectations so it kind of works out. However, when we're talking about roleplaying, the importance of other characters in the game rises even further. A lot of choices in BioWare games concern how the player's character interacts with other people. To put it another way, the player's capability to express their projective identity is heavily influenced by other characters in the game. This, in turn, puts a lot of emphasis on a) how well these characters have been written and b) how well interaction with them is presented in the game. Creating interesting characters has been a strong point for BioWare for the longest of times - and Dragon Age is definitely not an exception. Indeed, without a strong illusion of virtual relatedness I would not have bothered with the game for long.

There is one clear sign that Dragon Age succeeds in creating this sense of virtual relatedness: I had very different opinions of companions when I thought about them as myself, as opposed to when I thought about  them as Cath. It is, I think, the best indication that Dragon Age succeeds first and foremost as a roleplaying game. Whereas I find Morrigan's antics amusing, for Cath - whose life depends on her companions - they made Morrigan seem incredibly untrustworthy. While Leliana might have been naive and even childish for me, for Cath she was the most comfortable person to be around. One more: I liked Alistair from the get-go almost, but it took almost the entire game for Cath to be able to truly consider a human male as a friend. All these companions had a huge role in building Cath. Her choices became influenced most by those she held closest, and she became skeptical of anything Morrigan seemed to approve of.

The sense of relatedness is created by making companions (and other NPCs) feel as much like people as is feasible in a digital game. They have their opinions, and they make observations in the environment. They also talk to each other when traveling with the player. Dialogue with them is written well, and it's delivered with very solid voice acting. In short, they make you want to talk to them, even become excited about being able to visit the camp between dungeons. This may in fact have been one reason why I felt the dungeons were so effing long - they kept Cath from having chats with her companions. Indeed, in contrast to camp conversations, the dungeons offered nothing to Cath's personality growth. They were merely obstacles between me and the content I actually liked experiencing. For the record, Mass Effect largely failed to create similar feelings in me because of one important difference.

In Mass Effect, while characters certainly are conceptually sound and interesting, they are portrayed rather horribly. The effort to make them feel like people has been either misguided or simply lacking. Having a conversation with anyone in ME felt a lot like reading an autobiography. That's a fancy way of saying that characters almost exclusively talk about their background. Some banter exists when they are taken with Shepard to missions and space stations, but not enough. I never truly formed any sense of relatedness towards Shepard's companions in ME because they did not feel like people. Even Garrus, probably my favorite character in the series, felt a lot like an audio book. In comparison, characters in Dragon Age feel more real, and thus more relatable - even though they also do talk a lot about their past. The key difference is that they talk about other things more.

Sense of relatedness is not strictly tied to roleplaying. I see it as a facilitator. Relatable characters aid the player in constructing their projective identity by putting the character in social situations - something that for us as social creatures is massively important in defining who we are. That is to say, it's not impossible to roleplay in an empty world. It's simply easier to construct a personality for your character if you can reflect upon that personality through interactions with other people. You know you're there when empathy replaces instrumentality as the player's basis of making choices (this is something I want to expand in another post). Likewise, relatedness is important in all games, not just roleplaying games. This is hardly surprising, as it is just as important when consuming other forms of fiction - be it books or movies. Narratives tend to work rather poorly if it's enacted by unrelatable characters - we need to care.

3. There is no freedom in a group

Although we have now concluded that characters in Dragon Age are quite relatable as people, there is one thing they are not - and that's a group. It did not bother me as much this time around, but it certainly bothered me when I was playing Mass Effects. A lot of dialogue occurs between the protagonist and her companions, but the companions themselves speak very little with each other. There are no group events in the camp - basically all dialogue between companions takes place when they are in the active party. While well written and somewhat frequent, it isn't enough to provide a sense of group. The relations between companions are superficial at best and while their antics are amusing, they don't develop into anything. In this respect, the game is heavily centered on the protagonist. This is actually a very common trait in roleplaying games of Western origin - it's also a cultural thing.

Culture or no, conveying a sense of group in a game with relatively high degree of freedom is far from trivial. By limiting most interactions to one-on-one, the developers have saved a lot of resources. Whereas one-on-one conversations only need to branch based on player choices and a few flags, group conversation branching is likely to get out of hand quickly unless certain limits are placed - and DA is just not placing them, opting for more freedom instead. This is fine, and supports what makes it good as a roleplaying game. It does however also mean that it would be almost impossible to convey a sense of group by having many-to-many interactions. First of all, simply accounting for the fact that there is no telling which characters will actually be present would require a ton of branching. On top of that, they would also have to take into account all kinds of status flags about the protagonist's relationship with each character etc.

I am somewhat curious whether this aspect has been developed further in, say, Inquisition and its war council. Meanwhile, a close comparison can be found from the Persona series, where the sense of group is immensely strong - especially in P4. However, the game is practically linear and while the player character can have different relationships with his companions through social links, these relationships are in no way reflected as branching in group events. It makes the entire group more relatable, but at the cost of player freedom and their ability to roleplay. In this scenario, writers are always guaranteed that certain characters will always be available for the group event, and there are not status flags to worry about. Even player choices during events are there almost exclusively for flavor, so there is no branching whatsoever. This is a common trait in Japanese RPGs and they play out much more like a TV series in this sense.

It may not be impossible to get the best of both worlds but I'd imagine it would be incredibly resource-intensive. With very careful writing, it could be possible to make conversations modular enough that you could simply omit and/or replace single lines without changing the entire discussion at each branch. However, doing this while still attempting to make the dialogue interesting and the characters relatable sounds like a massively tall order. In the future problems like this could be maybe addressed with AI when they learn to produce text in a credible fashion while staying true to the speaker's personality - but again, that sounds far off. Until a game comes along and proves otherwise, I am going to consider the lack of group sense in DA as a cost that comes from giving the player freedom. Therefore, limiting the game to one-on-one interactions has likely been a conscious choice rather than an oversight.

Conclusion

Last time Dragon Age: Origins took a serious bashing from me; this time we have come back to explore its redeeming qualities. What the game lacked in, well, being a game, it took back in being a roleplaying experience. The real story in the game for me was following Cath's growth. Being able to immerse myself in the game world through my projective identity as Cath was far more important than any game mechanical aspects. This, to me, is an appeal that is generally more common in Western roleplaying games but even among them, strong experiences that get close to what tabletop RPGs offer are few and far between. Getting so much out of other aspects of the game most likely made the dungeon parts even more frustrating though. While companions feel like more relatable than they did in Mass Effect, they still do talk a bit too much about their past and a bit too little about other things.

Finally, there is no sense of truly forming a group of people in the game as most interactions happen between the main character and a single companion at a time. It would seem like a necessary amendment that is required to provide the desired degree of freedom to the player.

Because of the gameplay shortcomings I am a bit skeptical about Dragon Age 2, given that it has been generally decreed inferior to Origins. For some reason I still feel bad about skipping a game should I move straight to Inquisition. There was also another consequence after playing DA. Since I really enjoyed the drama and basically everything except dungeons, I decided to finally look into Telltale's storytelling games and also to play other purely story-based games (although, I actually just stopped playing any games at all* for a while after finishing Walking Dead season 1). My next post will probably be about Persona 4 Golden though. I will still write about some story-based games in the future.

* Dota 2 is not a game - it's a lifestyle.