EDIT: In case you're looking at this for settings, you can find them below the first little explanation under "Connection settings".

EDIT #2: As of March 23rd 2016, it seems almost all (if not all) channels have been moved to the new chat servers. If your DNS has updated, you shouldn't need to update your settings, but Chatty may require a restart.

Twitch has started migrating their chat servers to be hosted on AWS. Currently this migration has only started for only a few users, but will eventually migrate to all users.

Keep in mind that this is a guide done on Windows 10. It should work for older versions as well (at least 7 and 8.1), though. For Chatty users on Mac/Linux, you can use the same parameters for launching Chatty with, but the paths will obviously be a bit different.

Connection settings:

If you're a bit of an advanced user, the information below should contain everything you need for migrating whatever clients you have for connecting to the new Twitch chat cluster.

Keep in mind that Chatty only supports IRC with SSL using port 6697, by default.

Checking if a channel is migrated to the new chat cluster

You can check https://decapi.me/twitch/clusters?channel=CHANNEL_NAME (replace CHANNEL_NAME with the channel you're checking, obviously), which will then either say "aws" or "main".

"aws" is the new chat cluster, while "main" is the old one.

If the channels you're checking are all still on "main", you shouldn't have to reconfigure Chatty... yet. Otherwise, continue reading to see how you can connect to the new cluster and get chat back.

Doing it via Chatty's GUI

For those of you that only use it for your own channel (or fewer channels) and you know you've been migrated to the cluster, then it's best to just do it via the Chatty settings.

• Click "Main" at the top, then "Settings". Click "Advanced" on the sidebar for "Settings".
• Change "Server" to "irc.chat.twitch.tv"
• Change "Port" to "6697" (If you're having issues with port "6697", try port "80" or "6667" instead).
• It should look like this: Screenshot
• Restart Chatty and you should be able to connect to the channel(s).

Running another instance of Chatty specifically for AWS cluster

If you're somewhat like me, and use Chatty constantly for multiple channels, then changing the settings aren't optimal. The way I've done it is to run a separate instance of Chatty (which means I basically have two Chatty windows running, one for the new chat cluster and one of the old one).

• Create a new folder, as an example I'm going to create one under: C:\ChattyAWS
• If you have Chatty open, type "/opendir" and it should open a directory with a lot of files and folders. Copy the files "settings" and "login" into the new folder you created (in my case it's C:\ChattyAWS).
  • If you don't have Chatty open, the default directory for these files can be found by hitting Windows key R and then typing %userprofile%\.chatty
• Find where you have the 'normal' Chatty files saved (the "img", "lib" & "sounds" folders the "Chatty.jar" file) and copy them to the new folder (example: C:\ChattyAWS).
• Right-click on Chatty.jar and click "Create shortcut". Now that the shortcut is created, we can add the shortcut parameters to launch it separately.
• Right-click on the shortcut (should be named "Chatty.jar - Shortcut" or similar) and add the following at the end of "Target": -cd -server irc.chat.twitch.tv -port 6697
  • If you're having issues with 6697 as the port, try using 80 or 6667 instead.
  • It should look something like this: Screenshot
  • If you wanna know what these options do, they're explained on the launch options help page for Chatty
• Now you can move the shortcut anywhere and launch another Chatty instance with it that will be dedicated to the channels on the AWS cluster.
• Important note: You need to use the shortcut every time to launch Chatty properly for the AWS cluster, or else it will load the default settings.