PhanxChat is a chat mod aimed at reducing chat frame clutter, and making chat frames easier to use.
Announcements
Attention compilation uploaders:
PhanxChat is free as in "free beer", not free as in "free software", and you may not include it in your compilation or distribute it in any other way without first obtaining permission. See the "License" section below for more information. I'd love not to have to include this at the top of my addon page, but every time I take it out, new compilations spring up like weeds.
Found a bug? Do not post it in the comments section!
See the "Reporting Problems" section below for information on how to correctly report bugs. I will no longer be responding to bugs posted in the comments section. P.S. - Error messages are bugs.
Translations wanted!
Most existing translations need to be updated, as the options have been moved from a slash command interface to a GUI interface. Please send me a PM if you can assist with updating and/or maintaining translations for deDE, frFR, esES, esMX, ruRU, zhCN, or zhTW locales!
Features
Hide the chat scroll buttons
Enable mouse wheel scrolling in the chat frames
Shorten channel names and chat strings
Enable arrow keys in the chat edit box
Move the chat edit box above the chat frame
Configure the chat text fade time
Stop chat tabs from flashing when new messages are received
Lock docked chat tabs in place to prevent accidental dragging
Color player names by class in more message types
Make more message types sticky
Link URLs for easy copying
Suppress channel notification messages
Suppress repeated messages in public channels
For answers to common questions about PhanxChat and its features, see my portal for the PhanxChat FAQ.
For more information, including planned features, advanced configuration options, and a list of companion addons, please see my portal for extra info about PhanxChat.
Usage
Options are available in the standard Interface Options window. As a shortcut, you can type /pchat to open the Interface Options window directly to the PhanxChat panel.
You can type /pchat clear to clear the contents of all chat frames.
You can type /tt or /wt followed by a message to send that message to your current target.
Localization
PhanxChat currently has translations for English, German (deDE), French (frFR), Russian (ruRU), Korean (koKR), Simplified Chinese (zhCN), and Traditional Chinese (zhTW).
If no translations exist for your locale, PhanxChat will default to English, but some locale-dependent features may not work completely (like short channel names) or work in undesirable ways (like short chat strings using English abbreviations that might not make sense for your language).
If you can help translate PhanxChat for European Spanish (esES) or Latin American Spanish (esMX) locales, please send me a PM!
All existing translations will need to be updated for WoW 3.1, since the options are moving to the Interface Options window. If you can help update translations for any locale, please send me a PM.
Known Issues
PhanxChat's name coloring may not work correctly, or at all, if you have other addons that have not been properly updated for WoW 3.2. There is nothing PhanxChat can do about this beyond adding extra checks to prevent error messages.
Tell-target commands do not update the chat edit box to reflect the target of your message.
Requesting Features
Use the Feature Request tracker to suggest features you would like to see in PhanxChat. Keep in mind that I intend to keep this addon limited to simple, uncluttered chat frame modifications. Also, please take a look at the list of declined features before posting a feature request.
The actual error message. If you don't see an error message, are Lua errors enabled in your interface options? Do you have an error handling addon such as BugSack, Swatter, or tekErr enabled?
What is the problem? Be specific.
What were you doing when the problem occurred? Does the problem occur every time you do that? Be specific.
Does the problem occur when PhanxChat is the only addon enabled? If not, which addon is it conflicting with?
Does the problem occur while using the default settings? If not, which settings did you change from their default values?
What version of PhanxChat are you using? If you just say "the latest version" and do not provide an actual version number, I will likely ignore your report.
What locale (language) do you play WoW in? What is the current version of WoW in your locale?
License
Please see my portal or the README file included in the addon's folder for the full license terms under which PhanxChat is released. In particular, redistribution without prior permission is prohibited. Compilation creators, please take a few minutes to learn about the basic details of copyright law and software licensing before you upload a bundle of other people's copyrighted work. Thanks!
Change Log - PhanxChat
Version 3.2.0.53
Added checks to prevent errors caused by other addons that haven't been updated for 3.2, because I'm tired of hearing about them
Fixed suppression options again
Changed from hardcoded class name translations to new FillLocalizedClassList API
Version 3.2.0.51
Updated class coloring for WoW 3.2
PhanxChat's class color option now only colors player names in message types that are not colored by the default UI. To enable class coloring in other message types, use the default UI's chat options window and enable the option for every message type you want class coloring for.
If your locale has not yet patched to 3.2, do not update yet!
Version 3.1.1.49-beta
Fixed error preventing ChatFrame3 and ChatFrame7 from being formatted
Version 3.1.1.48-beta
Fixed achievement messages for Korean (and possibly other non-English) clients
Improved URL linking to reduce the occurrence of false positives
Updated koKR translations by kornshock @ WoWInterface
Version 3.1.0.40-beta
Rearranged configuration GUI
Re-added "/pchat clear" command for easy keybinding
Version 3.1.0.37-beta
Fixed suppressing repeated messages in 3.1
Fixed error in option for shortening channel names
Version 3.1.0.35-beta
Add LibStub for GUI configuration
Version 3.1.0.33-beta
Update for WoW 3.1 (not backwards compatible)
Fix German translation for "Death Knight"
Add GUI configuration in the Interface Options panel
Remove command-line configuration
Version 3.0.2.26
Fix channel notice suppression option
Version 3.0.2.22
Fix chat tab dragging
Version 3.0.2.21
Fix font size command
Version 3.0.2.20
Remove 2.4.3 compatibility
Version 2.4.3.19
Fix scroll-to-bottom button
Version 2.4.3.18
Fix channel notice suppression option
Version 2.4.3.17
Add complete deDE translations from Melikae
Add complete ruRU translations from Valle
Version 2.4.3.14
Fix suppression options
Add complete koKR translations from TalksWind
Version 2.4.3.10
Add complete frFR translations from Nicolas
Version 2.4.3.9
Fix frame blacklisting
Changed versioning scheme to match the rest of my addons (WoW version.addon revision)
I really like PhanxChat. Just wondering if there would be a chance of making the chat editbox moveable and not just stick to the chat window (that's - beside the alt list - the only feature why I still use Prat)...?
Originally posted by Skylinee That explains it. Could you maybe add coloring for message types like ''Player X has joined/left the raid group'', ''Player X loots Item X''? Those are not colored by default, and neither by PhanxChat.
They aren't colored because the player names they contain aren't links. In order to detect them, I'd have to scan every single word contained in every incoming message and try to guess which ones were player names, which would have a very high cost in CPU time for very little practical usefulness. It would be possible, but isn't something I'm interested in adding to PhanxChat.
That explains it. Could you maybe add coloring for message types like ''Player X has joined/left the raid group'', ''Player X loots Item X''? Those are not colored by default, and neither by PhanxChat.
AFK/DND messages, channel join/leave/moderation messages, and system messages are not colored by the default UI. You can easily see which types are colored by the default UI by right-clicking your chat tab and selecting "Settings". Any chat type listed on the main panel with a check box in the "Show class colors" column is colored (or can be colored) by the default UI. Any chat type not listed on that panel is not colored by the default UI.
Uhh... yeah... I guess I need to stop assuming people read stuff... this could have been cleared up weeks ago...
Quote:
Version 3.2.0.51
Updated class coloring for WoW 3.2
PhanxChat's class color option now only colors player names in message types that are not colored by the default UI. To enable class coloring in other message types, use the default UI's chat options window and enable the option for every message type you want class coloring for.
If your locale has not yet patched to 3.2, do not update yet!
I guess turning on blizz class coloring did the trick. So everyone who can't seem to get properly class colored names, do this:
Rightclick the chat-window, go into settings and behind every channel name, make sure you check ''class colored names''. Worked fine for me after 5 mins of testing, maybe your latest change depends on the blizz standard coloring.
Edit: If you enable Blizz class coloring like above, names are colored even when you turn off the option to color class names in PhanxChat, so i guess this option isn't needed anymore.
No, I don't use Github. You can find old versions on Curse, because Curse doesn't give me an option about archiving old versions, and deleting them is a gigantic hassle, so I'm usually too lazy to do it.
Anyway, telling me that things don't work for you is pretty much useless... I'm not having any problems, so I really have no way to fix or even identify a problem when all you tell me is "it doesn't work". Use the troubleshooting steps outlined on my portal, and then post a bug report with the resulting information.
Class coloring is working 80% in customized channels, though it's not really working at all in the gchat for example, even after doing a /who on several players. Also, where can i find the older versions of Phanxchat? Do you have a github repo maybe?
Edit: /say didn't work either. Used Prat previously with no problems though.
Use the old one then. Both versions work 100% for me, there isn't really any way for me to guarantee that anything will work for anyone else with whatever combination of other addons they're using. /shrug
Originally posted by Phanx If you are experiencing problems with name coloring, it is because you have another addon (or maybe more than one) that has not been properly updated for the 3.2 patch. Before this update, you would get an error message any time another addon screwed things up. Now, you just get an uncolored name. Beyond adding extra code to make sure you don't get error messages, there isn't anything I can do to retreive information that has, in effect, been erased by other addons.
If you're affected by this issue, your options are try to track down which addon(s) are causing the problem and ask their authors to update them, or find updated replacements for them, or live without name coloring on message types the Blizzard UI doesn't color.
Nice try, but with version '3.1.1.50-beta' name coloring works perfectly for me, and the latest one is broken.
If you are experiencing problems with name coloring, it is because you have another addon (or maybe more than one) that has not been properly updated for the 3.2 patch. Before this update, you would get an error message any time another addon screwed things up. Now, you just get an uncolored name. Beyond adding extra code to make sure you don't get error messages, there isn't anything I can do to retreive information that has, in effect, been erased by other addons.
If you're affected by this issue, your options are try to track down which addon(s) are causing the problem and ask their authors to update them, or find updated replacements for them, or live without name coloring on message types the Blizzard UI doesn't color.
Originally posted by Phanx Found a bug? Do not post it in the comments section! See the "Reporting Problems" section below for information on how to correctly report bugs. I will no longer be responding to bugs posted in the comments section.
Ah... looks like someone has already posted a report about this same error. Hopefully this will be fixed soon.
