General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "David P. Reed" <dpreed@deepplum.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] FW: [Dewayne-Net] Ajit Pai caves to SpaceX but is still skeptical of Musk's latency claims
Date: Sun, 14 Jun 2020 02:02:34 +0300	[thread overview]
Message-ID: <F8A2AF1C-EFF9-4EC2-93F1-6FAAE69F8517@gmail.com> (raw)
In-Reply-To: <7056.1592082916@localhost>

> On 14 Jun, 2020, at 12:15 am, Michael Richardson <mcr@sandelman.ca> wrote:
> 
> They claim they will be able to play p2p first person shooters.
> I don't know if this means e2e games, or ones that middlebox everything into
> a server in a DC.  That's what I keep asking.

I think P2P implies that there is *not* a central server in the loop, at least not on the latency-critical path.

But that's not how PvP multiplayer games are typically architected these days, largely due to the need to carefully manage the "fog of war" to prevent cheating; each client is supposed to receive only the information it needs to accurately render a (predicted) view of the game world from that player's perspective.  So other players that are determined by the server to be "out of sight" cannot be rendered by x-ray type cheat mods, because the information about where they are is not available.  The central server has full information and performs the appropriate filtering before replicating game state to each player.

Furthermore, in a PvP game it's wise to hide information about other players' IP addresses, as that often leads to "griefing" tactics such as a DoS attack.  If you can force an opposing player to experience lag at a crucial moment, you gain a big advantage over him.  And there are players who are perfectly happy to "grief" members of their own team; I could dig up some World of Tanks videos demonstrating that.

It might be more reasonable to implement a P2P communication strategy for a PvE game.  The central server is then only responsible for coordinating enemy movements.

 - Jonathan Morton


  reply	other threads:[~2020-06-13 23:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 16:03 David P. Reed
2020-06-11 16:14 ` Jonathan Morton
2020-06-11 18:46   ` David P. Reed
2020-06-11 18:56     ` David Lang
2020-06-11 19:16       ` David P. Reed
2020-06-11 19:28         ` David Lang
2020-06-12 15:39           ` Michael Richardson
2020-06-13  5:43             ` David Lang
2020-06-13 18:41               ` David P. Reed
2020-06-14  0:03                 ` David Lang
2020-06-14  0:36               ` Michael Richardson
2020-06-14  1:17                 ` David Lang
2020-06-14 15:40                   ` David P. Reed
2020-06-14 15:57                     ` Michael Richardson
2020-06-14 21:04                       ` David P. Reed
2020-06-14 23:13                         ` Michael Richardson
2020-06-12 15:30     ` Michael Richardson
2020-06-12 19:50       ` David P. Reed
2020-06-13 21:15         ` Michael Richardson
2020-06-13 23:02           ` Jonathan Morton [this message]
2020-06-14  0:06           ` David Lang
2020-06-14 11:23   ` Roland Bless

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F8A2AF1C-EFF9-4EC2-93F1-6FAAE69F8517@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=mcr@sandelman.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox