Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The prefix is dropped when building the message. We add it back here
so that the remote servers can recognize it as a server target.
|
|
|
|
|
|
|
|
|
|
This is a partial reversion of 687778b72e.
See also: #1749.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also, deprecate the old SerializeFormat/serialize/unserialise API.
|
|
|
|
|
|
|
|
|
|
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
|
|
This regression was introduced by #1659. This distinction is only
relevant on Windows so this should not affect non-Windows platforms.
|
|
|
|
Also fixes accidentally copying incoming tags on TAGMSG when sending to
other users
|
|
|
|
|
|
|
|
|
|
|
|
This should fix #851.
|
|
|
|
|
|
|
|
|
|
|
|
Don't ignore message tags on ServerCommands, and avoid creating
duplicate CommandBase::Params instances
|
|
When a user (U1) sends a PRIVMSG to a server (S1), which sends it to S2, which finally
sends it to S3 to send to U2, S2 doesn't send the tags it received on
the command from S1 to S3.
|
|
|