Advanced Settings
The 'Advanced' settings menu contains configuration options that allow the user to further tweak their interaction with chat. New users can generally ignore this screen safely, as TabbyChat should function just fine without any changes here.
The advanced settings are saved in a file called 'advanced.cfg', which can typically be found in .minecraft/config/tabbychat.
This input box will accept any integer value between 0 and 999, although a value below 5 will likely lead to functionality problems elsewhere. This setting allows you to change the number of chat lines retained by each chat channel (including the master) that are available to scroll back through. The default value is 100, and can generally be increased without noticeable impact on memory, but beware - this value applies to each tab individually.
Acceptable values here are 0-99. This setting helps keep the auto-searching algorithm in check by defining an upper limit on the length of the channel name (does not apply to PM searching).
See Multi-line chat for more info
See Dynamic chat box for more info
When the chat interface does not currently have focus (e.g. during normal gameplay), newly-received chat messages are displayed in the chat area, and then fade away after a period of time. In the vanilla client, this period of time is equal to 200 'ticks', which essentially means 200 iterations of the chat renderer. This slider allows you to increase or decrease the amount of time (in ticks) that messages stay visible under these circumstances.
Also note that the amount of space available to display these messages (prior to fading away) is limited by the aforementioned "Unfocused Height" setting.
The vanilla Minecraft client has two different font sources: the default (which I'll refer to as non-unicode), and a large set of character images support a full range of Unicode blocks. When a resource pack (or previously texture packs) provide an alternate font for the client, it's almost always restricted to the default rendering method. Minecraft will generally revert to the Unicode method, on its own, in situations where it's necessary - for characters not contained in the default font image.
Enabling this option will result in TabbyChat 'forcing' the use of the unicode fonts for rendering all text related to TabbyChat and chat in general. The result is basically a matter of personal preference, but many find the unicode font more visually appealing than the default.
Example:
