• Welcome to Valhalla Legends Archive.
 

[VB] Diablo 2 Gameing

Started by Celica, December 28, 2002, 09:55 AM

Previous topic - Next topic

Celica

Isnt MCP UDP? Or is it TCP?

Mesiah / haiseM

#1
tcp IIRC, but i dont play or have anything to do with those super lame diablo games...
]HighBrow Innovations
Coming soon...

AIM Online Status: 

Yoni

#2
Everything related to Diablo 2 and Battle.net is TCP/IP.

Grok

#3
Are you sure?  <grin>

Yoni

#4
Yes. I think so. Hmm. No. :(
What'd I forget?

Grok

#5
ICMP?

Yoni

#6
Blizzard's Diablo 2 client uses ICMP?

Yoni

Hmm... I did forget DNS though, which is probably UDP. :o

Grok

#8
When you "fps" in game, does it not show ping?

Mesiah / haiseM

#9
grok is so wise :P
]HighBrow Innovations
Coming soon...

AIM Online Status: 

Skywing

#10
QuoteWhen you "fps" in game, does it not show ping?
That could be from a ping-like message in their protocol, similar to how Starcraft/Battle.net Chat do ping, rather than ICMP.

Yoni

#11
QuoteWhen you "fps" in game, does it not show ping?
Mine shows nothing.

Never figured out why. :(

Zakath

#12
Yoni, maybe Blizzard doesn't like you. I still have that screenshot of the totally screwed up graphics from the War3 demo! ;D
Quote from: iago on February 02, 2005, 03:07 PM
Yes, you can't have everybody...contributing to the main source repository.  That would be stupid and create chaos.

Opensource projects...would be dumb.

Yoni

#13
lol :)
That was the Voodoo Banshit's fault.  I've gotten a better graphics card since, and Warcraft 3 runs fine now.

I think Diablo 2 worked better (and the fps command worked) with the old card though... But it would freeze the entire system every few hours, or few minutes in some places.

Noodlez

#14
sky = correct