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
Comments
-
AllInOneMighty Owner
-
View User Profile
-
Send Message
Posted Oct 14, 2006when 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.
-
View User Profile
-
Send Message
Posted Oct 13, 2006Released v1.3 Beta for Burning Crusade.
-
View User Profile
-
Send Message
Posted Oct 13, 2006@ Hack: Please read the second note beginning by "I am using a Blizzard (...)" in the Changelogs of ChatLog. Everything is explained here ;)
-
View User Profile
-
Send Message
Posted Oct 12, 2006Our 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.
-
View User Profile
-
Send Message
Posted Oct 12, 2006Sorry 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?
-
View User Profile
-
Send Message
Posted Oct 10, 2006Hello 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.
-
View User Profile
-
Send Message
Posted Oct 10, 2006thanks 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)
-
View User Profile
-
Send Message
Posted Oct 8, 2006A 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.
-
View User Profile
-
Send Message
Posted Oct 8, 20061.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\
-
View User Profile
-
Send Message
Posted Oct 6, 2006The "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! ;)
-
View User Profile
-
Send Message
Posted Oct 6, 20061.2.4 out.
Please delete WTF\Account\
-
View User Profile
-
Send Message
Posted Oct 5, 2006Tomorrow there will be a new release. In this release, it remains a few bugs but it should correct the annoying bug with the Dropdown menu. You WILL have to delete the ChatLog.lua file in your SavedVariables folder. I will post an Howto guide though :)
EDIT: Because of remaining bugs, I did not add the new scroll buttons. I want to have something very stable before adding anything.
-
View User Profile
-
Send Message
Posted Sep 29, 2006thanks to pb_ee1
when we use Itemdb, chatlog_whispers channel log these db, so i want to add a new channel,it merely logs these db...
-
View User Profile
-
Send Message
Posted Sep 28, 2006You should try this:
1) Logout from the game 2) Delete the file: World of Warcraft\WTF\Account\<Your_Account>\<Your_Server>\<Your_Character>\SavedVariables\ChatLog.lua 3) Run the game.
This should fix the bug until the next release ;)
-
View User Profile
-
Send Message
Posted Sep 28, 2006Is there anyway for you to post a temporary fix to version 1.2.3 so I can get the addon back up and running? Or will you be releasing the updated version within the next few days?
Thanks for looking into it so quickly.
-
View User Profile
-
Send Message
Posted Sep 26, 2006I just went through the code two minutes ago and I found a few stupid bugs that I have corrected. I am really happy with what I found, because it seems it is going to fix nearly all the errors that ChatLog users have at the moment.
The only thing I am not sure about at the moment is if the raid chat display will work again as expected. I am going to test a bit more and see if everything is OK. Additionnally, I will add two buttons to scroll the chat more rapidly ; and if everything is fine (hopefully), there will be a new release... with a chinese localization, thanks to wolftankk!
-
View User Profile
-
Send Message
Posted Sep 26, 2006Hum... this IS indeed strange. I'll have to go through the whole AddOn, I think, in order to find where the bug is located. It seems there are a few things not right at the moment, I have to take a few hours and to go through everything in order to see if something is wrong.
This bug is not normal but it will be fixed. The other bug regarding the raid channel being not properly displayed is strange too, but I supose that I will find it with a bit of patience ;)
Thanks for your reports, though :)
EDIT: The "debug" channel ID is here for debugging purpose. I hope it will help me in debugging ;p
-
View User Profile
-
Send Message
Posted Sep 25, 2006Well it was basically cycling thru all ur saved channels and it was coming across a channel with no "name" field. You have to open the ChatLog.lua file in:
[WoW Installation Folder]\WTF\Account\[Account Name]\[Server]\[Toon Name]\Saved Variables\.
Mine was the last entry in the file, but if u search for '["id"] = "debug"', it should bring u to the entry. Just delete it and it should remove the error.
-
View User Profile
-
Send Message
Posted Sep 24, 2006Whenever I try to change the channel I get the same error. Either by clicking on the arrow up top, or right clicking on the chat log screen.
Interface\AddOns\ChatLog\ChatLog.lua:591:bad argument #1 to 'gsub' (string expected, got nil)
I even made sure I had the latest version downloaded and I am using 1.2.3.
Any thoughts?
-
View User Profile
-
Send Message
Posted Sep 23, 2006At first the addon worked great. Loved it. Then after the first night of Use I moved the WowChatlog.txt to a different directory to parse. When I re-entered game the next day when I would try to change what channel is displayed in wow Chat log by clicking the Icon (Arrow on a 3/4 circle) in the top left this error pops up. Interface\Addons\ChatLog\ChatLog.lua:591: bad argument #1 to 'gsub' (string expected, got nil)
I tried deleting the addon folder and the chatlog.lua file started wow, then closed wow, resinstalled the addon, restarted wow and still got the same error.