Features
Description
Did you join a raiding guild, but truly "belong" in another guild? Do you miss reading chat from your "real" guild? Thanks to TB Cross-Guild Chat, you can read chat from other guilds, and talk on those guilds' chat channels as well, as if you were a member yourself.
Receiving Cross-Guild Chat
Whenever your peers are online, you will start receiving chat, guild announcements, and achievement announcements from the guild channels they are allowed to read. This option is configurable via the Blizzard Interface menu (default: enabled).
Sending Cross-Guild Chat
Whenever your peers are online, you may use the following commands to send chat over to their guild channels, provided they have sufficient permissions to talk over those channels:
- /tg <message>: send the specified message to your peers' guild channel.
- /tgo <message>: send the specified message to your peers' officer channel.
- /tgmotd <message>: set your peers' guild messages of the day to the specified message.
Note: Those commands will send the same messages to ALL of your peers, so it is recommended that if you specify several peers, they all be alts of the same person. You may prevent your peers from talking over your guild's channels via the Blizzard Interface menu (default: enabled).
Officer Chat
TB Cross-Guild Chat also offers the option to share your officer channel with your peers. Doing so will allow your peers to see your guild's officer channel, as well as let them talk over it. This option is configurable via the Blizzard Interface menu (default: disabled).
Special Note
In order for you to receive cross-guild chat, your peers must also have you defined as a peer, and as stated earlier they need to be online. This add-on works two-way, and specifying a player as a peer is how you establish a trust relationship as far as TB Cross-Guild Chat is concerned.
Setup
Open your Blizzard Interface menu, and under TB Cross-Guild Chat's Peers section, enter the name of your friend who is in a different guild. Then have him or her do the same for you, adding your name to his or her Peers list. Click Accept, and Okay. You may now use the slash commands to communicate cross-guild!
Notice
TB Cross-Guild Chat depends on TB Core and TB Chat Enhancements. The latest releases of TB Core and TB Chat Enhancements are included with TB Cross-Guild Chat so you do not need to download them separately.
Localizations
Localization for TB Cross-Guild Chat is open. Please contribute your translations using the CurseForge contribution page.
Bugs and Requests
Please submit them using the CurseForge Tracker.
About the Author
I am a professional software engineer who plays World of WarCraft way too much and develops add-ons as a hobby (crazy I know!). I have played the same character since the release of World of WarCraft, a hunter called Valana, in the Team BATTLE guild on the Mug'thol realm. I raid some, but my primary focus in this game is PvP (mainly arenas).
------------------------------------------------------------------------
r40 | valana_tb | 2009-05-24 04:16:30 +0000 (Sun, 24 May 2009) | 3 lines
Changed paths:
M /trunk/Locales/enUS.lua
M /trunk/TB_CrossGuildChat.lua
| => \124
Changed the menu options so as to avoid ellipses.
Fixed the GMOTD query response.
------------------------------------------------------------------------
r39 | valana_tb | 2009-05-19 19:14:15 +0000 (Tue, 19 May 2009) | 2 lines
Changed paths:
M /trunk/TB_CrossGuildChat.lua
* Defined defaults for all saved variables.
* Sharing of officer chat is now toggled per-character.
------------------------------------------------------------------------
r38 | valana_tb | 2009-05-15 17:10:37 +0000 (Fri, 15 May 2009) | 1 line
Changed paths:
M /trunk/Locales/enUS.lua
M /trunk/TB_CrossGuildChat.lua
Implemented an option to prevent sharing of cross-guild chat.
------------------------------------------------------------------------
r37 | valana_tb | 2009-05-14 07:52:53 +0000 (Thu, 14 May 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
TB Core now requires LibBabble-Zone-3.0.
------------------------------------------------------------------------
r36 | valana_tb | 2009-05-14 07:40:21 +0000 (Thu, 14 May 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
TB Chat Enhancements now requires LibWho-2.0.
------------------------------------------------------------------------
r34 | valana_tb | 2009-05-08 07:17:09 +0000 (Fri, 08 May 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
TB Core now needs AceHook.
------------------------------------------------------------------------
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP has a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
