Update beta help

This commit is contained in:
tduva 2016-04-04 07:42:16 +02:00
parent 9da7514942
commit beb543d773
8 changed files with 383 additions and 26 deletions

View File

@ -5,10 +5,23 @@
<body>
<div id="backlink"><a href="help.html">To main help page</a></div>
<h1><a name="top">Addressbook</a></h1>
<p>
<a href="#editing">Editing Locally</a> (<a href="#commands">Commands</a>) |
<a href="#advanced">Advanced Usage</a> (<a href="#modcommands">Mod Commands</a>, <a href="#file">Change via file</a>)
</p>
<ul>
<li>
<a href="#editing">Editing Locally</a>
<ul>
<li><a href="#commands">Commands</a></li>
</ul>
</li>
<li>
<a href="#advanced">Advanced Usage</a>
<ul>
<li><a href="#modcommands">Mod Commands</a></li>
<li><a href="#file">Change via file</a></li>
<li><a href="#unique-cats">Unique Categories</a></li>
<li><a href="#subs-cats">Automatic Subscriber Categories</a></li>
</ul>
</li>
</ul>
<p>The addressbook allows you to add usernames and assign categories to
them, which can then be used in other places such as the <a href="help-settings.html#Usercolors">Usercolor settings</a>
@ -81,10 +94,12 @@
</dl>
<h2><a name="advanced">Advanced Usage</a></h2>
<p>The following features are a bit more advanced and should only be used if
you somewhat know what you're doing.</p>
<h3><a name="modcommands">Moderator Commands</a></h3>
<p>You can use this to let the moderators of your channel edit your addressbook.
Depending on what commands you allow them to use, this can be a powerful tool,
@ -118,6 +133,7 @@
actual response, you need to have Chatty on stream (which means the response
is also affected by stream delay of course).</p>
<h3><a name="file">Change Addressbook via file</a></h3>
<p><em>This is a rather experimental feature, so it might not work reliably.</em></p>
@ -151,6 +167,53 @@ set testi ignore</pre>
the file should not be necessary.</p>
<p>Example: <a href="http://pastebin.com/LDFpEUaC">mIRC script</a> to edit the Addressbook.</p>
<h3><a name="unique-cats">Somewhat unique categories</a></h3>
<p>You can add somewhat unique categories to a setting, which means that
only one user will have that category assigned, as long as you only use
Addressbook commands to apply that category (and not the context menu or
Addressbook dialog).</p>
<p>Use <code>/set abUniqueCats star</code> to set the category <code>star</code>
as unique category. That way, only one user can have that category.
What happens is that when using an Addressbook command like
<code>/ab add Jack star</code>, it will first remove the <code>star</code> category
from all other users and then add it to <code>Jack</code>.</p>
<p>If you want to have more than one unique category, you can separate
several categories by comma: <code>/set abUniqueCats star,gold</code></p>
<h3><a name="subs-cats">Automatic Subscriber Categories</a></h3>
<p>This is an experimental feature that adds Subscribers automatically to
an Addressbook category, depending on how many months they subscribed.
This works on Subscriber Notifications in chat, so you have to be in the
channel at the time of the subscription for it to work.</p>
<p>First you need to do some configuration:</p>
<ul>
<li><code>/set abSubMonthsChan #&lt;yourchannel&gt;</code> - Set the
channel you want the feature enabled for</li>
<li><code>/add abSubMonths &lt;number&gt;</code> - Add one or several
subscription lenghts in months (repeat the command with a different
number to add more than one)</li>
<li><code>/remove abSubMonths &lt;number&gt;</code> - Remove a number
from the list</li>
</ul>
<p>The months represent the categories that are automatically added. For
example if you configured the months as <code>[3, 6, 12]</code>:</p>
<ul>
<li><code>.. subscribed for 3 months in a row!</code> would add that
user to the <code>3months</code> category</li>
<li><code>.. subscribed for 4 months in a row!</code> would add that
user to the <code>3months</code> category</li>
<li><code>.. subscribed for 11 months in a row!</code> would add that
user to the <code>6months</code> category</li>
<li><code>.. subscribed for 20 months in a row!</code> would add that
user to the <code>12months</code> category</li>
<li><code>.. just subscribed!</code> won't do anything</li>
</ul>
</body>
</html>

View File

@ -0,0 +1,59 @@
<!DOCTYPE html>
<html>
<title>Chatty - Using a Bouncer</title>
<link rel="stylesheet" type="text/css" href="style.css" />
<body>
<div id="backlink"><a href="help.html">To main help page</a></div>
<h1><a name="top">Using a Bouncer</a></h1>
<p>Chatty is tailored towards Twitch Chat and is not a general IRC client,
so using a Bouncer may not work correctly or may cause unexpected
behaviour. Nevertheless, if you want to try if it works for you, this
page should get you started.</p>
<h2>Connecting to the Bouncer</h2>
<p>By default Chatty will connect to the server/ports that are set in the
settings, using the store OAuth token. To connect to a Bouncer you need
to change both the server and port and tell Chatty to use the Bouncer
password instead.</p>
<p>You will need to start Chatty with some <a href="help.html#launch">launch options</a>.
You can create a <a href="help-guide_create_shortcut.html">shortcut</a>
or .bat file for that.</p>
<dl class="defList">
<dt><code>-server &lt;host/ip&gt;</code></dt>
<dd>This will overwrite the Server in the settings for this session (but
not change the setting). Set this to the IP/Host of your Bouncer.</dd>
<dt><code>-port &lt;port&gt;</code></dt>
<dd>Same as server, set this to the port of your Bouncer.</dd>
<dt><code>-password [password]</code></dt>
<dd>Set this to the password of your Bouncer. The password is not saved
in between sessions which is why you need this option.</dd>
</dl>
<p>If your bouncer uses special names starting with <code>*</code> like
<code>*status</code>, this will open an extra Tab in Chatty. You can
also use the <code>/msg</code> command to directly write to that name
(e.g. <code>/msg *perform list</code>).</p>
<h2>Configuring the Bouncer</h2>
<p>You have to configure your Bouncer to connect to Twitch Chat. There are
probably guides out there how to configure your Bouncer. In regards to
connecting to Twitch Chat in particular you can use one of the guides
for regular IRC clients and apply it to the Bouncer.</p>
<p>In addition to that, the Bouncer will need to send the following raw
commands after connecting to Twitch Chat, which will make it send info
like usercolors, emotes, user status and much more:</p>
<pre>
CAP REQ :twitch.tv/tags
CAP REQ :twitch.tv/commands</pre>
<p>See <a href="https://github.com/justintv/Twitch-API/blob/master/IRC.md">more information on Twitch Chat</a>.
</body>
</html>

View File

@ -30,7 +30,7 @@
<th>Subscribers</th>
</tr>
<tr>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&scope=chat_login">Request new login</a></td>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&force_verify=true&scope=chat_login">Request new login</a></td>
<td>x</td>
<td></td>
<td></td>
@ -38,7 +38,7 @@
<td></td>
</tr>
<tr>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&scope=chat_login+user_read">Request new login</a></td>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&force_verify=true&scope=chat_login+user_read">Request new login</a></td>
<td>x</td>
<td>x</td>
<td></td>
@ -46,7 +46,7 @@
<td></td>
</tr>
<tr>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&scope=chat_login+channel_editor+user_read">Request new login</a></td>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&force_verify=true&scope=chat_login+channel_editor+user_read">Request new login</a></td>
<td>x</td>
<td>x</td>
<td>x</td>
@ -54,7 +54,7 @@
<td></td>
</tr>
<tr>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&scope=chat_login+channel_editor+channel_commercial+user_read">Request new login</a></td>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&force_verify=true&scope=chat_login+channel_editor+channel_commercial+user_read">Request new login</a></td>
<td>x</td>
<td>x</td>
<td>x</td>
@ -62,7 +62,7 @@
<td></td>
</tr>
<tr>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&scope=chat_login+channel_editor+channel_commercial+user_read+channel_subscriptions">Request new login</a></td>
<td><a href="https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id=spyiu9jqdnfjtwv6l1xjk5zgt8qb91l&redirect_uri=http://127.0.0.1:61324/token/&force_verify=true&scope=chat_login+channel_editor+channel_commercial+user_read+channel_subscriptions">Request new login</a></td>
<td>x</td>
<td>x</td>
<td>x</td>

View File

@ -15,6 +15,7 @@
<h1><a name="top">Release Information</a></h1>
<p>
<a href="#0.8.1">0.8.2</a> |
<a href="#0.8.1">0.8.1</a> |
<a href="#0.8">0.8</a> |
<a href="#0.7.3">0.7.3</a> |
@ -39,7 +40,85 @@
full list of changes.</p>
<h2>
<a name="0.8.1">Version 0.8.1</a> <a name="latest">(This one!)</a> (2015-08-10)
<a name="0.8.2">Version 0.8.2</a> <a name="latest">(This one!)</a> (2016-03-10)
<a href="#top" class="top">[back to top]</a>
</h2>
<p>During March Twitch migrated Twitch Chat to new servers (Amazon AWS),
which you probably noticed due to some issues for some third-party
tools. This however also brought some improvements.</p>
<p>Twitch Chat now supports SSL
on ports 6697 and 443 and Chatty will automatically add these to the default ports if
your port setting is still on the previous default (otherwise you might
have to add it yourself). The migration also got rid of Event Chat which
previously meant some big channels were on separate severs and not easily accesible from Chatty or
Mobile Chat. Now all channels should be on the same servers.</p>
<h3>Full Changelog</h3>
<pre>
Improvements
============
- Added some account info to User Info Dialog (click on "More..")
- Added auto-unhost feature (to unhost when your stream goes live, disabled by
default)
- Added single-instance mode, with the ability to join channels in the already
running instance
- Improved Emote Dialog info a bit
- Added `force_verify=true` parameter to Authorize URL (makes Twitch always ask
if you want to Authorize, makes sure you are logged in to the right account)
- Added new Twitch Player URL in context menu
- Added /emoteonly and /emoteonlyoff commands (in case they get enabled again)
- Added "emotesets" parameter to /refresh command
- Changed twitchemotes.com API URL (which is the source of emoteset information)
- Added some support for selecting the correct chat server
- Added auto-responses to whispers for ignored/non-whitelisted users (disabled
by default)
- Added feature to automatically add Addressbook categories on Subscriber
notifications (experimental)
- Added feature to automatically copy messages into clipboard
- Moved debug logs to down directory
- Increased max reconnection attempts to 30
- Added error message for setting invalid stream status in Admin Dialog
- Added in-app announcements (Help - Announcements), for more reliable
communication of relevant news about Chatty (if new announcement is available
a window will pop up on start and a notification will be shown in the main
menu bar)
- Added /proc command to start native processes out of Chatty
- ShortenDisplayOfExcessivelyLongEmoteCodesLookingOutTheirWindow
- Updated help
Settings
========
- Added more font sizes to GUI
- Added input font setting to GUI
- Added setting to prevent highlights from specific users (e.g. your own bots)
- Added setting to toggle closing of Emote Dialog on double-click on Emote
- Added setting to remember Status History table sorting order
- Added setting to toggle Usercolor correction
- Added setting to display more detailed uptime in titlebar (enabled by default)
- Changed default for showing animated emotes to off
- Changed default for Min. Userlist Width to 0
- Changed defaults for server/port (actual values changed when updating to this
version, if setting values are on the previous default)
- Changed default for Highlight Mod Command to !highlight, ignore case for both
the channel and command setting
- Made setting names case-insensitive (when using setting commands)
- Changed the process of saving settings in an attempt to make it more reliable
- Added menu entry to save settings manually
Bugfixes
========
- Fixed Admin Dialog sizing causing display issues
- Fixed spam protection message being displayed on the wrong channel
- Fixed new Twitch Emotes code being one character short
- Fixed autojoin not working sometimes
- Fixed framerate of GIFs, which may break some GIFs that worked before, but
prevents high CPU usage (displaying animated GIFs in Java is hard)
- Check if Java supports opening URLs on the current platform and run native
command if necessary
</pre>
<h2>
<a name="0.8.1">Version 0.8.1</a> (2015-08-10)
<a href="#top" class="top">[back to top]</a>
</h2>
<h3>Highlights / Important Information</h3>

View File

@ -60,7 +60,8 @@
<a href="#streamchat">Stream Chat</a> |
<a href="#streamhighlights">Stream Highlights</a> |
<a href="#debugging">Debugging</a> |
<a href="#bots">Bot Badges</a>
<a href="#bots">Bot Badges</a> |
<a href="#cm">Copy Messages</a>
</p>
<table class="settings" style="border-collapse: collapse;">
<tr style="border-bottom: 1px solid #EEE">
@ -528,6 +529,48 @@
<td>Use bot names from FFZ API. FFZ emotes have to be enabled for this to work.</td>
</tr>
</table>
<h3><a name="cm">Copy Messages</a></h3>
<p>This can automatically copy all incoming messages into the clipboard.</p>
<table class="settings">
<tr style="border-bottom: 1px solid #EEE">
<th>Setting</th>
<th>Type</th>
<th>Values</th>
<th>Default</th>
<th>Description</th>
</tr>
<tr>
<td class="settingExclusive">cmEnabled</td>
<td colspan="2">Boolean</td>
<td>false</td>
<td>Enable/disable the copy messages feature altogether.</td>
</tr>
<tr>
<td class="settingExclusive">cmChannel</td>
<td>String</td>
<td>Channel Name (including leading #)</td>
<td><em>empty</em></td>
<td>Restrict copying messages to this channel. Leave empty
for no channel restriction.</td>
</tr>
<tr>
<td class="settingExclusive">cmTemplate</td>
<td>String</td>
<td>Template for the copied text</td>
<td>{user}: {message}</td>
<td>This is the template for what is put into the clipboard.
<code>{user}</code> is replaced with the name of the
user who send the message, <code>{message}</code> is
replaced with the text of the message itself.</td>
</tr>
<tr>
<td class="settingExclusive">cmHighlightedOnly</td>
<td colspan="2">Boolean</td>
<td>false</td>
<td>Only copy highlighted messages.</td>
</tr>
</table>
</body>
</html>

View File

@ -32,9 +32,18 @@
<a name="Main">Main</a>
<a href="#top" class="top">[back to menu]</a>
</h2>
<h3>Font</h3>
<h3>Chat Font</h3>
<p>Change font and font size by clicking on <code>Select font</code>.</p>
<h3>Input Font</h3>
<p>Input font is restricted to two fonts by default, because other fonts
cause issues due to a bug in Java. The number behind the font is the
font size. You can manually change this setting via
<a href="help-setting_commands.html">Setting Commands</a> (as with most
settings) if you really need another font, but pay attention to the
<a href="help-setting_commands.html#font">note</a> about the adverse
effects it may have.</p>
<h3>Startup</h3>
<p>You can select what will happen when you start Chatty:</p>
<ul>

View File

@ -241,10 +241,14 @@
</h2>
<p>If you experience any problems or errors, then there may be helpful
information for debugging in the debug log, which is located in the settings
directory <code>&lt;user_dir&gt;/.chatty/</code> (e.g.
<code>C:\Users\&lt;username&gt;\.chatty\</code>, if you
have Chatty running you can enter <code>/openDir</code> to open it or
<code>/dir</code> to output the path).</p>
directory:</p>
<p style="margin-left:10px"><code>&lt;user_dir&gt;/.chatty/debuglogs/</code>
(Example: <code>C:\Users\&lt;username&gt;\.chatty\debuglogs\</code>)</p>
<p>If you have Chatty running you can enter <code>/openDir</code> to open it
or <code>/dir</code> to output the path, then simply navigate to the
<code>debuglogs</code> subfolder.</p>
<p>In that folder, there are two kinds of debug files:</p>
<ul>
<li>The <code>debug.log</code> which is overwritten everytime you start

View File

@ -5,7 +5,7 @@
<link rel="stylesheet" type="text/css" href="style.css" />
</head>
<body>
<h1><a name="top">Chatty (Version: 0.8.2b1)</a></h1>
<h1><a name="top">Chatty (Version: 0.8.2b5)</a></h1>
<table>
<tr>
<td valign="top">
@ -20,6 +20,7 @@
<strong>Chat basics</strong>
<ul class="menu">
<li><a href="#symbols">Symbols used in chat</a></li>
<li><a href="#userlist">Userlist</a></li>
<li><a href="#favorites">Favorites / History</a></li>
<li><a href="help-whisper.html">Whisper Feature</a></li>
</ul>
@ -74,6 +75,7 @@
<li><a href="#about">About/License</a></li>
<li><a href="#ignoreJoinsParts">Ignore joins/parts</a></li>
<li><a href="help-memory_usage.html">About Memory Usage</a></li>
<li><a href="#custom-processes">Run Custom Processes</a></li>
</ul>
<strong>Guides</strong>
@ -81,8 +83,8 @@
<li><a href="help-getting-started.html">Getting Started Guide</a></li>
<li><a href="help-guide1.html">Run more than one instance of Chatty</a></li>
<li><a href="help-guide2.html">What to do when getting login fails</a></li>
<li><a href="help-guide_create_shortcut.html">Create shortcut (launch options/icon)</a></li>
<li><a href="help-bouncer.html">Using a Bouncer</a></li>
<li><a href="help-short_guides.html">More Guides..</a></li>
</ul>
<p style="padding: 10px;">Also check out the official
@ -220,9 +222,18 @@
<ul>
<li><code>/server &lt;host&gt;[:port]</code> - Connect to a custom server</li>
<li><code>/raw &lt;command&gt;</code> - Send a raw command to the server</li>
<li><code>/refresh &lt;emoticons/badges/ffz/ffzglobal/bttvemotes&gt;</code>
- Refresh the Twitch emoticons or badges (current channel) list or
refresh FrankerFaceZ channel emoticons (current channel) or global emoticons.
<li><code>/refresh &lt;emoticons/badges/ffz/ffzglobal/bttvemotes/emotesets&gt;</code>
- Refresh the given data from it's respective API:
<ul>
<li><code>emoticons</code>: Twitch Emotes</li>
<li><code>badges</code>: Twitch Badges (current channel)</li>
<li><code>ffz</code>: FFZ Emotes (current channel)</li>
<li><code>ffzglobal</code>: Global FFZ Emotes</li>
<li><code>bttvemotes</code>: BTTV Emotes (global and current channel)</li>
<li><code>emotesets</code>: Association between emoteset and
channel name, to display Twitch Subemotes info correctly
(twitchemotes.com API)</li>
</ul>
<em>This downloads the lists from the Internet, so don't use this
unless you need to (it's basicially like pressing reload in your
browser, just only for some stuff).</em></li>
@ -364,6 +375,52 @@
mod icon for some channels. You can disable this in the settings if you
want to keep the default one for all channels.</p>
<h2>
<a name="userlist">Userlist</a>
<a href="#top" class="top">[back to menu]</a>
</h2>
<p>The userlist on the side of the channel shows all users currently
considered to be in the channel.</p>
<ul>
<li>A user gets added to the userlist..
<ul>
<li>..when the user says something in chat.</li>
<li>..when Chatty receives a JOIN from Twitch Chat for that user (or
that user is on the received NAMES list).</li>
</ul>
</li>
<li>A user gets removed from the userlist..
<ul>
<li>..when Chatty receives a PART from Twitch Chat for that user.</li>
</ul>
</li>
<li>The userlist gets cleared entirely..
<ul>
<li>..when you close the channel (close the Tab).</li>
<li>..when you rejoin the channel (e.g. when reconnecting).</li>
</ul>
</li>
</ul>
<p>In order to receive JOIN/PART messages, the setting <code>Correct Userlist</code>
under <code>Settings - Advanced - Connection</code> has to be enabled.</p>
<p>JOIN/PART messages are sent in batches and can be pretty delayed. So if
someone joins the chat, he may only appear as joined after e.g. 15
seconds. If you want to use this to directly react on stream to someone
joining, then including stream delay your reaction may be e.g. 30
seconds too late (possibly longer). The user may even have already left
the channel again, but it just doesn't show yet.</p>
<p>The userlist can also take some time to initially load after you join a
channel, or not load at all sometimes.</p>
<p>Also note that the userlist doesn't necessarily have to do with who
watches your stream. A user can be logged into chat without watching the
stream and vice versa. Overall, just don't take the userlist too
seriously.</p>
<h2>
<a name="nickCompletion">TAB Completion</a>
<a href="#top" class="top">[back to menu]</a>
@ -663,7 +720,9 @@ MiniK http://static-cdn.jtvnw.net/emoticons/v1/25/1.0 set:793 id:3287</pre
<p>Required:</p>
<ul>
<li>The <strong>code</strong> can be prefixed with <code>re:</code>
to specify a regular expression. Otherwise it is interpreted as plain text.</li>
to specify a regular expression. Otherwise it is interpreted as plain text
(the same as regular Twitch emotes, case-sensitive and usually separated
by space from other characters).</li>
<li>The <strong>image file</strong> is relative to the settings directory (where you created
the <code>emotes.txt</code> in), so just put them in the same directory.
You should also be able to use URLs to load the image from the internet.</li>
@ -1076,6 +1135,30 @@ MiniK http://static-cdn.jtvnw.net/emoticons/v1/25/1.0 set:793 id:3287</pre
been removed. You can now disable the <a href="help-settings.html#Advanced-Userlist">Correct Userlist</a>
setting to not get any joins/parts if you think it could improve performance.</em></p>
<h2>
<a name="custom-processes">Run custom processes</a>
<a href="#top" class="top">[back to menu]</a>
</h2>
<p>Using the <code>/proc</code> command you can start processes directly out
of Chatty. An example of where this is already integrated into Chatty is
starting Livestreamer, however this is a more basic implementation.
<em>This is probably only interesting for advanced users.</em></p>
<ul>
<li><code>/proc exec &lt;command and parameters&gt;</code> - Try to
start a process on your computer.</li>
<li><code>/proc list</code> - List of processes currently running out of
Chatty.</li>
<li><code>/proc kill &lt;id&gt;</code> - Forcefully end the process with
the given id (get the id from the list of processes).</li>
</ul>
<p>Example: <code>/proc exec notepad H:\hl.txt</code> will start Notepad
and open the given file.</p>
<p><em>Note:</em> Commands and output of the process is logged in the Debug Log which
is written to file and output to <code>Extra&nbsp;-&nbsp;Debug window</code>.</p>
<h2>
<a name="launch">Launch options</a>
<a href="#top" class="top">[back to menu]</a>
@ -1110,7 +1193,8 @@ MiniK http://static-cdn.jtvnw.net/emoticons/v1/25/1.0 set:793 id:3287</pre
<dd>Connect immediately when starting Chatty</dd>
<dt><code>-channel &lt;channel&gt;</code></dt>
<dd>The channel to join</dd>
<dd>The channel to join (you can specify more than one channel by
separating them with a comma)</dd>
<dt><code>-ds</code></dt>
<dd>Don't save settings on exit (settings are everything that is
@ -1120,11 +1204,27 @@ MiniK http://static-cdn.jtvnw.net/emoticons/v1/25/1.0 set:793 id:3287</pre
<dd>Use current working directory (usually the directory you
start Chatty from) for saving/loading settings and other files.
This can be useful to make Chatty more portable or use several
different setting files on the same computer.</dd>
different setting files on the same computer.
<a href="help-guide_folders.html">More information..</a></dd>
<dt><code>-set:&lt;settingName&gt; &lt;setting value&gt;</code></dt>
<dd>Change any setting that can be edited via the <code>/set</code>
command (see <a href="help-setting_commands.html">Setting Commands</a>).</dd>
<dt><code>-single [port]</code></dt>
<dd>Run in single instance mode, which means if you start Chatty while
it's already running the parameters are forwarded to the already
running instance instead of starting another one. You have to
specify the <code>-single</code> parameter with the same port (or
no port to use the default one) for all instances that you want to
have run in the same single instance mode.</dd>
<dd>The port is listened to locally to check if any instance is already
running and to forward the commandline parameters. If you don't
supply a port a default one is used. If the used port is already
taken by another program you have to specify one that works or else
no instance of Chatty will be able to start.</dd>
<dd>Currently only the <code>-channel</code> parameter is used when
forwarded to an already running instance (joining the channel).</dd>
</dl>
<h2>