Ordered mode

Ordered mode

Normally, Raknetify2 lets independent packet channels continue while one channel waits for missing data. Ordered mode puts all Minecraft packets on one channel, so a missing packet holds up every later packet in that direction until it is retransmitted. This preserves the order expected by some anti-cheat software, but gives up Raknetify2’s ability to keep unrelated game traffic moving during that wait.

Enabling ordered mode

1. Install a Raknetify2 build that supports ordered mode on the server or proxy accepting RakNet connections and on each RakNet client.

2. Create config/raknetify2-compatibility.json relative to that server or proxy’s working directory. Create the config directory if it does not exist.

3. Add the following:

   {"mode": "ordered"}

4. Restart the server or proxy.

Clients follow the server’s setting automatically. Players do not need to create a configuration file or change their RakNet server address.

All Minecraft packets use one reliable ordered channel in each direction, including bundle delimiters and world transitions.

Proxy setups

When players connect through Velocity or BungeeCord, configure ordered mode on that proxy, even if the anti-cheat runs on a backend server.

The policy applies across backend switches. In ordered mode, the proxy forwards backend keepalive requests to the real client instead of answering them locally.

Checking the setting

On the first RakNet connection, the console reports:

Raknetify2 compatibility: ordered (updated clients required, genuine acknowledgements)

A successful compatibility exchange also logs ordered compatibility negotiated, followed by the peer’s address.

Keep anti-cheat checks enabled and validate your particular setup.

Older clients

RakNet clients that do not support ordered mode cannot connect to a server requiring it. Update Raknetify2 on those clients, or connect using the server or proxy’s normal TCP address and port without the raknet; prefix.

Returning to multichannel mode

Change the file to:

{"mode": "multichannel"}

Then restart the server or proxy. Removing the file also restores multichannel mode after a restart.

Configuration problems

The file must contain exactly one setting named mode, with either "ordered" or "multichannel" as its value. The values are case-sensitive.

Invalid or unreadable configuration rejects RakNet connections. Correct the file and restart the process.

If the console still reports multichannel, check that the file is in the working directory of the server or proxy accepting the RakNet connection, then restart that process.