| *** disco <disco!~disco@81.187.95.100> has joined #bzflag | 00:06 | |
| *** I_Died_Once <I_Died_Once!~I_Died_On@c-73-184-170-223.hsd1.ga.comcast.net> has quit IRC (Ping timeout: 272 seconds) | 01:29 | |
| *** Optic_Delusion <Optic_Delusion!~Optic_Del@2600:4041:194:ff00:a867:29ee:68b0:fb59> has quit IRC (Ping timeout: 244 seconds) | 06:33 | |
| *** Sgeo_ <Sgeo_!~Sgeo@user/sgeo> has quit IRC (Read error: Connection reset by peer) | 06:53 | |
| *** I_Died_Once <I_Died_Once!~I_Died_On@c-73-184-170-223.hsd1.ga.comcast.net> has joined #bzflag | 10:10 | |
| *** Optic_Delusion <Optic_Delusion!~Optic_Del@2600:4041:194:ff00:a9de:d89d:f539:934c> has joined #bzflag | 12:03 | |
| BZNotify | bzflag: atupone synchronized pull request #312 "Do not block on tcp recv" (https://github.com/BZFlag-Dev/bzflag/pull/312) | 17:28 |
|---|---|---|
| *** Sgeo <Sgeo!~Sgeo@user/sgeo> has joined #bzflag | 18:32 | |
| blast007 | oh wow, I've been misunderstanding the +s and -s options for so many years... and our documentation itself is a bit off | 21:55 |
| blast007 | apparently they don't set a minimum and maximum number of random extra flags to include | 21:56 |
| *** Optic_Delusion <Optic_Delusion!~Optic_Del@2600:4041:194:ff00:a9de:d89d:f539:934c> has quit IRC (Ping timeout: 272 seconds) | 21:57 | |
| blast007 | Basically, they don't work together. You'd only ever use one of them. | 21:57 |
| blast007 | +s makes it so there's *always* X number of extra random flags, whereas -s spawns *up to* X number of extra random flags | 21:58 |
| *** Optic_Delusion <Optic_Delusion!~Optic_Del@2600:4041:194:ff00:65aa:92f6:908e:33fa> has joined #bzflag | 22:00 | |
| *** Optic_Delusion <Optic_Delusion!~Optic_Del@2600:4041:194:ff00:65aa:92f6:908e:33fa> has quit IRC (Ping timeout: 268 seconds) | 23:07 | |
| *** Optic_Delusion <Optic_Delusion!~Optic_Del@2600:4041:194:ff00:5824:5f74:c656:9a68> has joined #bzflag | 23:51 | |
Generated by irclog2html.py 2.17.3.dev0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!