matthieu-vergne / distributed-mmorpg Goto Github PK

Actor models might be interesting to investigate:
https://doc.akka.io/docs/akka/current/guide/actors-intro.html

An efficient and secure communication P2P protocol should be designed. We can inspire from different resources:

• Le réseau dans les jeux vidéo (fr)
• Distributed ledger
• Matrix

• Create a minimal multiplayer game
  • Window showing world (GUI + data)
  • Avatar to move on it (world interaction)
  • Leave & reload (world persistence)
  • 2 players on same world (multiplaying)
  • Separate playing + merging (data integrity)
• Manage world distribution
  • GUI process + world process (client + server)
  • Distributed data (1 remote server + 2 local client-server pairs)
• Identify basic, network-friendly strategies to world evolutions
  • Cut & plant trees (player interaction)
  • Evolving trees (self-evolution)
    • Growing trees (local evolution)
    • Spreading trees (global evolution)
• Manage scalability
  • TODO...

Resources to be studied:

• https://martinfowler.com/articles/patterns-of-distributed-systems/
• http://highlyscalable.wordpress.com/2012/09/18/distributed-algorithms-in-nosql-databases/

Find a way to manage community updates.

An author should be able to:

• make an update (add/replace/delete)
• propose it to other players

A player should be able to:

• know that another player propose an update
• know its content
• understand its impact
• choose it (accept/reject)
• change its choice at any time

An update can be on anything considered worth to be managed by the community, among which:

• the code
• the content
• the decision rules

This project aims to produce a game distributed over a set of peers. So we need to assume that disconnection from all or some other peers shouldn't be a threat, but a nominal situation. Playing the game should be possible from alone to massively connected. Thus we need to establish how disconnection can be exploited rather than feared.

It can be part of the gameplay, so involuntary disconnections should be events manageable in the game. However, if the gameplay uses them, then voluntary disconnections should also be possible for those who want an extensive use of them.

If you are reading this thread, please feel free to suggest possible exploitations of these disconnections, so we can think about a proper way to design disconnection management.

We may reuse existing graphics, like the ones provided by EasyRPG. As long as the license allows it, any other would be fine.

To identify other instances on the network, we may use certificates/signatures, with public-private keys and all this stuff.
Resources to investigate to manage it properly:

• https://www.baeldung.com/keytool-intro