| 00:18.52 | *** join/#bzflag infobot (ibot@208.53.50.136) |
| 00:18.52 | *** topic/#bzflag is https://BZFlag.org || http://ohloh.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.14 released! https://forums.bzflag.org/viewtopic.php?f=62&t=19953 |
| 00:18.52 | *** mode/#bzflag [+v infobot] by ChanServ |
| 00:35.24 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 07:38.45 | *** join/#bzflag ruskie (ruskie@sourcemage/mage/ruskie) |
| 20:20.21 | blast007 | JeffM: I noticed that SSPs added do not show up until a rejoin. I have a possible fix coded, based on another status enum similar to the LSA (List Server Authentication) that tracks the join status, with the possible status being (something like) WaitingForAuthentication, ReadyToJoin, and Joined. For normal players they get set to WaitingForAuthentication, and for SSPs they get set to ... |
| 20:20.27 | blast007 | ... ReadyToJoin. |
| 20:21.07 | blast007 | also made some changes to the logic so that it doesn't try to call the non-existant nethandler for SSPs for handling joins |
| 20:21.38 | blast007 | there was one part where an API event for allowing a join was called, so I just set the IP for SSPs to 127.0.0.1 - but should I just skip the event for SSPs? |
| 20:22.06 | blast007 | I'm thinking a plugin shouldn't be able to disallow an SSP to join |
| 20:24.11 | JeffM | Yeah ssps come from the server they canât be blocked or banned |
| 20:24.46 | JeffM | It would be like the server banning itself |
| 20:25.39 | blast007 | k, I'll revise that part of the change when I get home |
| 21:29.52 | *** join/#bzflag spldart (~james@bzflag/contributor/spldart) |
| 21:29.52 | *** mode/#bzflag [+v spldart] by ChanServ |
| 23:01.11 | *** join/#bzflag kongr45gpen (~kongr45gp@bzflag/developer/alezakos) |
| 23:05.28 | *** join/#bzflag TD--Linux (~Thomas@about/essy/indecisive/TD-Linux) |