diff options
| author | Luke Bratch <luke@bratch.co.uk> | 2019-09-07 14:02:58 +0100 |
|---|---|---|
| committer | Luke Bratch <luke@bratch.co.uk> | 2019-09-07 14:02:58 +0100 |
| commit | c4e88bfe0c918604cb588ab8b3ce7d29b138cd0f (patch) | |
| tree | f061e6a4c1584e515104c9c15f729b823536788b /README | |
| parent | 202061c01eb3600a54f32b4e46327d6685fbd43d (diff) | |
Correct some typos with the replay days:hours:minutes syntax help/documentation.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -42,7 +42,7 @@ These options can be changed by issuing a BLABOUNCER REHASH command or by sendin Once connected to blabouncer with an IRC client, you can use the following special blabouncer commands: -"BLABOUNCER REPLAY [[[days:]hours:]minutes:]" (To replay a given length of time of replay log.) +"BLABOUNCER REPLAY [[[days:]hours:]minutes]" (To replay a given length of time of replay log.) "BLABOUNCER QUIT [quit message]" (To quit blabouncer, optionally sending [quit message] to the server.) "BLABOUNCER REHASH" (To reload settings from the configuration file, see above for details.) "BLABOUNCER CLIENTCODE [clientcode]" (To set an identifier for the current client for auto replaying just @@ -53,7 +53,7 @@ Blabouncer commands are all prefixed with BLABOUNCER which you can usually send == Replaying history == You can request that history is replayed at any time by using the command BLABOUNCER REPLAY -[[[[days:]hours:]minutes:]seconds], assuming replaylogging is enabled in blabouncer.conf. +[[[days:]hours:]minutes], assuming replaylogging is enabled in blabouncer.conf. In addition, you can have history automatically replayed upon a client connecting. There are multiple automatic replay methods available by setting "replaymode" in blabouncer.conf: |