Closed S-S-X closed 10 months ago
Related to mt-mods/mail#128, when syncing the mute list it is giving all the existing players.
Wrote few simple test for this, and a lot of it is failing. Seem /mute
is pretty messed up currently.
It is handling
before_send_pm
before_check_muted
(no idea why this is even included, before_send_pm
would prob work for every use case)on_send_on_channel
I guess before_check_muted
can stay anyway, might not be a good idea to change it just yet.
Pretty sure I just simply did not really think it through when adding events but just included anything that seemed somewhat appropriate. Back then /mute
was part of the core functionality and very tightly integrated with other stuff, isn't like that anymore.
Should I disable sync
function for the moment (transfer
works fine) on mail pull request ?
Should I disable
sync
function for the moment (transfer
works fine) on mail pull request ?
Actually I don't remember what it was supposed to do... if it isn't needed then probably better disable.
sync
get the data from beerchat and adapt it to mail (called in get_setting
), transfer
does the contrary (called in set_setting
)
unmuting should always work, no matter if target exists or not.
Not sure if this got fixed or not. Probably but there's no specific tests for it. Can be tested in prod and issue closed if all is good.
I think I've heard last part was also confirmed to work as it should so closing this.
Q: Request for a test: is /mute and /unmute actually broken?
A: test with an alt let a $20 whisper through... and the unmute part didn't work. "was not muted", but that muting remains (but does not affect at least local whisper). also /unmute anything-that-is-not-logged-on results in "Unumuted player anything-that-is-not-logged-on." message which seems rather bogus.
Q: Did muting still work for pm and channel messages? A: yes muting worked for channel and pm, but unmuting didn't work when online. Able to introspect resulting state from where ever it is stored?