Report Issue

First of all make sure that you're running the latest version (Help - Check for update or GitHub Releases). Updating (including to a beta, if available) may already fix your issue. If not, then include as much information as possible in your report, such as:

• Chatty version, Java version, OS (can be found in the output of the command /appinfo)
• What is the issue? Describe is thoroughly, include screenshots if possible.
• When did the issue first occur, has it occured more than once?
• Can you reproduce the issue, and if so how exactly? Be as clear as possible. Reproducing an issue is often elemental in fixing it.
• The complete error message (if an error message was shown).
• If possible, include the Debug Log of when the issue occured.

If you don't include this information, it will be harder to help you.

The best way to report an issue is usually in the Chatty Discord, because you're not as limited in message length as on Twitter, there are other people there that may be able to help and you can easily upload screenshots or short videos. But if you prefer, Twitter and E-Mail are also available.

You can also open a GitHub Issue, which contains a template for reporting an issue which you should follow.

Please only contact me via one of the mentioned ways at a time. Reporting the same issue in several different places is just confusing and will probably hinder the solving of your issue.

Debug Log

Chatty is writing a debug log, which you can view in two ways:

• While Chatty is running via Extra - Debug Window:
  • Log - The main Debug Log (this is usually what you want)
  • Irc log - Raw communication with Twitch Chat (has to be enabled)
  • FFZ-WS - Raw communication with FFZ Websocket server
  • PubSub - Raw communication with Twitch PubSub
  • Other - More specialized debug messages, most of which have to be enabled first
• In the Debug files, located in the settings directory

Debug log files

The debug log files are located in the settings directory, in the subfolder debuglogs. While Chatty is running you can use the command /opendir to open the settings directory in the file browser, then open debuglogs.

There are two kinds of debug files:

• The 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.
• Several files (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:

1. If you haven't started Chatty again after the error occured, check the debug.log first.
2. Otherwise check if one of the debug0.log, debug1.log, .. files could contain the necessary information, based on the last modification dates.
   • Even if the error is already some time back, it may still be in there, depending on how much data has been added in the meantime.