Play + Crit

Game A

MPGaH III

Remember:

A conflict happens when multiple clients write to the same shared object at “the same time” so that's what you need to avoid.

You won’t have a conflict when:

• only a single client writes to a particular shared object, even if frequently
• multiple clients only read from a shared object at the same time
• multiple clients write to different shared objects at the same time
• multiple clients write to the same shared object, but not at the same time

Pattern: Participant Shared

Create a shared object for each participant, and design your game so that participants only write to their own shared object.

p5.party supports this pattern by automatically creating a shared object for each client that connects, removing that object when the participant disconnects, and providing you an array of all the objects for currently connected participants.

partyLoadGuestShareds()

partyLoadMyShared()

p5.party Example

Intro: Press Kit