| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There is no reason to have these events in one big handler and it
causes unnecessary event hooks to be created by having them like
this.
The ServerEventListener class still exists for compatibility
|
|
|
|
|
|
Usually a duration of 0 is not allowed or handled separately,
but it can also be used as a 'no set time' without separation.
Case in point: m_chanhistory calls DurationString() to convert
the max time seconds back to a human readable string for the
mode serializer. Returning a blank string is bad here.
|
|
Currently a duration of 52w will return a blank string.
When I added weeks to the calculations, I failed to update
the number of seconds to a year. As 365 days and 52 weeks
aren't the same, but the calculation needs to be consistent.
|
|
|
|
|
|
This regression was introduced by #1659. This distinction is only
relevant on Windows so this should not affect non-Windows platforms.
|
|
There is no reason to do this.
|
|
|
|
|
|
This causes inconsistent message ids between servers.
This reverts commit 638e4bb417ebcd4f0a384ac19585620b0fde1569.
|
|
|
|
The legacy method of enabling these extensions is just a wrapper
around the capability. If the cap module is not loaded it can not
be enabled so we should not advertise it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also fixes accidentally copying incoming tags on TAGMSG when sending to
other users
|
|
|
|
This makes debugging issues easier.
|
|
|
|
|
|
This is essentially identical to the one for the start event.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
