~steering/inspircd++.git/src/modules/m_exemptchanops.cpp, branch v3.4.0

Show the mode syntax in ERR_INVALIDMODEPARAM.

2019-06-12T20:52:58Z

Fix building on older compiler versions.

2019-06-07T19:22:43Z

Validate the exemptchanops parameter better and check permissions.

2019-06-07T09:44:20Z

Closes #1055.

Textual improvements and fixes such as typos, casing, etc. (#1612)

2019-04-28T08:14:21Z

Add the tag and switch ListModeBase to always use it.

2018-12-19T09:02:09Z

The old method of doing this was: 1. Extremely inconsistently used. Some list modes used and some used their own config tag. 2. Not documented in the slightest. There was a small reference to for the ban mode but nothing else. 3. In some cases conflicting with other config tags. The chanfilter module defined a tag for general config whilst also using it for the max list settings. The new tag avoids these issues entirely.

Use consistent numerics when a mode already exists or doesn't exist.

2018-12-09T06:57:10Z

Use ERR_BANLISTFULL in the chanfilter and exemptchanops modules.

2018-12-09T06:29:48Z

Add ERR_INVALIDMODEPARAM for responding to invalid mode params.

2018-01-29T11:52:13Z

Currently on invalid modes we do a combination of different things: 1. Send a custom mode-specific numeric (which often collides with other modes). 2. Send a server notice. 3. Do absolutely nothing. This new numeric is a generic way of handling invalid parameters when setting a mode that avoids all of the mistakes of the previous behaviour.

Add the override keyword in places that it is missing.

2017-11-21T15:51:45Z

GCCs warnings for this are much better than Clangs.

Move the OnCheckExemption hook out of the core.

2017-03-20T11:47:59Z