Re: Your 1st point. Why do you say to not use WebRTC for web games? The official docs suggest the opposite (link):
WebRTC is implemented in Godot via two main classes WebRTCPeerConnection and WebRTCDataChannel, plus the multiplayer API implementation WebRTCMultiplayer. (...) These classes are available automatically in HTML5, but require an external GDNative plugin on native (non-HTML5) platforms.
Hi all. I'm interested in making a Tetris Attack (TA)-like pvp game for the browser. The only hard requirement is to be playable with people across the globe, i.e. high latency. It'd be nice to have 4-player multiplayer too, but not essential.
The gameplay itself requires very low latency, multiple moves per second, but the multiplayer interactions less so. If you're familiar with TA, you'll know there's basically one signal sent between players - new boulder of size X. So in order to deal with high latency from the network I plan to make each player's own state mostly local and transmit the attack signal with high priority. Each player will also receive the opponent's state but at a lower priority/higher interval.
My first idea is to build it as p2p where one player hosts. I came across this article that looks like a decent start: https://perons.writeas.com/creating-a-peer-to-peer-snake-game-with-godot-webrtc
I have no godot or game dev experience. I have some web dev experience but not with webrtc. This sounds like an awful lot for a weekend so I'm thinking if I'm just able get two players to communicate state that's a win!
