Closed KoraggKnightWolf closed 5 years ago
This is most likely caused by the module not prioritising itself in front of m_allowinvite.
cc: @genius3000
Apologies on the delay with this fix. I actually had it done much earlier but with a typo, so it didn't work and I didn't have time to investigate (as I didn't see my typo). Sometimes it's the simple things that get ya. :smile:
Description
When a user has user mode +V set and is invited by any user to a +A channel the user mode +V does NOT block the invite.
Steps to reproduce the issue:
Describe the results you received:
The /INVITE was received as if umode +V were not set despite coming from a non opered user (or non umode +V exempted oper)
Describe the results you expected:
The /INVITE should have been blocked due to umode +V as it was sent by a regular non oper (or non umode +V exempted oper)
Additional information you deem important (e.g. issue happens only occasionally):
This issue requires the channel mode +A/the m_allowinvite.so module to be reproduced (shipped with InspIRCd by default).
Output of ./bin/inspircd --version:
InspIRCd-2.0.27 r0