Ignorance of the physical layer? Your thought is that bungie has a check that can sense any voltage loss? So when we disconnect it shows up as a voltage loss?

Go and read my post again. It's funny that you're getting defensive about it tho. To answer your question; which is so ridiculous I have to believe you actually think you understood what I'm saying. What is most likely happening at the ethernet port is:

is eth0 connected?
 >yes. then loop.
  >no. then pass up the stack OSIorTCP/IP stack to app layer and kick from XBL   

Also, in UDP the sender doesn't worry about the connection, it just shits out packets and hopes they get there. The receive side does error checking to know what packets made it. UDP provides error checks, but not error recovery. So the recieve side can check against the header and checksum and see a packet was lost, but it cannot retrieve that packet, hence the "connectionless"

Relevance? You didn't make a point or correct anything I've said.

If there was no check going on then they would have no idea if someone disconnected, or what their "ping" strength was.

You have conflated connection orientated protocols with the ICMP echo request/reply that is known as ping.

So I think you don't entirely understand connection protocols, or what goes I to error checking while hosting multiple clients (or even a single p2p connection).

You're drunk go home.

And in addition to all of that, there is no way it is pure UDP but more than likely a combination of TCP ad UDP where voice and server connection(for gear, items, lobby info) are handled by TCP and character movement and object data is sent via UDP. You always have to be connected to the bungie server for gear and such, and that most deff uses TCP.

I am not suggesting there are no connection orientated protocols at work in destiny. In fact, you regurgitated what I just suggested in my last comment. For convenience I've copied it here.

Got any proof their using a connectioned orientated protocol? Most games (counter strike, etc) rely on the UDP protocol, which is connection-less. Maybe Bungie has devised an application layer check to see if packets are received normally. Tho I doubt it, as any checks like this significantly increase latency and player upstream overhead. Maybe they have? That could explain the cornucopia of error codes in their help database. I still want some sauce for it tho.

Furthermore, you're muddying the waters by bringing topics that are not PvP. Voice chat? Not PvP. Inventory? Not PvP. Lobby info? Debatable, tho surely not in any way related to the lag experienced in firefights. I can agree that player profiles and histories are maintained by Bungie servers, where else could they be? But you're driving away from the topic of lag in firefights. Is it because TCP is used to confirm damage dealt? Are people invincible because they're dropping all the packets saying they're dead?