In this 2018 GDC session, Spry Fox‘s Daniel Cook explains how to keep human beings from being treated as interchangeable, disposable, or abusable when designing multiplayer games.
If you’re developing, or thinking about developing a multiplayer game, this is a great talk to better understand the challenges of designing multiplayer interactions that result in more engagement and player satisfaction.
Daniel talks about the potentially negative social effects of multiplayer implementations, the effects of proximity, propinquity, serendipity, and density on people’s relationships, the logistics of forming new friendships in games out of strangers.
He covers basics like persistent identities (and repeat encounters), events (and their density), daily incentives, and offline communities as well as anti-patterns such as anonymous players, empty spaces, too many gameplay modes, and separation of players by skill. He also talks about the challenges of matches and matchmaking, which often necessitate large amounts of concurrent players to be viable, and the issue of matchmaking queue churn, resulting in low repeat interactions. The talk also covers the topic of similarities; tribalism, nationalism, their negative effects, and how to work with similarities in a positive context through fictional places and cultures. Daniel speaks to reciprocity, how it levels up relationships by building trust for more meaningful and deeper interactions, and the challenges of building trust, which is easily destroyed by cheating, scamming, or even premature disclosure which then kills relationship leveling.
I think the whole talk is fantastic, but the friendship levels of solitary play, parallel play, ambient/accidental coop, soft coop, and hard coop, are something any multiplayer game designer should think about because designing games around those different levels can have far-reaching effects and give games the proper appeal they need to grow and thrive.
The low trust, medium trust, and high trust Venn diagrams of increasingly more discrete player skills can also be found on Raph Koster’s website in his post about The Trust Spectrum. It’s a great read. The topics apply to all games, but it makes me appreciate Deep Rock Galactic even more for its well-thought-out design.
I find it funny that Daniel calls out retrofitting a social architecture as hard because I define architecture fundamentally as “that which is difficult to change later.” The context or nature of the architecture is usually less important.
This inventory system release refines a lot of architecture guide sections based on customer feedback and adds over 100 additional pages to the PDF guide. Features: Bug fixes:
This release contains the new Godot editor integrations. It offers an Item Library bottom panel that makes it easier to manage your inventory item types, and an inspector plugin that lets you edit items in a GGItemCollection. This also reduces the need for manually creating GGItemData resources, which simplifies item management at design time significantly. …
Need optimized export templates with PCK encryption support but don’t want to have to set up a build pipeline or download the entire compilation toolchain on your computer? Well, now it is. Fill out the form, checkout, and we’ll email you the download link after the compilation completes. Compilation may take 30 minutes to 3 …
Design Patterns for Building Friendships
In this 2018 GDC session, Spry Fox‘s Daniel Cook explains how to keep human beings from being treated as interchangeable, disposable, or abusable when designing multiplayer games.
If you’re developing, or thinking about developing a multiplayer game, this is a great talk to better understand the challenges of designing multiplayer interactions that result in more engagement and player satisfaction.
Daniel talks about the potentially negative social effects of multiplayer implementations, the effects of proximity, propinquity, serendipity, and density on people’s relationships, the logistics of forming new friendships in games out of strangers.
He covers basics like persistent identities (and repeat encounters), events (and their density), daily incentives, and offline communities as well as anti-patterns such as anonymous players, empty spaces, too many gameplay modes, and separation of players by skill. He also talks about the challenges of matches and matchmaking, which often necessitate large amounts of concurrent players to be viable, and the issue of matchmaking queue churn, resulting in low repeat interactions. The talk also covers the topic of similarities; tribalism, nationalism, their negative effects, and how to work with similarities in a positive context through fictional places and cultures. Daniel speaks to reciprocity, how it levels up relationships by building trust for more meaningful and deeper interactions, and the challenges of building trust, which is easily destroyed by cheating, scamming, or even premature disclosure which then kills relationship leveling.
I think the whole talk is fantastic, but the friendship levels of solitary play, parallel play, ambient/accidental coop, soft coop, and hard coop, are something any multiplayer game designer should think about because designing games around those different levels can have far-reaching effects and give games the proper appeal they need to grow and thrive.
The low trust, medium trust, and high trust Venn diagrams of increasingly more discrete player skills can also be found on Raph Koster’s website in his post about The Trust Spectrum. It’s a great read. The topics apply to all games, but it makes me appreciate Deep Rock Galactic even more for its well-thought-out design.
I find it funny that Daniel calls out retrofitting a social architecture as hard because I define architecture fundamentally as “that which is difficult to change later.” The context or nature of the architecture is usually less important.
This talk also reminds me of Penny Arcade’s Greater Internet F***wad Theory, which is soon coming up on its 20th anniversary.
Related Posts
Inventory System v1.15 available
This inventory system release refines a lot of architecture guide sections based on customer feedback and adds over 100 additional pages to the PDF guide. Features: Bug fixes:
Inventory System v1.4.1 available
This small update addresses inventory serialization to persist the allow_gaps and expiration_multiplier settings. These were previously overlooked.
Inventory System 2 Alpha 2 available
This release contains the new Godot editor integrations. It offers an Item Library bottom panel that makes it easier to manage your inventory item types, and an inspector plugin that lets you edit items in a GGItemCollection. This also reduces the need for manually creating GGItemData resources, which simplifies item management at design time significantly. …
Introducing GodotBuilder: Custom Export Templates built on demand
Need optimized export templates with PCK encryption support but don’t want to have to set up a build pipeline or download the entire compilation toolchain on your computer? Well, now it is. Fill out the form, checkout, and we’ll email you the download link after the compilation completes. Compilation may take 30 minutes to 3 …