If you experience a laggy interface, this can have several reasons. For one some chat channels are very busy and depending on your computer, this may not be easy to handle. Managing the userlist can cost a lot of performance in large channels because of having to react to hundreds of users joining or leaving at once. It can help to temporarily ignore joins/parts in this case.
You may also want to check if Irc logging is enabled in the Debug Window
(Extra - Debug window - Checkbox: Irc log), which should
be disabled by default, but can lower performance if checked.
First of all, you only need Global Hotkey support when you want to use global hotkeys (which you can define in the settings). If you don't, you can just ignore any related messages or download the version of Chatty without Hotkey support. Global hotkeys currently only work on Windows.
If you want to use global hotkeys and you get a message related to them not working, check the following sections. If you don't get a message, but the global hotkeys you defined just don't work, make sure you actually have global hotkeys enabled in the settings.
If you try to add a global hotkey and it tells you that you have the
wrong version of Chatty, you probably don't have the version supporting
global hotkeys. Download the version that contains hotkey
in the .zip filename and try that instead.
Chatty requires the jintellitype-1.3.8.jar to be in the
lib subfolder of where the Chatty.jar is
located.
If you get this error, you started Chatty with Hotkey support, but it couldn't load the library (.dll) necessary to register hotkeys. This can mean that:
.dll)JIntellitype.dll isn't stored where the program can
find it
Find out if you have the 64bit or 32bit version of Java (e.g. by
entering java -version on the commandline to check if there
is 64bit in the response), then check if you downloaded the matching
version of Chatty.
Enter /wdir in Chatty to find out what your working directory
is and make sure the JIntellitype.dll is in there. If you
are starting Chatty via a shortcut, remember that the directory
specified in the Run in field determines your working
directory (on Windows at least, but global hotkeys are currently Windows only
anyway).
See the Chatty Livestreamer Help.
If a user is timed out in one channel, Chatty may show the timeouts in other channels as well. This is because there is no channel associated with timeouts or bans in Twitch Chat, so the program has to guess in which channel the timeout occured. See also: Joining more than one channel.
If you repeatedly get disconnected because of possibly invalid login
data, please open the Connect Dialog and choose Configure login.. - Verify login.
This will send a request to Twitch to check if the access token is valid.
If the login data is valid, then Twitch may just have temporary problems
and you should try again later. The same goes for when the check itself
fails because it can't reach the Twitch API.
If the login data isn't valid, you can just remove the login and request new login data. Also see the section about login for more information about invalid logins.
If Java encounters a character that is not contained in the chat font
you currently have configured, it will try to find it in the fallback
fonts. While still not all characters will be displayed this way, it
should work a lot better. If you want to be able to display even more
characters, you can add your own fallback fonts into the Java fallback
font directory: <JRE_INSTALL_DIR>/jre/lib/fonts/fallback
On Windows, the JRE would usually be located in
C:\Program Files\Java\ or
C:\Program Files (x86)\Java\.
Note: If you set the inputFont
setting to something else
besides a Java logical font, then the font fallback mechanism may break.
This was the case before version 0.7.3.
You need to have at least Java 7 JRE (Java Runtime Environment) installed to run Chatty.
If you try to start Chatty by double-clicking the Chatty.jar,
first make sure that .jar files are associated with Java,
and not some other program like WinRAR. The icon of the Chatty.jar
should have a Java icon (coffee cup). If you right-click the Chatty.jar
you can select the program to open it with under Open with.
If you are sure that the Chatty.jar is actually started with
Java, but no program window appears, it may be that an error occured before
the window (GUI) could be created.
Open a commandline window and enter assoc .jar which should output
.jar=jarfile and enter ftype jarfile which should
output something like "C:\Program Files\Java\jre7\bin\javaw.exe" -jar "%1" %*
(see also
Could not find the main class. Program will exit.)
Running Chatty from the commandline has the advantage of being able to
get messages from before the GUI is established. Open a commandline where
the Chatty.jar is located (Win7/8: Hold Shift while Right-Clicking to open
the context menu, click Open command window here) and enter
java -jar Chatty.jar.
If you experience this when entering java -jar Chatty.jar
in the commandline, then it probably can't find Java because it's not in the
PATH environment variable (that defines where to look
for programs of which only the filename has been entered, not the whole path).
You can enter PATH in a commandline window to check what is
in it. It should show a list of semicolon-seperated directories, one of which
should point to Java.
See next section. Of course you'll have to navigate to the folder manually.
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 <user_dir>/.chatty/ (e.g.
C:\Users\<username>\.chatty\, if you
have Chatty running you can enter /openDir to open it or
/dir to output the path).
In that folder, there are two kinds of debug files:
debug.log which is overwritten everytime you start
Chatty. It may also have a number at the end (like debug.log.1)
if Java couldn't open the usual debug.log.debug0.log, debug1.log, ..), whereas
one of them is written to at a time, and then switched to the next when
a certain filesize is reached, rotating between a certain number of files.
Those files are not overwritten when Chatty is started, but instead new data is appended.So to find possibly relevant data:
debug.log first.debug0.log, debug1.log, ..
files could contain the necessary information, based on the last
modification dates.
Contact me please.