| 00:11.05 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 00:47.27 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 01:36.35 | *** join/#bzflag KaadmY (uid135503@gateway/web/irccloud.com/x-zrdbekbidwnqanim) |
| 01:41.52 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 02:29.24 | *** join/#bzflag jnoob22 (~jnoob@unaffiliated/jnoob22) |
| 02:29.35 | jnoob22 | would it be advisable to run a server with 2.4.6 RC2 ? |
| 02:31.49 | the_map | jnoob22: just a heads up, you may have to wait for a while for the answer, unless someone that knows what they're talking about is paying attention to IRC atm |
| 02:32.26 | allejo | yea. that's what i'm running on my servers |
| 02:32.43 | jnoob22 | np the_map |
| 02:32.49 | jnoob22 | ok good to know |
| 02:33.01 | allejo | the "RC" part is more intended with client side changes, not server side |
| 02:33.11 | allejo | for this specific release at least |
| 02:33.27 | jnoob22 | ah ok....just discovered my version was at 2.4.3 |
| 03:14.39 | blast007 | jnoob22: generally it's fine to even run the latest stable git branch (current the 2.4 branch) |
| 03:59.18 | *** join/#bzflag L4m3r (~l4m3r@bzflag/developer/L4m3r) |
| 03:59.18 | *** mode/#bzflag [+v L4m3r] by ChanServ |
| 04:53.42 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 05:30.44 | Shuist | I was just thinking, the difference between button up and down... Is that 'button down' is as soon as the button is pressed, whereas the 'button up' is when the button is released? |
| 05:32.08 | the_map | pretty sure |
| 05:32.20 | the_map | it is with xdotool (linux automation tool) |
| 05:35.05 | Shuist | With shooting however, I cannot find a difference between 'bind Q down fire' and 'bind Q up fire'. |
| 05:36.30 | the_map | if you bind to something besides shooting, can you tell a difference? |
| 09:23.14 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 10:55.51 | rodie | meow |
| 11:20.19 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 12:34.06 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 13:49.31 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 13:59.43 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 15:02.12 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 15:48.20 | macsforme | Shuist: our input system has so many hacks and inconsistencies that it makes very little sense |
| 15:48.42 | macsforme | however, if you look at https://github.com/BZFlag-Dev/bzflag/blob/2.4/src/bzflag/ActionBinding.cxx, you can get an idea for how the client expects keys/buttons to be bound |
| 15:49.18 | macsforme | for firing, for example, I think it wants both up and down bound |
| 15:54.51 | blast007 | https://github.com/BZFlag-Dev/bzflag/blob/2.4/src/bzflag/playing.cxx defines a fireButton boolean (line 119) that gets set when the 'fire' command is triggered (line 631) and is used for handling MachineGun (line 6650) as well as the normal firing mechanism ( https://github.com/BZFlag-Dev/bzflag/blob/2.4/src/bzflag/clientCommands.cxx#L332 ) |
| 15:55.21 | blast007 | basically, fireButton gets set to true when the firing button is "down" |
| 15:56.01 | blast007 | this is why using the mouse wheel to shoot causes the MG flag to never stop on some/all platforms (because it only creates a 'down' event, never an 'up' event, so fireButton remains true) |
| 16:01.48 | *** join/#bzflag nitroxis (n@nxs.re) |
| 17:31.37 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 17:39.32 | zuii | I really thought never stopping MG is a setting/plugin :D |
| 20:16.23 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 21:50.02 | *** join/#bzflag Shaba1 (~Shaba1@wsip-68-105-243-92.sd.sd.cox.net) |
| 22:25.13 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 22:48.50 | *** join/#bzflag Void7 (~Void7@205.157.147.198) |
| 23:29.36 | *** join/#bzflag KaadmY (uid135503@gateway/web/irccloud.com/x-rgbeuokvzlmajumx) |