Categories
Game Design Villanostra

Subtle Changes

Continuing my solo playtest with threats. Their impact is rather subtle so far, but that’s kind of intentional. The first reason is that until buildings are completed, nothing can be done about the threats. The second reason is that in the real world, humans tend to ignore threats until they cost too much to ignore: I want the players to argue about who will pay the cost to deal with the threats, when all they really want to do is make their own buildings.

Solo 3-councilor playtest. Starting the build phase of year 4.

Still, the threats need to be credible if they’re going to impact the game. I’m not sure I can determine their credibility in a solo playtest. I told Karen this morning that this game is getting harder and harder to solo playtest, because the decisions are becoming increasingly complex, even though the mechanisms are more elegant than they have ever been. This pleases me.

Also: At Protospiel Online, Amelie Le-Roche suggested that I try putting newly selected buildings at the front of the build line instead of the back. I’ve been pondering this. It means that if your building isn’t completed the year it’s selected, it will be much harder to complete it before the game ends. That sounds interesting.

Categories
Game Design Villanostra

New Threats

First Villanostra solo playtest with the new threat mechanism. At the start of each year, randomly select morals equal to the number of players, and increase each corresponding threat. Any councilor can apply influence to a completed building to reduce the corresponding threats.

Categories
Game Design Villanostra

Massive Changes

In the span of slightly more than one week, Villanostra has gone from this:

To this:

By focusing on the most important aspects of the game–voting on buildings and influencing workers to build them–I dramatically reduced the ruleset, play time, and component count. A three-player test session went from being unfinishable in two hours to completing in 45 minutes (including time for teaching rules and post-game analysis). Ideas from playtesters led to combining the voting and influence tokens, which led to each councilor having distinct moral-based abilities, which also resolved issues with ally selection. The whole game feels more smooth and elegant. Playtesters were enthusiastic.

Next step: Add mechanisms that threaten the village as a whole. I now have some confidence that I can do so without making the game too heavy for the players I want.

Thanks to all my Protospiel Online playtesters for your time, thoughts, and encouragement!

And thanks to The Pitch Project for putting me through the sell sheet process, which helped me clarify and focus upon the core of the game.

Categories
Game Design Villanostra

Simple Threats

I just finished a three-year playtest of Villanostra, after hacking out lots of the mechanisms and adding in annual moral-based threats. The threats are simplistic: they all do the same thing, no matter what moral is drawn. But they can only be alleviated by spending effort from a building associated with the moral. That worked… okay. It still led to some interesting choices, even though the buildings were effectively all identical. I’m torn, because I want the threats and buildings to feel distinct, but the game already takes so long to play that I’m scared to add any more complexity.

I tried at first having each councilor care only about their primary moral, with no secondary / sympathy morals. That created a lot of situations where a councilor had no motivation to act at all, so I added the secondary morals back in.

I tried starting with random villagers. That created an ongoing situation where one councilor had no influence on any villager, which was intolerable. So I went back to having each councilor choose a starting villager. But I’d like to always start with 3 villagers, so that’s not a great solution. For the next playtest, I’m removing every villager that none of the players can influence, but that doesn’t guarantee that each councilor will always have a matching villager in play. Ugh.

I changed scoring to occur only at the end of the game (three years, for now). I’ve also added a rule that each player’s score is reduced by the number of villagers having more than 4 stress. The Judge scored 7 points, The Priest and the Doctor each scored 3. 10 points seems like a good target.

Categories
Career Game Design UX Engineer

Game Design as Acquired Skill

This was shared with me and I want to be able to find it again. It certainly applies to interaction design / UX design / front-end development as well.

Categories
Game Design Villanostra

The Right Tool

This morning I started a Villanostra sell sheet, as my submission for The Pitch Project. This is what I have so far. I was just getting ready to set up columns for the rest of the layout when my spouse (and graphic design mentor) looked at it.

She said “You should be using InDesign for this instead of Illustrator. Illustrator is for drawing, InDesign is for layout. If you try to use Illustrator for layout, you will hate your life.” And she’s right. So I know where I’ll be picking up tomorrow.

Categories
Game Design Villanostra

Stripping Down

Saturday’s playtest confirmed that Villanostra has become far more complex than is practical. It took over an hour to play a single year. So this morning I stripped out all the components that didn’t seem essential. Here’s what the game looked like Saturday morning:

And here’s what it looks like now:

This will require substantial rules changes, of course. But it has already led to some interesting ideas. One of my biggest struggles with this design has been to represent the morals, so each of them feels important in a different way. I have been trying to demonstrate their value through the buildings, but I think instead I should be demonstrating their value through threats to the village. My next step is to make event cards that are drawn each year, each representing a threat that can be ameliorated by one of the morals. Then I can give each building an ability to deal with its matching threats.

Categories
Career UX Engineer

What Prototyping Tool?

I am getting some contacts about business analysis jobs. It’s hard to ignore opportunities for paying work. But it’s abundantly clear that from a career perspective, BA work is not going to take me where I want to go. So I’ve decided to respond to those requests by asking, “What prototyping tool would I be using for this position?”

Categories
Game Design Villanostra

Does that seem fair?

New solo playtest. At the end of year 1, all players but Red have 1-2 points. Red has 16. Problem?

Uh, yeah. Here are some rules I used in this playtest that were contributing factors:

  • First solo playtest of a four-councilor game. The (untested) rule for distribution of Sympathy cards was to deal them all out at random. If you get your own, deal with it.
    • Note that Red got two of their own, so any advantage they get in scoring is multiplied.
    • Also note that everyone has 3 Sympathy cards instead of just 2. So Red’s multiplier for their own moral is 4 rather than 3.
  • Random selection of starting villagers. Kelly and Lee gave Red 4 pips right out of the gate. Green had 2, Blue and White had none.

There’s no point continuing this playtest. I still want to try random starting villagers, but I’ve changed the four-councilor Sympathy card rule to match what I’ve been using for three councilors: you get one of the unplayed councilors at random, plus the councilor to your left.

Other than that, lots of positive improvements! I like the new village grid. The community support and stress rule already looks good. And the new Building card visual design already looks a lot better.

Categories
Career UX Engineer

Continuing React, and Indy.js

Today I continued working through React lessons in FreeCodeCamp. Didn’t make it all the way through. Lots of non-intuitive stuff that is forced by making accommodations into kludges against EcmaScript syntax. I’m glad I have enough of a CS background to see why some of the more confusing things must work the way they do. But React is still a massive kludge, however useful it is.

I also attended my first meeting of the Indy.js meetup. There were four very informal lightning talks, and some chatting afterward. Again, even when I don’t follow everything they’re saying, I feel more comfortable with the developers than the designers. I also learned that there’s a very active FreeCodeCamp community in Indy, so I’ll be looking into that.

Oh, and I applied to some developer jobs and places I think would be good to work. I’m not as prepared for those jobs as I’d like, but they have openings NOW so I need to apply NOW. And keep learning.