upbeatDiamond
commented
9 months ago Well, IPFS is a file system first and foremost, meaning that writing from one person, and then reading from another would likely be a bit slow. Even if it's not, that sounds cumbersome to implement, and would be better used (if at all) for storing a list of fully-public servers.
Consider the following, or any similar apps to the following:
I was thinking about writing up something quick, but seeing as I'm currently busying myself with language parsing, pathfinding, and the mere concept of multiplayer, I don't have time or skill enough to create and then distribute a solution.
The ideal multiplayer interface would enable LAN, F2F, and after passing through some dark patterns, WAN P2P.
The solution should be fast enough to carry all packets regarding player movements, battle requests, etc, but solid enough that I can play with anyone and not be able to tell where they live more precisely than what hemisphere they're likely playing in.
It needs to carry both remote procedure calls (Godot functions send via interweb), and allow for chat and map sharing, which is allowed to be a lot slower.