If you can't find a solution here or require additional help, read the page on Reporting Issues.

Known Issues [back to menu]

User Interface

Errors / Crashes

Documentation of some issues

Bad performance / OutOfMemoryError [back to menu]

You may 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.

Global hotkeys don't work [back to menu]

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.

Wrong version of Chatty

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.

Could not load library (jintellitype-1.3.8.jar)

Chatty requires the jintellitype-1.3.8.jar to be in the lib subfolder of where the Chatty.jar is located.

Could not load JIntellitype.dll

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:

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).

Related information: Chatty directories and files

Livestreamer won't run properly [back to menu]

See the Chatty Livestreamer Help.

Settings lost [back to menu]

If you loose your settings (or part of it like just the Addressbook) then either they weren't saved/loaded properly for some reason or you changed your configuration and your settings directory is not the same anymore.

Wrong image/sounds folder [back to menu]

The image/sounds folders are based on the current Working Directory, which is set when you start Chatty. More Information..

Can't connect because the login failed [back to menu]

If you repeatedly get disconnected because of possibly invalid login data, please go to Main - 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.

Another reason may be that you are connecting to the wrong port.

Can't connect [back to menu]

It's possible that your internet/firewall doesn't like the port you are using to connect. By default it tries to connect to 6667 first. Twitch may also have changed the ports. You can check (not an official Twitch site) which chat server/ports are available (make sure to use an irc server). The host should resolve to the available server IPs, so you normally shouldn't have to enter an IP directly (for main chat).

If you are using a shortcut to start Chatty, also check any custom server/port you may have defined there using commandline parameters.

Can't get login data [back to menu]

If you get an error getting login data, see What to do when getting login fails.

Broken characters / Fallback fonts [back to menu]

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. You can add your own fallback fonts if you need to be able to display more characters than by default.

The Java fallback font directory is located in the Java Runtime Environment (you may have to create the /fallback directory yourself): <JRE_DIR>/lib/fonts/fallback

To find the <JRE_DIR> location you can either enter the command /openJavaDir to open the directory in your file browser or enter the command /showJavaDir to output the path. The commands have to be entered in the Chatty chat inputbox.

Note: If you set the inputFont setting to something other than a Java logical font (which is currently only possible through setting commands, changing through the Settings Dialog is fine), then the font fallback mechanism may break.

Chatty won't start [back to menu]

You need to have at least Java 8 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.

Run from commandline

Running Chatty from the commandline has the advantage of being able to get messages from before the GUI is established. It also may work when Java isn't integrated into the OS correctly (but is installed).

  1. Open a commandline window on the directory where the Chatty.jar is located
  2. In the commandline window, enter java -jar Chatty.jar and press Enter.

When you enter the above command and Chatty starts correctly (but doesn't when you double-click the Chatty.jar), this may mean that Java isn't integrated into the OS properly. You can create a shortcut or a .bat-file to start Chatty similiar to entering the command above, but much more conveniently.

If Chatty doesn't start when you enter the above command, check the commandline window for error messages. Send a screenshot of the commandline window along with information on what other things you tried if you require further assistance with it.

Check Association of .jar with Java (Windows)

If the integration of Java into the OS may not be correct, and you want to try to fix it, you can try this.

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.)

Error: Java is not recognized as an internal or external command (Windows)

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-separated directories, one of which should point to Java.

Find errors in debug.log

See next section. Of course you'll have to navigate to the folder manually.

Visual Artifacts/Glitches [back to menu]

Some people experience issues with stuff in Chatty not being drawn correctly (e.g. on top of eachother, areas not showing). This is probably a Java bug that is system-dependant in some way (possibly OS or graphics driver related, it's not really clear). There is no definite solution for this, but there are a few things you can try:

Read Issue #64 for experiences of other users and possible workarounds, and add your own data to the discussion.

Debug log [back to menu]

Moved: Report Issue