Skip to content

Tag: howto

What I learned in the Playable Stories Workshop

Yesterday, I participated in a workshop on how to write for playable stories. It was a workshop oriented to professional game writers, and I am not. Still, I found it very useful in improving my skills in narrative design.

It was divided into 3 sessions, with pauses in the middle. Session one was about how games change stories. Session two was about how to make stories playable. The last one was about how to use the storytelling toolbox. The tools all writers have and also the tools that belong only to game writers.

The workshop was packed with practical insight and exercises to train for the next days. In Fall 2022, a company I worked for paid for my fee at the narrative department workshop. This gave me access to a series of interesting workshops at a special price. I am thankful for that.

On technical skills

Let’s talk about technical skills. I read a question around often and sometimes some students ask me: what skills should I have?

The question comes most of the time from our innate desire to fit (gregariousness, submission). There is a job market and we want to get in. This is fair.

As far as I’m concerned, the answer is like learning a new language. If there is no valid reason behind it, we will make a lot of effort to learn it. I learned English to better understand songs and video game stories. I learned Spanish to be able to live where I live. I learned Portuguese because of the culture and history behind Capoeira. I did learn because I felt would improve me as a person.

Likewise, the technical skills I decided to cultivate for game design come from there. Spreadsheets because I have always liked math and put things in order. The most common engines, especially for level design, because it puts me in a state of flow like when I play a video game. Game writing because, as you can see, I love writing. UX/UI because I don’t know how to draw, but I still like to arrange things visually as a form to clarify my ideas.

The question for me is not “which skills should I learn?”, but “which are the technical skills that can help me find my voice and let it come out?”

The main challenge of a professional game designer

It’s one thing to design a game (or a feature of a game) and another to sell it. This is perhaps the hardest lesson to learn during the career of a game designer.

It’s not just about thinking about systems, mechanics, development context. It’s also about convincing someone to go ahead.

  • If you have the funds, this someone can be a potential player. You have to convince them to play.
  • If you don’t have the funds, but you have a great idea, this someone can be a publisher or an investor.
  • If you work for someone, you have to convince them!

The key point is always in the expectations that one has about something.

  • “I will buy this game for 30 euros because I think I will have a fun time”
  • “I have to invest in this project because I see great possibilities of return”
  • “I approve this design because I think it is the right one for our game”

The biggest challenge is that creatives think on a different level than others.

I’ll give a concrete example with my game Pawtners Case. Lately I’ve been proposing it to try to finance it. It is perceived as a game that is too cheap, and so with little potential. It doesn’t matter that I propose something workable and scalable. Publishers prefer to focus more on something unachievable rather than go step-by-step.

A good use case for Claude.ai

I just paid for the premium subscription to Claude AI. Writing certain design documents took me 3-4 days. With Claude, 1-2.

Like every AI, it freaks out a lot. But this help me get started on tasks. I tell it to write me certain spec, it writes me something full of errors and that helps me think. It’s like teaching to a dumb student.

Then, when I have my document with wireframes, I pass it to it and first I tell it to act as a programmer. Again, it hallucinates but it helps me understand the “edge cases” the empty cases that I hadn’t thought of.

Finally, after a second iteration on the document, I send it again and ask to act as a quality assurance professional, to generate a test plan for me. This helps me think carefully about closing all the loose ends.

This is valuable. Indeed.

Playtest what’s wrong to find solutions

A good way to learn more about your game is to keep something that you see as problematic and playtest it. You will discover the obvious, that you need to fix it. But you will also understand much more things behind that.

It happened to me last week, I had the opportunity of running a playtest for my game. And for it I decided to create a specific control system. The developers said “we don’t feel it right”, and me neither.

At the playtest, everyone told me that the system was unconfortable. But I had to see their struggle to decide to take action in first place. In fact, I could notice how they handled the things and that helped me find the solution.

LLMs to spot design flaws

I just discovered another interesting use case for current LLM tools. I use Claude.ai at the moment it’s the best in class. I use the free version.

When you design on a document, let’s say a GDD or a one pager for a feature, you should cover the most possible edge cases. In this way, your coders will have everything pretty much clear by reading the document.

If you submit a document to Claude, then you can ask it to simulate the coding in Unity or Unreal Engine for that GDD. It will spit out pseudo code and reasonings. There will probably be lots of hallucinations and things unuseful. Still, there are good chances to discover something you didn’t considered.

Working in a team is self-discovery

Today I discovered something more about myself, thanks to the creative director of the project I am working on with a company.

I tend to not insist too much on my vision. I explain it, defend it, and usually that’s it. When I see too much resistance from the other side, if I have no real power over the decision, I desist and try to meet the boss’ vision.

This is good, but it can lead to a passive-aggressive way of communicating. “I will do like you say, but I do not agree”. At first it may seem like there’s nothing wrong with that, butthe issue is that:

  • it looks like a “ok, whatever” and can damage the relationship
  • it is vague, proposes no real solution, and can damage the project
  • It is not informative enough for the team to make choices on that

Today I have learn something more about myself. Something I want to fix. And that’s why I prefer to work within a team.

Job applications do not work

When I was 20 in Naples, it happened that I was with friends and we met unknown people. And we discover some party at a student’s house to sneak in. Sometimes it went well, others we would find ourselves with very different people. Among ourselves, sitting in a corner, sipping the same beer we had bought to join the party.

Today I don’t sneak in anywhere anymore. I like parties, but I prefer the comfort of being with people I already know. Sometimes I go to strangers’ houses, but in general I like to know a sufficient number of people.

The same goes for job hunting. I prefer having groups of friends in the industry and moving with them. I have a job right now because during the first months of my daughter’s life I played Fortnite at night and wanted to learn how to make levels. That’s how I met the person who then put me in the loop. This is the healthiest way to learn about realities and find opportunities.

What to do when you don’t know what to do?

Often it happens that your team is developing what you have defined in your design documentation. It happens that you don’t know specifically what to do next.

I use these moments to play competitor games and engage with their audience. I join Discord servers, lurk subreddits, and so on. I try to keep myself in the shoes of a Player of my references.

The second thing I do is to play the last build or the last code version intensively. As a game designer you need to be aware of what game is coming out.

I also keep ordered single big documents containing everything that has been already defined and implemented in the game. It is very useful to keep track of the vision and its progress.

Someone said “no” to LotR

The biggest Italian books publisher rejected The Lord of The Rings, many years ago. The first reaction I had when I saw this post the other day was from my belly.


But I had the time to reflect: to me, LotR is a masterpiece, but it has also a strong “personality”. It’s not an average story; you may like it or not for specific reasons.

Imagine to be the person in charge of selecting the best books. Something like this arrives, you read it and you like it. But its personality is very strong, and your role requires you to be cold and professional.

Today I can read these words and think that the decision maker made a mistake. But then I put myself in their shoes and it’s hard to make a decision with something like Tolkien’s book. A modern Tolkien can write tales in smaller formats on platforms like Substack. With nobody predicting if the text could be right for a specific geography.

It happens also with video games, I have to say especially to us game designers. Part of our responsibility is to pitch new ideas for features and mechanics. All companies have people in charge that filter our proposals. This process filters also good things out, it’s part of the game.

To design and produce you often need a sort of authorization from people in charge. These people, like you, make mistakes. The lesson you take can be that this is unacceptable, but often it’s a matter of communication. If something so special like The Lord of The Rings arrives on your desk, you can make errors. That’s why people that get a proposal should be prepared first.

I don’t know the full story, maybe the Tolkien’s agent just sent the book with a note. When you present something, the receivers should know all that from before. In that way, they will feel already connected and familiar to the thing.

Like new writers on Substack, leave crumbs and taste the environment!