What I did

  • Project management as Scrum Master
  • Traffic system in Blueprints
  • Created spreadsheet for calculating working hours

What I used

    About the project

      Mayor is a city management game made in the second year of my game development bachelor at IGAD. The game was made from concept to final product in a period of two and a half weeks as part of a so-called game marmalade (i.e. an extended game jam).

Scrum master

During a workshop I saw someone gathering the available hours of each team member as working/available/unavailable/ICE (available in case of emergency). I created a spreadsheet and requested each team member to fill it in. I added some color for readability and added a summary on the right.

On another worksheet I added a summary calculating the total number of hours available.

In the sprint planning and HacknPlan the metric used was hours, hence this was consistent everywhere

Traffic system

Because of my irregular schedule as a result of growing into the role of Scrum Master, I allowed myself to work only on aesthetic tasks to not become a bottleneck for others.

The task I spent most of my non-scrum-master time on was the traffic system, intended to bring some life into the scene.

The traffic node gizmos as seen in the editor

The inspector view on a traffic node actor

The city layout was not entirely grid-like (though every corner is a right angle). Because of this I settled on a pathing graph system. Each node in the graph knows to which neighboring nodes it is connected (a node is represented as a white sphere in the scene).

A central traffic manager is responsible for the spawning, updating, and despawning of the cars.

The inspector view on the traffic manager actor

The car actors themselves are actually all on the center of the street, but the model itself is offset to one side (kudos to the artist who inspired this simple and neat solution).