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 Error [back to menu]

Note: If you don't use global hotkeys you don't have to worry about this.

If global hotkeys don't work, but there is no error message about it, make sure that you actually have global hotkeys enabled in the Hotkeys settings or in the menu "Extra - Options".

Global hotkeys should usually work on Windows, Linux and Mac. It's possible that they don't work in just some contexts, for example some games.

Error message

If you get an error message related to global hotkeys:

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 - Account - 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 it you can use the command /showFallbackFontDir to output the full path or the command /openFallbackFontDir to directly open the path in your file browser. The commands have to be entered into the Chatty chat inputbox.

The Windows Standalone already contains the Unifont fonts as fallback fonts by default.

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]

Windows Standalone Version

The Chatty.exe uses the bundled Java (JRE) in the runtime directory to execute the Chatty.jar in the app directory. If you have issues executing the Chatty.exe, try the following:

Error: Failed to find JVM..
The Chatty.exe and the bundled Java in the runtime directory may not be compatible or they weren't installed correctly. Manually delete the Chatty.exe and the runtime directory and re-install the Standalone version and make sure it installs or extracts fully.
Error: Class chatty/Chatty not found. / Failed to launch JVM.
Make sure that the path where Chatty is located contains only ASCII characters (basicially no non-english letters).
Issue: Nothing happens when executing the Chatty.exe
In new Standalone versions (ChattyPortable.exe exists) make sure that the directory runtime/lib/ext does not exist.

JAR Version

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.

Blurry UI Scaling [back to menu]

When using a High-DPI monitor or changing the monitor scale setting in Windows, you may experience blurryness in the UI since UI scaling is not very well supported at the moment.


If an app does not handle scaling Windows will attempt to scale up the app automatically, which will usually not look very sharp. There are different ways to tell Windows that Chatty/Java should handle the scaling:

Once Windows lets the app do the scaling, there are different possibilities:

You can change the "UI Scaling" setting under "Main - Settings - Other" to force a fixed scaling. This may not always work. To avoid blurry images and other UI issues a scaling of 1.0 is recommended (you can change "Look", "Font" and "Emoticons" settings to scale up fonts and emotes).

Debug log [back to menu]

Moved: Report Issue

MacOS Issues [back to menu]

Files can't be accessed

If Chatty can't access some files (e.g. sounds), you may have to give the JAR Launcher additional access. Go to System Preferences - Security - Privacy - Full Disk Access and add the Jar to the list. More information..