Skip to content

Paolo's Blog Posts

Mobile cloud as a feature

The classic way to start a new mobile game is:

  1. For some reason, I arrive at the virtual store
  2. I choose the game to install and tap the Install button
  3. I wait for it to install. Some games are huge.
  4. I start and there is a stage where the screen is dark
  5. I wait while looking at a splash screen for a few seconds, less than 15
  6. In case there are updates this time increases
  7. I am introduced to the game.

The games of the future should be like this:

  • For some reason, I arrive at the virtual store
  • I choose the game and PLAY
  • I wait less than 2 seconds
  • I am introduced to the game

It seems like an impossible feature, but that’s what will make the difference for me.

15 years in the Games Industry!

I realized that I am turning 15 in the video game industry this year. Not bad, considering that the average time is 7 years. I have doubled the average, and I am satisfied.

There have been times when I haven’t found a job in my industry and I’ve dedicated myself to something else. I have been a QA tester in a cybersecurity company. I was a data scientist at a robotic automation startup. All these experiences have enriched me.

I am very happy that I was able to stay in the industry. Despite the various blows received, I always got up. Thank God I wasn’t too impressed, although I bear the consequences.

Nowadays my job is part of my identity as a person, and I’m not sure that’s always a good thing. Many people work as game designers, I AM a game designer. People appreciate my designs, they always reveal a passion for the projects I am involved in. I have serious difficulties relating to the lack of professionalism, though.

Personal challenges

When I see a roadmap based on “best practices” without reflecting on “whys” and with no connection with the Players of the game, my blood boils.

I can’t accept the use of KPIs as targets, a huge mistake that is very common in the industry. Direct efforts to improve indicators and your game become a means of justifying investments. Not a means to deliver a great playful experience to people. I understand that we talk about KPIs with investors, it is a way of selling. But transferring these discussions to those who have their hands in development is deleterious.

I always think of all references and edge cases and it is an activity that engages my mind a lot even when I am in front of a book in the evening. And if I see the solution being replaced for no reason, I already know that I will spend a sleepless night out of anger.

My love for game design

I love to define everything in detail. In a self-respecting team, some more visionary people manage everything and make decisions. I like to help these people land ideas down. I like to support them in their decisions.

Someone has to do the dirty work! Prepare documents, wireframes, and flows. Square all the numbers in a spreadsheet. They are long and difficult activities. For some, they are also boring. I love doing them! I’m a game designer, it’s not that they pay me to do it. I do it for love!

My goal for the next 5 years is to improve my relationship with the profession. And my next full-time gig should start me in the World of leadership. I have seen a lot of things, now it’s time to take part in the strategy too!

In the meantime, happy anniversary to me!

Reviews are your best friend

Whenever you are starting a new game project or if you are working on LiveOps for an old one, you have a free asset that is very useful: reviews.

Only a small part of Players are willing to leave reviews for your games, especially in free-to-play. Videogames can ask directly in-game to leave a review, but not everyone does so. They do not represent in any case the dominant opinions, but they are useful to spot opportunities for your game.

  • If you read critical reviews and you notice something that repeats a lot, that something can be converted into a unique selling point for your game.
  • If you read positive reviews and you notice something that repeats a lot, that something should be a must-have for your game.

Use Steam or Data.ai to filter out positive and negative reviews. Remember Pareto’s principle. Use always 80% of other games and innovate on the 20%.

  • 80% you should take can be read in positive reviews that repeat
  • 20% of novelty can be read in critical reviews that repeat

Analyze the reviews of the main game you are taking as a competitor, but also of its clones and competitors!

What? There are NO clones of that game? You are probably choosing the wrong competitor and you will hardly manage to have success in its field.

I broke it!

One of the trends I see in mobile game design comes from the hyper-casual wave of games: games that you can break.

Link to original Tweet

It helps the game get viral, players feel smart and it’s clever. Especially in multiplayer games, it works great!

One may feel that designers made bad work, but it’s not always the case. Often there are surprising discoveries in the process!

Can your game be broken by the Players? If not, can you make some mechanics less controlled to open up to that possibility?

Existence and storytelling

Yesterday I have finished watching a great Netflix show called “From Scratch”. Very suggested to anyone reading.

One of the topic of the series is death, still a romantic/casual audience may appreciate this kind of series.

Think in casual snackable games. What about creating some narrative to make the people reflect on existential topics?

Will that work?

Those topics are not comfy, but something very powerful may please our love for great stories.

The value in silence and resilience

Every so often I ask myself: what am I doing and why? It’s something that comes in handy, makes me put things into perspective and sometimes leads me to swerve on the path of my life.

I went to an event last week where I met a lot of friends and also alumni. It is amazing the amount of talented people that exists in the video game industry. Every time I go to these events I am surprised. Since the fashion of the home office began, unfortunately I am less in contact with so many people. There are very few people who, like me, decide to share the little they know online.

On the other hand, there are many people with exceptional talent who do their work in silence. They will not be known, they work for big companies very often diluting themselves in the mass but making millions to the corporations that are so lucky to have them in their ranks. Or they’ve been working on their own independent game, maybe for years. I really admire this resilience, even though I can’t help but notice the enormous risk of doing so.

However, life is one, and therefore I always ask myself: what am I doing? Probably the answer is: the right things to find my way.

How to use Twine for Player Experience Narrative

Play Lilys Choices in your browser here.

Game writers use Twine to write stories. It’s a great tool and pretty easy to learn. I have learnt during my certification course at The Narrative Department. This week I am prototyping a new feature for Lily’s Garden, so that I decided to use this new tool to test its effectiveness also in terms of feature prototyping.

You can play the Twine prototype here: we have the feature, Lilys Choices.

Final thoughts

  • Twine is a great tool to create a proper Player experience narrative for a new feature.
  • The idea of having an extra resource to start extra Dramas is not new, but it is very important that the dramas end up with a surprise for the Players. Also in terms of concrete rewards!
  • It is important for this kind of games not giving to the Players choices that exclude specific branches. First of all, produce all this content has a cost. Second, some Player may feel frustrated and may want to try the other way around. This thing is not possible in those games.
  • The narrative should be focused on a true fan of the game. At this stage other profiles in the team will probably find risks and flaws to the designs, so be prepared! It is very important to push things forward boldly.

Devlog

From the idea to the prototype

This week I am prototyping a new narrative system for a puzzle-renovation game like Lily’s Garden. I generated lots of ideas and then I selected the best ones. Now it’s time to translate those ideas to a prototype.

Goals and features

Before of starting sketching a flowchart for our Twine prototype, it’s important to understand why to prepare a prototype in first place. A prototype is not something ready to go out. It is not a product. A prototype is useful to:

  • Persuade the stakeholders that this step is necessary and invite them to think in its ROI
  • Align the vision of all the team members that will work on the feature
  • State all the assumptions, useful to prove with data and analytics the feature’s success
  • Inspire roadmap updates to fix the feature’s development in the pipeline.

I have very few time to do a proper prototype, I am doing this exercise for “ikigai” (= to do something I enjoy for the sake of it). I need to put some limitations, so that my prototype will feature:

  1. Only 1 event to show how the Player’s journey changes meaningfully thanks to the feature
  2. Player’s development across the journey
  3. Maximum 3 valuable binary choices, in order to avoid too many outcomes. In fact with 3 choices we will get 2^3=8 endings.
  4. The prototype should not be minimum. I am against minimum viable things. The prototype should show all that’s necessary to truly unleash potential, instead! That is why I will use the main idea and the two secondary ones described previously.

Prototype definition

Important for this kind of games is to keep things very linear and straight. Those are not RPG games full of options. The only options that the Player has at every moment is either to start a new task or play a new level.

Glossary

  • Lilys: the new feature will be called Lilys. Lilys are a resource that the Player accumulates based on creating special tiles (combining 4+ tiles) and/or getting and using power-ups, which are special tiles at the end of the day.
  • Lily Branches: every Day has a set of choices. Some choice are cosmetic, those are already present in the game. Some other choice can be meaningful story branches. In order to take some of the options, the Player should use Lilys.
  • Choice Points: Every time the Player makes a choice gets Choice Points which are useful to unlock extra rewards at the end of the day.
  • Variable Rewards: every time the Player completes one Lilys branch, there is the chance of getting a power-up. Variable rewards are useful to foster engagement. The Players in this way will have reasons to make Lilys Choices.
  • The Player can choose to Play a level or start a Task
  • During the Level, the Player will get and use power-ups
  • At the end of the Level the power-ups and special tiles will be counted and converted in Lilys
  • During a task, the Player will have to make a meaningful choice
  • One of the branches will involve the use of Lilys
  • All the branches will give choice points, useful for the end of the Day to get extra rewards
  • if the Player uses Lilys, a random reward will pop-out: 30 minutes infinite lives. It is important that the Player feel that there is a random factor there.

Now I can proceed in developing the proper prototype!

How to map and select ideas

This week I decided to prototype a new narrative system for Lily’s Garden using Twine. After deciding the right problem statement, which is:

How can we engage more the Players more interested in the story, rewarding every effort they make to reach better outcomes during the puzzle part?

I passed to generate a lot of ideas on my notebook. Then I filtered out the best of them.

Ideas classification

Now it’s time to map the ideas in a proper chart. The X axis will represent the engagement, the metric to improve. Engagement is measured with session length and average sessions per day. Those are the KPIs.

On the Y axis consider the motivation to stay longer and open the game more during the day. This article by The Games Refinery will help us.

The two main motivational drivers for this genre are Mastery and Expression. So that we have two possible charts to map out the outcome of our brainstorming.

I classify the ideas in both those maps and see if we spot something in common. Usually this process is a team process and takes time and discussion. Again, in my case is just a quick exercise.

Against mastery we can see that we have 3 possible ideas to build:

  1. Choose your Story: creating and using special tiles/power-ups during the puzzle match, you get points to invest in story branches.
  2. Day Perks: Once a Day ends according to what you used you can get extra rewards (boosters, power-ups, infinite lives, ingots)
  3. Rewards Missions: playing the game and performing positive actions such as buy lives, get extra movements, return every day, you unlock a special currency which can be converted in boosters and power-ups.

Mapping ideas with expression in mind, a single idea is in the hot spot.

We have then selected our main idea: Choose your Story. Secondary ideas: Day Perks and Rewards Missions. On this base we can build our prototype!

New narrative system ideas

This week just for the sake of ikigai I am prototyping a new narrative system for Lily’s Garden. Today I focused my efforts to the idea generation. I wrote down hundreds of ideas and preselected just some of them, which will be shown here.

The narrative of Lily’s Garden

The story is divided into large day arcs with subplots. Each day involves renovating a specific location. In order to do that, the Player has to beat puzzle levels earning Stars. Stars are useful to start tasks.

In the course of the game’s renovations, Lily collects items like keys and photographs, builds her relationships with other characters, and discovers more about the estate and her family history.

We will use those terms in this post:

  • Day: set of specific tasks that complete a story arc. We can consider a day like a sequence of an episode in TV series.
  • Positive action: use power-up/boosters, lives refill, use extra movement, complete a goal also if not beating the level, and so on.
  • Perks: boosters, power-ups, infinite lives, stars, ingots.

Reviews analysis

In order to better select the ideas, I’ve spent 1 hour reading reviews. Data.ai allows you to filter favorable and critical reviews.

The game let’s you decide the style of your house and decorations. It is fun and easy to play. The perfect experience for when you just want to relax. Engaging and full of power-ups to beat hard levels that you can create on the board or get by using ingots and completing tasks. The main character Lily reacts to everything and completes tasks.

The new system should be built on those strengths. Maybe it is better to have something more specific towards power-ups and tasks completion.

Many levels are hard to beat and some Player feels stuck. The day’s storylines have not always the same quality, probably because of different kind of writers involved in the project. Players lose what they got at the end of some event. Some Player may feel that the game is too greedy in monetizing the puzzle part (extra movements and boosters).

Our system should be able to mitigate the puzzle limitations. The Player should not feel stuck and if they are doing all the efforts to beat a specific level, that should be rewarded somehow.

References

I took some notes on things used in other games with a narrative component. I didn’t looked at top competitors, I just took notes on type of games that I already worked on in the past. This because one of the requirements of this task is agility.

Episode: Choose your Story: Premium choices for premium paths. Great for re-playability, usually something that is not considered in puzzle-renovation games because the days cannot be replayed.

It is interesting to be able to unlock an extra path during a Day, also if some Player may want to get to other outcomes. Branches should always connect again before of the end, to avoid this effect.

Tales: Choose your own Story: Trials and paths according to stats accumulated during the Story like in a roleplaying game. It would be great to connect the puzzle and the story somehow. Maybe associating each character to every level and let them accumulate statistics according to the power-up used and more in general to the positive actions done.

From the other side, this can complicate too much the system and it may become hard to balance and monitor the Player’s progression on the long term.

Fallout Shelter: There are characters to whom the Player can assign specific tasks to get more points and currency. What if during a specific day you can put your characters performing extra tasks to get extra perks?

This adds an idle/farming layer which may be not suitable to the core audience of this kind of games.

Project Makeover: Customize the aesthetics of avatars in order to make them successful for the end of the episode (day). Maybe the characters of a specific day set can strive to arrive perfect to the end of the arc, in order to the ending be more satisfying.

The risk is to fall in the trap of misogynic and racist narratives, thou. While makeover is great, it should be carefully designed to not offend anyone. Especially when something works out and translates to UA creatives it enters in a dangerous territory. Is that what we want as designers? I don’t think so.

Survivor.io: Complete missions and get an extra currency, useful to be exchanged with other resources during a season. It’s a pretty common practice among casual games and gives lots of agency to the Players.

The problem comes when the event end because Players may accumulate a resource and then they lose it or it’s automatically converted in something not valuable to them.

Selected ideas

I wrote down hundreds of ideas and, since I am doing this alone, preselected some of them. The format I use is: title, wireframe and short description. It is the best way of taking them the day after and decide what to do.

Remember the problem statement decided in the previous article.

How can we engage more the Players more interested in the story, rewarding every effort they make to reach better outcomes during the puzzle part?

Accumulate perks during a day and collect them based on the positive actions done at the end of the day. Each day has a limited numbers of perks that can be achieved and unlocked at the end.

Everytime you create and use a power-up (selecting it in level intro or creating it during the match), you accumulate points useful to take specific paths. If you want to take a specific path, then, you should create use more boosters in the puzzle game.

Start specific tasks by performing positive actions and get extra perks on completion. If the day ends, all the tasks are immediately completed.

Achievement system for positive actions with special resource to collect and use for special choices during the story.

Obtain extra personalization options if you manage to perform a certain number of positive actions.

At the end of an event, recount all the positive actions done and give extra perks according to the milestone. Giving the premium currency can be extremely valuable for the Players, but it may influence the monetization.

If the Player uses X boosters/power-ups/extra movements to beat a level and still loses, he is allowed to postpone that level for a while.

Conclusion

In a real context with a real team, all this process would be a workshop. Also, the study of top competitors is very important. This exercise is good to keep my mind fresh and to quickly play with narrative techniques I learnt in past weeks.