| *** Zehra <Zehra!~Keiki_Han@unaffiliated/zehra> has joined #bzflag | 00:03 | |
| *** nitroxis <nitroxis!n@nxs.re> has quit IRC (Read error: Connection reset by peer) | 01:17 | |
| *** nitroxis <nitroxis!n@nxs.re> has joined #bzflag | 01:18 | |
| Zehra | So quick question, how to edit/modify/delete chat messages "without swear filtering" done, since the "bz_eMessageFilteredEvent"... | 02:48 |
|---|---|---|
| Zehra | is listed as only occurring "whenever a message is censored by the swear filter", which is limiting to an extent. | 02:49 |
| CaptainRoberts[m | That’s what the raw chat event is for, edit it before the filter is applied. | 02:57 |
| Zehra | Ah, okay, thanks. | 02:59 |
| Zehra | Seems a bit counter-intuitive for the API, hence my confusion. | 02:59 |
| blast007 | how so? | 02:59 |
| CaptainRoberts[m | It literally says before filter in the comments on the event | 03:00 |
| Zehra | This is partially since it mentions "unmodified", but does not hint nor imply it is modifiable. | 03:02 |
| Zehra | Also creates a bit of confusion if the event is passed, would other plug-ins receive the "original" message? | 03:02 |
| CaptainRoberts[m | If it was immutable it would have been marked const, the entire reason for that event is to let plugins write filters | 03:03 |
| CaptainRoberts[m | No, it’s a chain each result goes to the next loaded, that’s why there are two events. | 03:03 |
| CaptainRoberts[m | Things are modifiable in the api by default | 03:05 |
| Zehra | The usage of an event as both "notification" and "modification" is effective, but can cause confusion with items in sequence at times. | 03:09 |
| CaptainRoberts[m | Yes, that is why everyone should have a pair | 03:11 |
| CaptainRoberts[m | Or even 3 | 03:11 |
| CaptainRoberts[m | Allow, modify, notify | 03:11 |
| Zehra | Seems mostly reasonable, would have to check out the event flow more to be certain. | 03:14 |
| CaptainRoberts[m | It’s not that hard | 03:15 |
| Zehra | It's not about "difficulty" or "hard" in reference to complexity, but mostly where if this is to notify original, modify, and final. | 03:17 |
| CaptainRoberts[m | I said should not does | 03:18 |
| CaptainRoberts[m | Raw chat is for modify, | 03:18 |
| CaptainRoberts[m | It’s the start of the chain | 03:19 |
| Zehra | My confusion was simply misinterpretation, since "raw" seems as in "unmodified", regardless of what other plug-ins may or may not do. | 03:21 |
| Zehra | But since it is where it can be "modified", it means now either conditions set, may not be "met", despite being set. | 03:22 |
| CaptainRoberts[m | Yeah, raw means unmodified, has nothing to do with it’s mutability | 03:23 |
| Zehra | Thanks for the insights, it's appreciated. | 03:25 |
| *** Zehra <Zehra!~Keiki_Han@unaffiliated/zehra> has quit IRC (Quit: Quit) | 04:03 | |
| *** BulletCatcher <BulletCatcher!~bc@bzflag/developer/BulletCatcher> has left #bzflag ("tank sank") | 04:19 | |
| *** I_Died_Once <I_Died_Once!~I_Died_On@unaffiliated/idiedonce/x-1828535> has quit IRC (Ping timeout: 260 seconds) | 05:04 | |
| *** BulletCatcher <BulletCatcher!~bc@bzflag/developer/BulletCatcher> has joined #bzflag | 05:31 | |
| *** ChanServ sets mode: +v BulletCatcher | 05:31 | |
| brlcad | /last -hilight | 05:58 |
| *** nitroxis <nitroxis!n@nxs.re> has quit IRC (Remote host closed the connection) | 07:26 | |
| *** nitroxis <nitroxis!n@nxs.re> has joined #bzflag | 07:27 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has quit IRC (Remote host closed the connection) | 09:46 | |
| *** Sgeo <Sgeo!~Sgeo@ool-18b982ad.dyn.optonline.net> has quit IRC (Read error: Connection reset by peer) | 09:50 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has joined #bzflag | 10:00 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has quit IRC (Remote host closed the connection) | 10:18 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has joined #bzflag | 10:50 | |
| *** I_Died_Once <I_Died_Once!~I_Died_On@unaffiliated/idiedonce/x-1828535> has joined #bzflag | 10:59 | |
| moriah | man, i miss when brlcad played bz....good memories | 13:21 |
| Juesto | oof, yeah good memories when i played years ago | 13:23 |
| Juesto | not the same excitement for some reason | 13:23 |
| blast007 | I always miss when I play bz. Need to work on my aim. ;) | 13:35 |
| blast007 | think I left at like -26 yesterday | 13:35 |
| blast007 | though my accuracy is excellent when it's my own tank | 13:36 |
| short_circuit | =D | 14:03 |
| moriah | I'm the queen of sks...and tks, sadly | 14:19 |
| *** Zehra <Zehra!~Keiki_Han@unaffiliated/zehra> has joined #bzflag | 15:12 | |
| *** Sgeo <Sgeo!~Sgeo@ool-18b982ad.dyn.optonline.net> has joined #bzflag | 16:05 | |
| CaptainRoberts[m | Zehra: solo bots share the connection of the 'real' player, so yeah kicking one is going to kill the entire connection and all players associated with it | 20:19 |
| blast007 | is that still the case? | 20:22 |
| CaptainRoberts[m | not unless you've massively refactored the solo bot code and added a kick bot message. | 20:23 |
| *** FusionDude is now known as Flash | 20:54 | |
| Zehra | Confirmed it only happens with the "solo" bots. | 21:13 |
| Zehra | Kind of was hoping it wasn't the case, but at least BZFS is smart enough not to kill all connections by IP. | 21:14 |
| CaptainRoberts[m | It’s by socket | 22:03 |
Generated by irclog2html.py 2.17.3.dev0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!