TECH Signal 504
RuneScape's 2004 client packed a 3D multiplayer world into 56k dial-up using a 600ms tick
↗
A 2004 RuneScape client fit a 3D multiplayer RPG into 56k dial-up by using a 600ms server tick, a single TCP connection, and ISAAC-encrypted opcodes.
This shows how to design a networked game for extreme bandwidth constraints, where every byte counts. The approach of encrypting only the opcode and using a length byte for variable packets is a lesson in minimal protocol design. It also demonstrates that a browser-based Java applet can handle real-time multiplayer with careful engineering.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
RuneScape's 2004 client used a 600ms server cycle to determine what each player can see and send updates.
The client encrypted only the opcode byte with ISAAC, leaving the packet body unencrypted.
The client ran in a Java applet with no UDP, so all traffic went over a single TCP connection.
THE CLUSTER