diff options
| author | Osmium Sorcerer <os@sof.beauty> | 2026-03-22 17:50:28 +0000 |
|---|---|---|
| committer | Osmium Sorcerer <os@sof.beauty> | 2026-03-29 22:22:25 +0000 |
| commit | 173c52f87d9519f2462c6f33a500cea005b71ada (patch) | |
| tree | ab84e970c7bb81a679acba4c92569e6731ee81dc | |
| parent | f7dc5daa20bf943fdd824ff2aa1b408f1bc239b9 (diff) | |
Remove sending CT on server join
Strange idea, no realization. Trying to set up a "username requirement"
is antithetical to AO's pseudonymous nature. At least, CT packet is not
the way to do this: nothing guarantees its uniqueness, it's prone to
spoofing if we can send arbitrary CT messages at some point during the
handshake, and not everyone has their OOC names preconfigured.
It was never meant to be. Delete it.
| -rw-r--r-- | src/packet_distribution.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/packet_distribution.cpp b/src/packet_distribution.cpp index 066fc6b..5c9cd17 100644 --- a/src/packet_distribution.cpp +++ b/src/packet_distribution.cpp @@ -288,8 +288,6 @@ void AOApplication::server_packet_received(AOPacket packet) send_server_packet(AOPacket("RD")); - // TODO : Implement username messaging and requirement server-side properly. - send_server_packet(AOPacket("CT", {Options::getInstance().username(), ""})); log_to_demo = false; } else if (header == "FM") // Fetch music ONLY |
