IRCLogs • ArmaNelgTron.tk

Searching from 2023-08-17 00:00:00 to 2023-08-17 23:59:59.999999.
Query completed in 0.46 seconds
[2023-08-17 05:54:30] --> monr0e has joined the channel
[2023-08-17 10:20:47] <-- monr0e has quit (Ping timeout: 245 seconds)
[2023-08-17 10:39:31] --> monr0e has joined the channel
[2023-08-17 13:40:32] <armagetron-bridge> 12discord:zman_0| @northernscrub I don't fully understand what you are suggesting. We have one case where the server rewrites history, it's the "zero rubber death". If ping charity is a thing an a high ping player cuts a low ping player, because the high ping player's timer runs late on the server, the server only notices that after the low ping player has already passed. If possible, the low ping <clipped message>
[2023-08-17 13:40:32] <armagetronbridge> 12discord:zman_0| @northernscrub I don't fully understand what you are suggesting. We have one case where the server rewrites history, it's the "zero rubber death". If ping charity is a thing an a high ping player cuts a low ping player, because the high ping player's timer runs late on the server, the server only notices that after the low ping player has already passed. If possible, the low ping <clipped message>
[2023-08-17 13:40:32] <armagetron-bridge> 12discord:zman_0|  player is then reset to the position of the cut. If the low ping player has turned in the meantime, though, that is no longer possible and the low ping player is just killed.
[2023-08-17 13:40:32] <armagetronbridge> 12discord:zman_0|  player is then reset to the position of the cut. If the low ping player has turned in the meantime, though, that is no longer possible and the low ping player is just killed.
[2023-08-17 13:45:35] <armagetronbridge> 12discord:zman_0| Generally, I tried to follow these principles. They're not the only possible ones!
[2023-08-17 13:45:36] <armagetron-bridge> 12discord:zman_0| Generally, I tried to follow these principles. They're not the only possible ones!
[2023-08-17 13:45:36] <armagetron-bridge> 12discord:zman_0| 1. The server has the absolute truth.
[2023-08-17 13:45:37] <armagetronbridge> 12discord:zman_0| 1. The server has the absolute truth.
[2023-08-17 13:45:37] <armagetron-bridge> 12discord:zman_0| 2. Clients have two, and only two, versions of the truth: Their own preliminary truth, guided by the player input that has not yet made the round trip to the server. And the remote truth, the copy of the server's truth that it gets with syncs.
[2023-08-17 13:45:38] <armagetronbridge> 12discord:zman_0| 2. Clients have two, and only two, versions of the truth: Their own preliminary truth, guided by the player input that has not yet made the round trip to the server. And the remote truth, the copy of the server's truth that it gets with syncs.
[2023-08-17 13:45:39] <armagetron-bridge> 12discord:zman_0| 3. The server tries to make the absolute truth as close to the client's preliminary truth as the rules allow.
[2023-08-17 13:45:39] <armagetronbridge> 12discord:zman_0| 3. The server tries to make the absolute truth as close to the client's preliminary truth as the rules allow.
[2023-08-17 13:45:40] <armagetron-bridge> 12discord:zman_0| 3. Clients will try to reconcile their preliminary truth with the remote truth, but very cautiously. Any corrections (slides) are disorienting. You don't want them to go this way, then the other way because the client was overcompensating first.
[2023-08-17 13:45:41] <armagetronbridge> 12discord:zman_0| 3. Clients will try to reconcile their preliminary truth with the remote truth, but very cautiously. Any corrections (slides) are disorienting. You don't want them to go this way, then the other way because the client was overcompensating first.
[2023-08-17 13:45:41] <armagetron-bridge> 12discord:zman_0| Yeah, I dunno where I was going there and what the relevance was 🙂
[2023-08-17 13:45:42] <armagetronbridge> 12discord:zman_0| Yeah, I dunno where I was going there and what the relevance was 🙂
[2023-08-17 14:08:49] <armagetronbridge> 08discord:delinquent| I have to confess, I'm having some trouble putting what I'm seeing in my head into words. However, I'm starting to see that any implementation of what I'm thinking of would require more client trust, which may not be a good idea. It might be possible to mitigate that somewhat... maybe? In short, the objective would be to rely more on timestamped orientation and positioning as dic <clipped message>
[2023-08-17 14:08:50] <armagetron-bridge> 08discord:delinquent| I have to confess, I'm having some trouble putting what I'm seeing in my head into words. However, I'm starting to see that any implementation of what I'm thinking of would require more client trust, which may not be a good idea. It might be possible to mitigate that somewhat... maybe? In short, the objective would be to rely more on timestamped orientation and positioning as dic <clipped message>
[2023-08-17 14:08:50] <armagetron-bridge> 08discord:delinquent| tated by the client, but it would also be easy enough to hijack this to change positions and wall placement after the fact. 
[2023-08-17 14:08:50] <armagetronbridge> 08discord:delinquent| tated by the client, but it would also be easy enough to hijack this to change positions and wall placement after the fact. 
[2023-08-17 14:08:51] <armagetron-bridge> 08discord:delinquent| Maybe compression is the answer. Or maybe marking armagetron traffic with as many different priority indicators as possible could help. Discord already does this, some netgear users will attest to it.
[2023-08-17 14:08:52] <armagetronbridge> 08discord:delinquent| Maybe compression is the answer. Or maybe marking armagetron traffic with as many different priority indicators as possible could help. Discord already does this, some netgear users will attest to it.
[2023-08-17 15:07:30] <armagetronbridge> 14discord:monkey_arma| "Or maybe marking armagetron traffic with as many different priority indicators as possible could help"
[2023-08-17 15:07:30] <armagetron-bridge> 14discord:monkey_arma| "Or maybe marking armagetron traffic with as many different priority indicators as possible could help"
[2023-08-17 15:07:30] <armagetron-bridge> 14discord:monkey_arma| I think I like this idea a lot.
[2023-08-17 15:07:31] <armagetronbridge> 14discord:monkey_arma| I think I like this idea a lot.
[2023-08-17 15:08:38] <armagetronbridge> 12discord:zman_0| Yeah, me too. Is there a standard API way to do that? I looked into it waaaay back, and then the concept barely existed, let alone ways to access it from a sending application.
[2023-08-17 15:08:38] <armagetron-bridge> 12discord:zman_0| Yeah, me too. Is there a standard API way to do that? I looked into it waaaay back, and then the concept barely existed, let alone ways to access it from a sending application.
[2023-08-17 15:15:37] <armagetronbridge> 12discord:zman_0| There seems to be a way with setsockopt:
[2023-08-17 15:15:37] <armagetronbridge> 12discord:zman_0| https://stackoverflow.com/a/70623636
[2023-08-17 15:15:37] <armagetron-bridge> 12discord:zman_0| There seems to be a way with setsockopt:
[2023-08-17 15:15:38] <armagetron-bridge> 12discord:zman_0| https://stackoverflow.com/a/70623636
[2023-08-17 15:15:38] <armagetronbridge> 12discord:zman_0| https://groups.google.com/g/libuv/c/8b0lvUqnGaM?pli=1
[2023-08-17 15:15:39] <armagetron-bridge> 12discord:zman_0| https://groups.google.com/g/libuv/c/8b0lvUqnGaM?pli=1
[2023-08-17 15:24:00] <armagetronbridge> 08discord:delinquent| If you figure out a way to set dscp to 101, I'll install that branch on the fort/sumo pickup servers that I host
[2023-08-17 15:24:01] <armagetron-bridge> 08discord:delinquent| If you figure out a way to set dscp to 101, I'll install that branch on the fort/sumo pickup servers that I host
[2023-08-17 16:53:25] <-- monr0e has quit (Ping timeout: 245 seconds)
[2023-08-17 23:14:21] <-- Z-Man has quit (Ping timeout: 250 seconds)
[2023-08-17 23:14:39] --> Z-Man has joined the channel
View entire month
DISCLAIMER: These logs of public chat may contain some content which may not be appropriate for all audiences. Use at your own risk.
Logs from 2006-2009 pulled from wrtlprnft
Format changes at: 2015-08-25, 2017-02-20, and 2020-03-23. Times (2015 and later) should be Eastern.
. [About this site] [Credits]