| 00:36.00 | *** join/#bzflag rob1n (Nomsayinth@unaffiliated/rob1n) |
| 01:24.32 | *** join/#bzflag Pimpi (~frank@pD9E11CE1.dip0.t-ipconnect.de) |
| 04:55.21 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |
| 06:53.41 | allejo | when creating new versions of API events, should there a "cut off" time for adding stuff to them? |
| 06:54.58 | allejo | for example, I recently created bz_AllowSpawnData_V2 |
| 06:55.22 | allejo | would there be any issues with me adding more stuff it? |
| 06:56.03 | allejo | so I guess I'm asking, would the "final" version of an API event be every release? so like at 2.4.4 then bz_AllowSpawnData_V2 is finalized |
| 06:56.18 | allejo | but during 2.4.3 it can still be modified |
| 07:31.34 | BulletCatcher | If you reasonably think that no one but you is using it so far, then go ahead and change it. |
| 08:46.00 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 17:06.42 | *** join/#bzflag ukiki (~ukiki_@99-29-152-121.lightspeed.bcvloh.sbcglobal.net) |
| 18:17.29 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 18:17.29 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 18:27.37 | allejo | I'm gonna create a bz_PlayerJoinPartEvent_V2. Anyone want anything in it? |
| 18:33.23 | blast007 | bacon |
| 18:33.48 | *** mode/#bzflag [-b *!*@c-24-16-240-200.hsd1.wa.comcast.net$##fix_your_connection] by blast007 |
| 18:34.08 | *** mode/#bzflag [-o blast007] by blast007 |
| 18:34.17 | blast007 | what are you planning on adding to it? |
| 18:36.48 | allejo | A startOnBase boolean |
| 18:37.22 | allejo | So a plugin could decide whether for a player to start in the base or not per player without using the freeCTFSpawns options in a map |
| 18:37.39 | blast007 | does it make sense to do it there and not as a spawning event? |
| 18:38.08 | allejo | was debating on which to add it to, could work for both |
| 18:38.10 | blast007 | because that gets reset after a flag capture, for instance |
| 18:39.56 | allejo | Could add to both events actually |
| 18:40.07 | allejo | For the allow spawn, would just have keep track of player just joined |
| 18:40.35 | allejo | e.g. A player joins mid match, don't have them start at the base |
| 18:41.11 | allejo | Actually I'll definitely add it to allow spawn, should it be added to player join too? |
| 18:41.33 | blast007 | it wouldn't seem very useful on the join event |
| 18:41.51 | blast007 | and I'd certainly not bump that data type just for that |
| 18:43.56 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 18:43.56 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 19:07.02 | allejo | Then adding it to the spawn event it is. Yea that's why I was wondering if anything else was wanted because a bump just for that wasn't reasonable |
| 19:07.17 | allejo | I'll add it to allow spawn v2 later today |
| 19:29.57 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 19:29.57 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 19:41.32 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |
| 21:10.09 | *** part/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 21:24.32 | *** join/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 23:16.36 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |