Browser vim plugin prevents me from playing.
Show HN: I Built Multiplayer Deathmatch Joust
51–60 of 107 posts
Re: Show HN: I Built Multiplayer Deathmatch Joust
#52Most of this code dates back to 1998, when I built a little 2 player Joust game to push the bounds of what you could do with Div (and at the time Layer) tags in the latest browsers such as IE4 and Netscape 3. Surprisingly, most of it still worked when I thawed it out recently, provided your browser knew about document.all. Over the weekend, I brought it up to date a bit and introduced it to Socket.io. Thus far it has…
Re: Show HN: I Built Multiplayer Deathmatch Joust
#53Re: Show HN: I Built Multiplayer Deathmatch Joust
#54Re: Show HN: I Built Multiplayer Deathmatch Joust
#55Re: Show HN: I Built Multiplayer Deathmatch Joust
#56HN gentle hug of death.
On a tech site like this can we please bring 'slashdotted' as the verb to describe a non-malicious DDoS? /. atleast earned the right to coin the term.
Re: Show HN: I Built Multiplayer Deathmatch Joust
#57Re: Show HN: I Built Multiplayer Deathmatch Joust
#58See also: Killer Queen (and Killer Queen Black)
Re: Show HN: I Built Multiplayer Deathmatch Joust
#59Most of this code dates back to 1998, when I built a little 2 player Joust game to push the bounds of what you could do with Div (and at the time Layer) tags in the latest browsers such as IE4 and Netscape 3. Surprisingly, most of it still worked when I thawed it out recently, provided your browser knew about document.all. Over the weekend, I brought it up to date a bit and introduced it to Socket.io. Thus far it has…
I remember making a CGI (that's an ancient, simple server backend for the young-ins) IM chat in 1996. It used the keep connection open trick present in HTTP 1.0 and a tiny bit of Netscape JS.
Re: Show HN: I Built Multiplayer Deathmatch Joust
#60Most of this code dates back to 1998, when I built a little 2 player Joust game to push the bounds of what you could do with Div (and at the time Layer) tags in the latest browsers such as IE4 and Netscape 3. Surprisingly, most of it still worked when I thawed it out recently, provided your browser knew about document.all. Over the weekend, I brought it up to date a bit and introduced it to Socket.io. Thus far it has…
If you can figure out a way to only send inputs for each player instead of their full state, it should significantly reduce network traffic and lag for each player-- right now it's sending ~1KB/frame!