| 00:33.44 | *** join/#bzflag Sgeo_ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 01:42.25 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 01:58.26 | *** join/#bzflag ahs3- (~ahs3-@cpe-2606-A000-1101-54D-3475-632B-322-8CD0.dyn6.twc.com) |
| 05:22.21 | BZNotify | 02redesign @ bzflag.org: 03allejo pushed 1 commit (06https://git.io/fjeMx): |
| 05:22.22 | BZNotify | 02redesign @ bzflag.org: 03allejo 144aaf9d: Make sidebar scrollable only on desktop view (06https://git.io/fjeMp) |
| 05:24.28 | BZNotify | 02redesign @ bzflag.org: 03allejo pushed 1 commit (06https://git.io/fjeMj): |
| 05:24.29 | BZNotify | 02redesign @ bzflag.org: 03allejo 1422a020: Remove unused scrollable-sidebar class (06https://git.io/fjeDe) |
| 05:26.42 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 06:41.09 | BZNotify | 02feature/redesign/search @ bzflag.org: 03allejo pushed 1 commit (06https://git.io/fjeDr): |
| 06:41.10 | BZNotify | 02feature/redesign/search @ bzflag.org: 03allejo 14c33e60: Add search form to sidebar layout (06https://git.io/fjeDo) |
| 08:20.42 | *** join/#bzflag Sgeo_ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 11:16.19 | *** join/#bzflag infobot (ibot@rikers.org) |
| 11:16.19 | *** topic/#bzflag is https://BZFlag.org || https://www.openhub.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.18 released! https://forums.bzflag.org/viewtopic.php?f=62&t=20030 |
| 11:16.19 | *** mode/#bzflag [+v infobot] by ChanServ |
| 15:51.32 | *** join/#bzflag Opus (~opus@76.202.115.164) |
| 19:08.46 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 19:41.37 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 20:46.16 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 22:12.53 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 23:07.40 | Zehra | Would anyone be aware of any issues with 'rendering' shockwaves on the client side? |
| 23:08.29 | Zehra | I have noticed that when setting shockwaves with an excessively large size and time period, that they will appear to explode much 'smaller' on the client side. |
| 23:09.00 | Zehra | This does not occur with shockwaves fired by others, but does occur for ones own shockwaves. |
| 23:10.15 | blast007 | if the lifetime of the shot is longer than the reload time, the local client will erase the local shots |
| 23:10.27 | blast007 | (when the reload happens, that is) |
| 23:11.13 | blast007 | I can't recall if it's still the case that shooting will overwrite remote shots in the same slot or if the shot slot was decoupled from the shot IDs for 2. |
| 23:11.16 | blast007 | 2.4* |
| 23:11.52 | blast007 | if it's still the old way, shoot again will make the other players see your old shot disappear |
| 23:11.57 | blast007 | shooting* |
| 23:14.29 | Zehra | Interesting. I also seem to recall that this was used by certain individuals to 'reload' much faster, hopefully this isn't the case these days. |
| 23:15.46 | blast007 | that's still handled client-side |
| 23:15.54 | blast007 | I think |
| 23:17.19 | Zehra | Would the local client shot rendering bug still exist in 2.6.x? (As I can almost recall that shots were moved to the server side.) |
| 23:17.49 | blast007 | probably |
| 23:20.12 | Zehra | I'll check the master source and do a few tests, if it still does, I'll file a proper bug report so some formal tracking may be done on the subject. |
| 23:21.05 | BZNotify | 02feature/redesign/search @ bzflag.org: 03blast007 pushed 1 commit (06https://git.io/fjvft): |
| 23:21.06 | BZNotify | 02feature/redesign/search @ bzflag.org: 03blast007 14902094: Update a couple comments and add FlexSearch to the credits page. (06https://git.io/fjvfq) |
| 23:24.23 | *** join/#bzflag Sgeo (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 23:39.36 | *** join/#bzflag Peridot (~Peridot@47.185.225.32) |
| 23:51.34 | Zehra | Could the following threads be updated: https://forums.bzflag.org/viewtopic.php?f=78&t=11311 and https://forums.bzflag.org/viewtopic.php?f=30&t=3552 or replaced? |
| 23:52.18 | Zehra | First one mentions Wiki and as soon we will have official documentation, this will be outdated, second mentions one is able to find who they were banned by... which is no longer the case. |
| 23:53.24 | Zehra | I could provide a post with an update of content, if that is preferred, but would rather see the threads updated or replaced. |
| 23:55.14 | *** join/#bzflag Peridot (~Peridot@47.185.225.32) |
| 23:55.47 | Zehra | Before I forget, the following could be updated to reference https://forums.bzflag.org/viewtopic.php?f=8&t=891 GitHub being used to get BZFlag. |
| 23:57.17 | Zehra | Also https://github.com/BZFlag-Dev/bzflag/blob/2.4/README.MINGW32 could be updated, as SourceForge.net is referenced. |