| 03:23.08 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 05:44.20 | *** mode/#bzflag [-v Foo_man_choo] by ChanServ |
| 08:15.08 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 10:34.04 | *** join/#bzflag brad (~brad@stupid.h-o-s-t.name) |
| 10:34.04 | *** join/#bzflag brad (~brad@unaffiliated/brad) |
| 10:58.51 | *** join/#bzflag Foo_man_choo (~james@2601:2c5:c600:2365::518d) |
| 13:56.38 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 18:49.30 | *** join/#bzflag nadir (uid134094@gateway/web/irccloud.com/x-tewlownmhvusgfqa) |
| 20:09.07 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98dd9.dyn.optonline.net) |
| 21:47.35 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 22:23.56 | Zehra | In a few plug-ins, tracking the game state is required for them to operate properly. This works alright, but when having multiple plug-ins, it is excessive redundancy of code. So I am considering creating a single plug-in to track the game state and use inter-plug-in communication to minimize the amount of redundant code. |
| 22:25.17 | allejo | first, that's not something that should live in a plugin. secondly, what's redundant? |
| 22:26.11 | Zehra | The code used for tracking the game state. |
| 22:26.23 | blast007 | what kind of state are we talking about? |
| 22:27.04 | Zehra | Last flag grabbed, last killer ID, last shot event...etc |
| 22:28.51 | allejo | you're gonna have to elaborate more on the benefits of having this data available in some central location |
| 22:29.46 | blast007 | I'm also not familiar with the performance overhead of inter-plugin communication |
| 22:31.08 | allejo | no clue about performance, but using it isn't straightforward and limited |
| 22:31.21 | Zehra | My thoughts are that I'll be able to avoid all this "tracking" of the game state in my plug-ins and simply have a "single" plug-in take care of that and simply get that data from the inter-plug-in communication. |
| 22:31.52 | blast007 | what's the main motivation behind this? worried about performance, or just redundant source code? |
| 22:32.31 | allejo | will your plugin have the ability to track when was the last time the US flag was grabbed by a non-rogue player who had a score of -5 or less? |
| 22:32.44 | allejo | whose callsign also had 4 vowels |
| 22:34.12 | Zehra | It's more of not having to constantly adjust and mess with a bunch of boilerplate to get something going with the part of having more maintainability. |
| 22:34.24 | blast007 | you may be able to just have a base class that extends bzPlugin and then share that between your plugins |
| 22:34.47 | blast007 | copying as needed, or something like plugin_utils |
| 22:35.05 | blast007 | https://stackoverflow.com/questions/357307/how-to-call-a-parent-class-function-from-derived-class-function |
| 22:35.55 | blast007 | have an Event method in both the parent and child class and call the parent method from the child class? never tried that myself |
| 22:36.08 | blast007 | at least not in C++ |
| 22:37.40 | blast007 | could have bools in the parent class like 'trackLastFlast' that controls if the parent class cares about stuff, and then registers events if needed |
| 22:38.22 | blast007 | default them to false, and set the values of those to true in the child class Init method |
| 22:41.32 | Zehra | I'd have to check into that a bit more as it is a bit above my current level of experience and might be a bit overly complex for my needs. |
| 23:14.55 | *** join/#bzflag spldart (~james@2601:2c5:c600:2365::518d) |
| 23:14.55 | *** join/#bzflag spldart (~james@bzflag/contributor/spldart) |
| 23:14.55 | *** mode/#bzflag [+v spldart] by ChanServ |
| 23:50.35 | blast007 | trackLastFlag* |
| 23:54.54 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |