Elephant
"Shoot... what did he say again? I just got disconnected."
"Didn't that folk already loot that rare item 10 minutes ago?"
"I really wish I could remember the name of the item linked on the guild chat yesterday at 9:00 PM."
...
Already been in one of these situations? Don't be annoyed anymore, here is the solution!
Solution to chat loss annoyance
Elephant logs the chat for you in the background even when you get disconnected. It saves the WHISPER & BATTLE.NET, RAID, INSTANCE & BATTLEGROUND, PARTY, GUILD, SAY, YELL and OFFICER chats separately, but also all general chats (General, Trade, LocalDefense, ...), custom chats you are currently on, achievements, loots and finally system messages (auctions, rolls, server going down, ...). You can easily go through all these logs, thanks to a straightforward interface displaying all the access buttons on the right side of the main window. You can access the options of the addon by typing /elephant and also bind a key to pop up the addon.
Elephant gives you the ability to copy up to 100,000 (yes, 100k) characters of logs to another application. A BBCode feature is even included, letting you copy/paste a chat with colors and links to an item database in a very quick and simple way to your favorite forum.
This is THE addon that you should install if you want to never forget what somebody told you in game. Be a pro of managing hell tells, go peacefully AFK for a few minutes, or be an awesome role player. Elephant is also perfectly designed for Guild Leaders, Officers and Raid Leaders particularly because it restores the chats after you've been disconnected.
Main features
- Logs the chats in the background, with a limit of 10,000 lines for each chat (Blizzard's default is 161 lines for everything).
- Saves the logs when you log out or get disconnected.
- Display the chats with timestamps, or using your Prat settings if you have it installed.
- Copy the chat and paste it in other applications (BBCode supported!), up to 100,000 characters.
- Save the chat and combat log in two different files on your computer (using the default Blizzard logging system).
Other features
- Use filters to avoid logging some of the custom channels you join.
- Enable/disable logging for each chat separately.
- Item links in logs are displayed in their proper color and are clickable.
- Player names in the main window are clickable.
- ...and much more!
Community
Report an issue (bug & suggestions): https://www.wowace.com/projects/elephant/issues
now update zhCN local for chatlog ver2.0
--zhCN Local --Translator: <CWDG>月色狼影 --10 28 2006
local L = AceLibrary("AceLocale-2.2"):new("ChatLog")
--[[
thanks pb_ee1.. gonna give this a shot tonight in game, see how it runs for me. nice to see really active decelopment on this mod, its been really handy in the past for me :)
ChatLog 2.0 released, have fun ;)
ChatLog 2.0 is now almost ready for a release. A small bug is still remaining, sometimes poping up an error window when you change from one channel to another (Hearthstone, ...). I'll correct this bug tomorrow and release the AddOn ;)
I am currently waiting for an account in order to commit ChatLog on WoWAce, but if it takes too long, I'll release it before. Hum... well because I'm a bit excited to release v2.0, I'll only wait until tomorrow afternoon ^^
Great news mate. I'm trying to use only Ace based addons and I'm really happy to see that you are switching to Ace2 as well.
Keep it up mate. I like and use ChatLog a lot, tho those bugs with full logs can be annoying I just empty them (since I log them anyway in wow\logs) and then I'm ready for 1000 more lines :)
Any ETA for ChatLog 2.0 ?
A very quick note: ChatLog 2.0 is on its way ;)
There will not be a lot of changes in the User Interface, but A HUGE work has been done on the code. ChatLog 2.0 will be using Ace2 (http://www.wowace.com/wiki/Main_Page).
An error occurs when the log is full: no new line is added to the log variable in memory. It seems it is (again) a Blizzard's UI bug.
I would like to correct this bug, but I also would like ChatLog to use Ace2. I'm working on this irritating bug.
Maybe you did not delete the right ChatLog.lua file.
DO NOT delete: \Account\
when attempting to open the channel display menu : File: Interface\AddOns\ChatLog\ChatLog.lua Line: 607
Error: bad argument #1 to `gsub' (string expected, got nil)
only happens on my 60 mage. cleared ChatLog.lua (and bak) many times.
Released v1.3 Beta for Burning Crusade.
@ Hack: Please read the second note beginning by "I am using a Blizzard (...)" in the Changelogs of ChatLog. Everything is explained here ;)
Our Guild used to use GEM as well but have since converted to Group Calender with great success. It doesn't have the same issues you are talking about that I have noticed at all. I have checked and as I stated no probs. It is very easy to setup and use and also has cooldowns (trade monitoring ones) and lets you track tells if you want to see them while viewing it. I am only mentioning this as a possible option as when the Guild I am in and other Guilds I have been in have used GEM there always seem to be someone who cant set it up right or some other issues like this one that occur to often. Hope this helps and here is the link if you want to look at it http://www.curse-gaming.com/en/wow/addons-2718-1-groupcalendar.html
Good Luck.
PS: Thanks PB for such a great addon as a Guild Leader it is invalauble as I often have so many conversations going that I couldn't do it without this addon.
Sorry about that pb, thats what I get for assuming everyone uses other addons. GEM - Guild Event Manager http://www.curse-gaming.com/en/wow/addons-1592-guildeventmanager.html
Basically we have it setup so that instead of using the 'new' internal guild communication channel we have kept it to a dedicated channel for this addon to communicate with its other users. This channel like many thers uses one of the channels that blizzard lets you use for communications with (in our case its named 'gemdotu' i.e /join gemdotu). For some reason even though I have used the disable button for this channel it still logs it regardless. I have tried a couple of things now and it refuses to stop logging it..
eg: 10/7 18:53:09.828 [4. gemdotu] Playernamel: <GEM2.14>05-1160207908-Name7BName111603304001Karrasame2gg
This addon updates VERY frequently so a 2meg WoWChatLog.txt can very quickly turn into a 10-15meg one instead (over the course of one nights raiding the log file usually gets to about 7meg). The other problem is of course that the log is full of lines about the gemdotu channel in between the actual information I need to refere back to occasionally.
I assume it is possible to filter out what gets saved to the WoWChatLog.txt file is it? or will it just dump everything to that regardless?
Hello Hack,
I'm not sure about what you are calling a "GEM" channel. Could you be clearer? For your problem, the way to disable the channel should be like this: 1) Look at the log of the channel. 2) Click on the "Disable" button at the bottom of the window.
Update for the problem I posted the 8th of October: It seems the bug comes from the "tinsert" function of LUA. I am currently working on a workaround but I couldn't find something that works. More news in the next few days.
thanks for the work that you have put into this mod. Its been great for me to use as one of the main DKP trackers for our guild as I am able to check the history of the chat in the log incase i missed any items off.
I do have one problem though and I have not been able to work it out so far. No matter what I do I can not stop chatlog logging the GEM channel that our guild is using. Obviously with the ammount of updates this sends through the curse of a few hours following a conversation is a absolute nightmare. Do you happen to know why this may happen, and if so a fix? (disabled logging other chans no problems)
A bug still remains, preventing the raid or party chat to display correctly. It seems it is coming from Blizzard's UI. I am looking through the logs and here is what i found:
(...) [434] = "[22:26:49] |Hplayer:<player>|h[<player>]|h: <text>", [435] = "|c00ff7100[22:26:52] |Hplayer:<player>|h[|c00ffff00<player>|r]|h: <text>|r", [438] = "|c00ff7100[22:27:05] |Hplayer:<player>|h[|c00ffff00<player>|r]|h: <text>|r", [439] = "[22:27:14] |Hplayer:<player>|h[<player>]|h: <text>", (...)
The keys of the tables are not correct, going from 1 to 435, then we have 2 empty spaces, and then going again from 438 to 1000. I did not disconnect between the different sentences, so i don't know what happens. And because of this, ChatLog bugs and does not display any log after line 435. It seems that this only happens for raid/party. I have to look where it comes from.
1.2.5 out.
It should correct nearly all the bugs that were still remaining in ChatLog. I recommend to update to this version as quick as possible.
Be sure to delete the WTF\Account\
The "Log new channels" checkbox will surely not work in v1.2.4. I am working intensively on 1.2.5 at the moment, changing a lot of things to improve ChatLog performance & stability. It seems it will produce a quite cool result. More info in the next few days! ;)
1.2.4 out.
Please delete WTF\Account\