Develop Conference 2015 - Being a Mother != the End of Making Games

What is Develop Conference? 

If you’ve not been before, Develop Conference in Brighton is probably the biggest UK developer event.  Amazing talks, free expo and of course fantastic networking opportunities (read parties).  This year marks my fourth conference, and this years felt very different as it is the first where I’ve taken on more of an active role.  Don’t get me wrong, attending the talks can be incredibly insightful and inspiring (check out Rami’s keynote for example).  Even if you just rock up to the bar and chat the day away with fellow developers you can absolutely get a lot out of the three days that is Develop Conference. It’s just this time I decided to sign up for the game jam and put myself forward as a speaker.  

Taking Part

Way back in the year the call for speakers happened and so I threw my name in the hat.  Alex and I put forward a talk on how not to indie, Des put me in for a panel on how being an indie is not easy and I nominated myself as a noob speaker.  Well after the first two talks got rejected, third time was indeed the charm (pro tip here, if you really want to take part put yourself forward as much as possible!).

Closer to the day the announcement for places in the game jam surfaced and as it’s been such a long time since I last jammed (and I already had a babysitter for the week - thanks again Aunty Vicky) I booked places (Alex needed more convincing, but I booked him in anyway).

The Game Jam

So 16 hours is a super short amount of time to make a game, but this is a jam and we’re all about the challenge!  Oli teamed up with us once more and we felt good about having a bit of fun with a silly little game.  So the theme was announced as ‘Pebbles’ and we were off.

Alex was all about using the pebbles as counters and to maybe revive ‘Trowerstone’* but this seemed really dull for me, and as the artist it wouldn’t leave me much to do apart from making the best goddamn pebbles 16 hours can buy… So I put forward the idea of using the pebbles to make tiny golems and BOOM!  Tiny Golem was born.  The POA we settled on was that we would have a box of procedurally generated pebbles with different statistics attached to them - big pebbles were slow with lots of health, small shiny pebbles were fast and flat pebbles were stable - the player would then pick 6 (head, body arms and legs) to create their golem who would then be unleashed on a sand castle.  The golem would attack the castle whilst the castle defended itself with cannons, the aim to destroy as much as possible before the tide came in.  The player would have indirect control over the golem, choosing to be defensive (and slower), normal or charging (fast but vulnerable).

We began.  Oli created the pebbles using shader magic and Alex wrote the animation (all in code, none of these fancy Unity animation tools) and I got onto some UI and sand castle production.  There was pizza and drinks provided (thanks Square Collective for sponsoring!) and by midnight on the first day we were quietly confident that we would get what we set out to do done.  If you’ve not game jammed before, this line of thinking is basically what gets you in trouble.

Next day and the final 8 hours and we had lots of lovely visitors and could see we were going to have to drop some stuff.  So Ken (Wong) was kinda right, he said we would get 45% done, I reckon we managed about 60%.  We also had a fab visit from Luca (Redwood) who gave us loads of coffee (if you want to make friends at a game jam - bring coffee).  So the tide was dropped (because don’t do water in a game jam) it became golem vs. castle and the indirect control was dropped so you really had to choose your pebbles wisely!  But we finished (right on the nose) and have a very playable game!

A very playable game that only went a won!  I knew there would be judging and a prize, but I didn’t realise the trophy would be so nice!  Now we can get the asymmetric multiplayer in where one player builds the castle and another the golem, and more defences, leaderboards and sharing to social media.  If anyone would like to fund the mobile release we also have plans for golem resurrection, gatcha special pebbles and for monetization ;)  

Micro Talk

The jam was a nice distraction from the bubbling fear that was starting to surface as the talk drew nearer.  I maybe didn’t really think this through. I’m not very good at public speaking, I absolutely want to be a positive influence in the games industry and particularly for women and parents, but that means I have to put myself out there, so here I am bidding for a full talk slot at next years conference.

The format for the talk was, a group of new budding speakers had 3 minutes each to talk on one of a collection of topics and then be rated by the audience.  I chose ‘What I Learned by Accident’, which basically gave me license to talk about anything in my indie career as it all began ‘by accident’.  I almost didn’t talk about being a parent and an indie developer, but after a confidence boosting chat with another female game lady dev and on reading an article about ‘mother shaming’ in the workplace (it’s not just games that struggle) I decided to run with it.  

There is a drop in the number of women in the industry in their mid 30s, and we think it is because they are having children and not coming back to the games industry.  The point of my 3 minute rant was we should hire more parents. Why?  Because if you want team members who are not just committed to making good games but also committed to your business succeeding then hire people who have responsibilities outside their work that mean they really, really need to hold down a job!  Obviously we’re not going to want to work overtime, or crunch (because no one does), but to make sure we can leave the office on time we will work harder and smarter in the time we have.  No one multitasks like a parent.  For example, whilst waiting to give the talk, I was texting my sister instructions on how to prepare dinner for Willow.      

Well the talk seemed to resonate with the audience, after all the talks were given and the cheer-ometer had whooped it’s last whoop, I was declared the winner!

So What Next?

Now I have 12 months to prepare to do it all again, but this time maybe stress less about my talk!  So back to work it is, and hopefully some more talk opportunities along the way!  

*A game for another post methinks.

Tiny Red Riding Hood Dev Diary 02 : Best Laid Plans

O' mice an' men oft go astray.

Well, last time I had hoped to get a lot done before showing my progress off at the next Brighton Indies.  Suffice to say I didn't quite get there.

It's not all my fault or all doom and gloom for that matter.  Interrupting my progress was the very awesome Space Krieg Jam that we hosted, Alex has taken up gainful employment which has had a massive effect on the work/life balance and Willow has been a bit poorly and needed lots of cuddles and attention.

Also some things happened which have maybe slightly altered my perspective on the game.  Mostly the release of A Day In The Woods, which I think just looks a lot better than where I seem to be heading and has made me question everything (OK not really, just how it looks).

So time to turn it off and on again.

Not a false start.

That is to say everything up to this point hasn't been a complete waste of time.  As I said before this is a learning process and part of that means throwing stuff away and starting over with all the juicy new knowledge and skills you now have!

So what's happening?

It's OK just not right.

Red and Trees re-do.  There's more to this than me getting my knickers in a twist over a better looking game.  Red is kind of broken.  She hasn't skinned well and has lots of one sided polys which don't play well in Unity.  I want to retain her look, I just need to make her better, and probably man up and face UV unwrapping her (*shudder*).  The trees on the other hand are just not English forest enough for me and far too simple.  They did the job of introducing me to low poly modeling and will do fine as place holder trees, but they just don't look right.  I need to make low poly trees that resemble oak and fir trees.

NavMesh, State machine and Lists.  So here's a whole bunch of things that are new to me!  At the last Unity and Cake meet up I went to these things cropped up.  Using a NavMesh to help Red navigate the woods in a less linear manner, an introduction to state machines and how characters animations interact, and finally using lists, which I'm sure I do know but then I really don't!  Basically if I want the apples to appear in different locations on the tree, it has been advised that the best way to do this is to have a list of possible locations on the tree which do or do not get populated with an apple.

POA

Tomorrow is the final Unity and Cake meet up.  After that Kerry will be busy nailing the public version and then the show hits the road as the newly branded Make, Play, Code.  And I really want to have a working prototype ready!  So, in the spirit of keeping it small and iterating on what I've done the aim for tomorrow evening is:

• Have a basic UI in place
• Have the apples appear on the tree
• Have the player count (tap) the apples

I'll still be using the assets I have for now, once I get this much working we'll look at making it all look less generic and just nicer!

I wish I could Blender better...

The Mother I Never Knew I'd Become

I've said before that one thing about becoming a mother that really excited me was the idea of making games for and with Willow.  I decided that the game I would start developing as part of the Unity and Cake meet ups would be my first attempt at an interactive book for Willow.  Obviously I'm really excited about this, it's something I've had in mind since before I was showing, but now that I'm doing it I'm finding it's not nearly as simple as I thought it would be.

Willow's already a gamer.

Little Red Riding Hood

When I was thinking about what games I would make for Willow, I had a grand idea of a woven fairy tale land where classic characters from different stories, fables and nursery rhymes would all live together in a big fantasy world.  But this would be a huge undertaking!  Firstly it needs a lot of writing, and not just taking the old stories and modernizing them or adapting them but also linking all the characters and weaving their stories together.  Secondly it would require a massive amount of art, far to much for just little old me at the moment.  And finally it would need skills to produce that I just don't have yet.  I still want to make this game, but not yet.  For my first solo project I need to start much smaller.

I don't know why but when I think of children's stories the first one that comes to mind is Little Red Riding Hood, so I'm going to start with this one and work up to the big world.  I thought I knew the story pretty well but wanted to do some research, so I brought Willow some fairy tale books (thanks again to everyone who gave us gift cards for her birthday) and downloaded a bunch of Little Red story apps.

Turns out Little Red Riding Hood isn't nearly as warm and fuzzy as I remembered...

Nerfing the Brothers Grimm

So I always thought I wouldn't be the type of mother who won't let their child fall over, eat dirt or grow up with the same stories that I did (yes Willow is going to know all about the Thundercats).  And whilst she will happily eat floor fluff (as hard as we try to stop her), and has had more than a few tumbles leaning to walk, we get to Little Red Riding Hood and suddenly I'm reaching for the bubble wrap and thinking about how I can make the ending less horrid.

For those of you who don't remember how it all ends (spoilers) the hunts man hears the wolf snoring (after a heavy meal of Grandma and Little Red he needs a power nap), so he cuts open his big belly to retrieve Nan and Red.  They then decide to stuff the wolf with rocks and sew him back up so in the future they'll hear him rattling before they see him.  Lovely.  

Not what we want...

 Now as a story at bed time I an see that this is totally fine.  We can make all the noises and rumble Willow's tummy, and when it comes to all the bits that are a bit nasty, well that's left to Willow's cute and adorable imagination.  My problem, and why I feel I need to nice it up a bit, is that when you're putting this into a game, and asking the player to interact with the story points, suddenly you've got a cross between Surgeon Simulator and Cooking Mama World: Hobbies and Fun.  Which isn't exactly what I want.

I'm not saying that it's all as bad as say the original story (before the Grimm's lightened it up a bit), or Todd McFarlane's vision of Little Red, but it still doesn't sit well with me.  I'd rather not have both Grandma and Little Red cut out of the wolf.  There must be a better way of telling the story.   

And A Better Way to Play

Whilst doing research into story apps I came across a lot of criticism for interactive story books.  One article in particular quotes author and critic Nicolette Jones as saying "I’ve never seen a picture book-app that does something that a book doesn’t do better" and having looked at 6 different Little Red Riding Hood story apps on iOS I would have to say she might have a point.

On the one hand I'm really disappointed with the apps available.  The interaction really doesn't add anything.  If all you're doing is moving the character across the screen or selecting a fork in the road you might as well be reading a 'chose your own adventure' version of the story.  But there is opportunity here.

Of the apps I played, the Nosy Crow version was by miles the best.

I always had it in mind that the interaction in the story would be more involved and teaching areas such as numbers, colours and letters.  Like when your little one is watching kids TV and the cartoon character on screen asks if they can see the white sock?  It doesn't matter if Willow interacts or not, the cartoon will continue by congratulating the audience on finding the sock.  This is where an app has the advantage, not only will the story wait until the child has located the sock but next time we read the story it could be a shoe or a flower that needs to be found, or this time a red sock not a white one.

Making the App

So here's the tricky bit.  Not only do I need to figure out a 'better' way of ending the story that doesn't involve cutting up the wolf, but I need to come up with interactive learning games within the story and decide how it all will look.  The games I think will be the easiest part, and the most fun to test with Willow.  How the game will look is proving to be the hardest part.

First Red doodle

A part of me knows that I'm doing this for Willow, well and for me, so how it looks needs to only appeal to us.  And she doesn't care.  She's fascinated by anything on our mini magical colour boxes, but I am my worst critic and I'm finding this part really challenging.  I can't make my mind up if it should be magical like the setting of a Ghibli film, or clean and contemporary like the Toca Boca games, or crafty and homemade like Lumino City.

At least I know Red is going to look like Willow.  

I have no idea what the forest should look like.

Right now I've a bunch of ideas for endings and lots of interactive games so I can start getting the mechanics and interface up and running (least I'll have something to show at the next Unity and Cake meet up!).  For now I'll keep hitting my head against my artistic block and hopefully something will fall out that I can use.



Next I suppose I should start worrying about Kings who murder princes and Children pushing witches into stoves...