Skip to content

Tag: insight

New narratives for mobile casual games

I loved this NoClip documentary on the making of Dishonored.

I believe that in terms of narrative there are a lot of interesting aspects that can be taken from this concept. Take the match-3 with decoration genre for a moment. You earn a star beating a level and you use that star to complete the next task. A cutscene with dialogues is shown and then new tasks are opened. You have to play more levels and see how the story goes on.

What if:

  • we can make the environment speak more about what’s happening
  • we can let the Players explore better and interact with environment discovering where to use the stars to fix things
  • we can deliver the story reacting to the Player’s actions instead than stop it to show a cutscene or a dialogue

The MVP Culture

Over the years I have learned the single thing that product leaders hate most: uncertainty. There is a common myth of epic leaders capable of having a solid vision to spread across their team. It is almost never the case. Usually the game vision is the result of team effort.

During the development of a new game or a feature for an existing game, there are a lot of variables that make the people feel uncomfortable and insecure regarding the return on that investment. Which is why the MVP, minimum viable product, concept has been rented from the startup “fail fast” culture.

You develop the basics of that new implementation and with that you measure the results. In theory, you will eliminate risks.

In practice, instead, often that way of producing things shows a lack of vision and understanding of the market. I saw many times the MVP converting to the final product. The team publishes the MVP of a new features, metrics and analytics seem OK and they pass to the next MVP without putting the right effort to make that feature really awesome. 

This is a short term strategy that never works. Games are a refined craft that require passion for the details. That is where the magic happens.

MVP are useful to:

  • Test the technical context and make proper development estimations
  • Have something practical to show an idea to the upper management
  • Run playtests with some cohort

MVP are NOT the right thing to do if you want to:

  • Run split test with engaged cohorts
  • Prove the growth potential of a new game
  • Estimate the LTV improvement on the long term

Designer VS Author

A game designer is the facilitator of the act of game design among a team. Everyone in a team participates actively to the design of the game. From the producer to the junior QA, everyone is making the effort of delivering a great experience to the Players. Which is to design a videogame.

A friend of mine made me this question today: what if you make a game alone? Are you still a game designer?

I answered him: no, you are not a game designer. In that case you are an author, which is different.

He insisted: but you are designing a game, right?

Yes you are. Making a game alone is game design, too. In that case, all the work is on you. You are not facilitating the act of game design among a team.

To be a professional game designer ready to work for companies you need a completely different set of skills. You should be able to:

  • Understand the business goals translating concepts like scope, budget, KPIs to the gameplay
  • Being able to inspire your team analyzing and breaking down other games and by preparing specific proposals
  • Create and maintain well written documentation so that the vision will be the less ambiguous as possible
  • Run playtests and undestand the pain points of your game. Being able to translate that insight to all stakeholders.
  • Be present in a lot of meetings often facilitating creative workshops.

All of those things are different when you are making a game alone. Which is why I differentiate a game designer from an author. An author is a game designer, but can be a bad teammate. A game designer is a facilitator, but can have not the right talent to make a game alone.

If you want to work for a company as a generalist game designer prove your ability to work in a team. You will unlock a lot more possibilities!

Stadia and Cloud Gaming

Stadia was killed by Google. Cloud gaming is still alive and well in services like Microsoft Game Pass. Google put cloud gaming in the center, selling the idea of cloud gaming as a revolutionary platform. Microsoft instead put cloud gaming in the right place: as an added feature for a great service.

Cloud gaming is a very interesting features. I ask myself when Valve will also adopt it. I have a lot of friends with MacOS willing to play the same games with other friends with PCs. Cloud gaming would be a great add to Steam.

Cloud gaming is not the future of videogames, thou. Until now, in fact, there is not a single scenario in which Cloud Gaming offers something better than classic Console/PC gaming. Usually performances are better on console. Also, people who cannot afford best devices usually has access to worst Internet connections too. So that the market for pure cloud gaming is very small.

Cloud gaming is a feature and not a platform.

People like us

I hear at almost any meeting and occasion to speak about game design people’s personal opinion. To me this is not clear. I like when I do this and that happens. When I see something like this I feel angry. And so on.

That is because we naturally relate with people like us. Fact is that people like us are a myth. A utopy. Each one of us is unique and we have our tastes and behaviors. Which makes our job as designer so interesting.

Instead of referring to people like us it is better to think in missions, journeys and more in general activities that those people like to do. People who like to run with their dogs. People who play chess with friends on thursday afternoon. People who only eat vegetables.

That is where the most interesting things are considered.

Games and stories

I am taking a course on game writing and learning the hard way how a game can live and be successful without a story. Games do not need stories.

When gameplay and story marry well the story can boost the experience for it be remarkable and memorable. This is because play is a problem-solving activity, useful to improve some of the skills useful to survive. Stories instead help us understand better people and how to relate with them. Games are about things, stories are about people. This is why is so hard to link a game with a good story.

Point of touch among design and writing is that designers look for fun. And fun is a feeling. Writers look for feelings. You can easily spot there is an interesting overlap.

First impressions on the new podcast by Hideo Kojima

As a great percentage of game designers out there, I really admire and respect Hideo Kojima. He has a big ego, he doesn’t speak one word outside Japanese but still he managed to introduce many innovations to the medium.

The main advantage of mister Kojima is probably also his greatest weakness. He didn’t managed to become a movie director and he adapted many things from movies and books to the games mediums.

Today the first episode of his new podcast was published on Spotify:

I like that he explains exactly WHY he helped creating the stealth genre. It is very interesting to hear his chain of thoughts. He acted like a true designer: he understood a genre (shooters or shooting games) and he had a personal tought on storytelling . Shooters of the time, in fact, had no story. No reason why to kill enemies.

Plus, technical limitations on MSX gaming system made impossible having many shots at the same time. So that Mr. Kojima, starting from a personal thought and using the limitation as creative leverage, created the perfect excuse to eliminate enemies: infiltration, heroism.

I like a lot that, before of answering the question regarding the secret of MGS’s success, first thing he says is: I don’t know. Then he starts to reason. Very humble attitude, hard to see out there.

I would like to wish huge success to this new initiative by Mr. Kojima!

Being loyal

Year ago I was running a very promising free-to-play project in a local incubator. It was very promising, it was the future. My lead artist said: you are inventing the devil. Of course, it was just in my head. The project had no chance to go forward, because I wasn’t being loyal to my will of creating a new company around it.

Being loyal with ourselves is not just to maintain the promises we make. It’s not to respect the compromise. Is also to make well our numbers. If you want to build anything and we consider ourselves game designers it is necessary to stop and think well to all costs and scopes of the things we want to build. And then add a 20% of error to all of that. Otherwise we will most probably fail.

My project failed at many levels, but the main one is that you cannot start a free-to-play ambitious project without great professionals and lot of money behind. The art of giving games for free is very expensive, needs a good monetization strategy and the acquisition of new Players requires huge efforts.

I am glad that I didn’t invented any devil, and I am glad to be here happy telling you those stories.

A VIP idea from Delta Airlines

Design games for the free-to-play mobile business is whale hunting. Unless you are a genious, like Bit Life developers, you will probably do the math. And doing the math, you will notice that you need high spenders to sustain your business.

Yesterday I saw this comment on a LinkedIn post:

Shoutout to Tom Hammond for this great idea.

I checked out the original Delta program and now I cannot understand why nobody is doing that.

Scenario

Ana, a Slotomania player, is a Black Diamond level VIP client. She gets an ad from your Mobile Casino Game that promises her VIP level can be matched with a challenge.

  • Installs the game, logs in
  • A pop-up asks her if she already has VIP status in other games, she answers that she does and details that she is a Black Diamond in Slotomania
  • Within 12 hours, a person from Customer Support contacts Ana, asking for more information
  • Ana’s VIP level is matched with the game’s VIP level.

Why?

If someone has a high VIP level in another game, it is most likely a whale. It could be a whales acquisition strategy.

Failing at premises

Successful games are games that manage to meet the right audience willing to invest their money in them to get the kind of fun they expect. And that is nothing new, it’s game design 101. It’s the very first lesson you learn anywhere when you start designing games. You should design a game for some audience.

There are many ways of failing at this. Actually, the vast majority of games fail to deliver this exact point. Which is why video games are a very risky business.

The experience may help you avoid some mistake, and mine has a almost constant issue that I see: failing at premises.

In fact, a lot of times I hear sentences like:

We want to make a game like <CoolGameTitle> but more [casual|hardcore|midcore], just like <NewTrendyGameTitle>.

Senior VP of Product Ownementshipssss (or some fancy title like this)

I don’t know if the syntax I am using is completely clear, I guess it is not. But the truth is that when you want to change a playstyle from a specific audience, that almost for sure leads to disaster. Casual, midcore and hardcore to me are a way of describing the gameplay session time.

It is good that you take your references, but if you are willing to force a significant change in gameplay behavior you are on the wrong way. If you know that a specific successful game has that playtime, you should consider that seriously as a pillar and not as something to change. We can be misled to think that “making things simpler” means “shorter/longer gameplay sessions” and that is almost never the case.

Never say never of course, but that is in my experience one of the false premise that make a game lose the money and efforts you and your team invested in.