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 Aug 19, 2006My game freezes right after the loading bars complete and right when the world starts to load ever since i installed 1.2. only freezes on 1 of my characters and ok for everything else. i disabled all addons except chatlog, and it freezes up. if i turn off chatlog, then it doesnt freeze.
edit: i loaded 1.1.5, and it was fine loading up like before. now when i opened up chatlog (1.1.5), and tried to open the log of the channel with CTRaidAssist, it freezes up.
-
View User Profile
-
Send Message
Posted Aug 18, 2006Wow! Thanks for this bug report guest10, I'm going to look very closely to this ;) But it seems the problem is not only here, because I have exactly the same error even if I don't join 10 channels (it's very rare, but it happens sometimes). I'll add a fix for the problem you discovered in the next release.
I'm going to see for a confirmation dialog, too :)
Cheers
-
View User Profile
-
Send Message
Posted Aug 18, 2006The "Clear all" button is kinda close to a few buttons below it. One mis-click and it's all gone, perhaps a confirmation dialog might be a good idea. Thank you.
-
View User Profile
-
Send Message
Posted Aug 18, 2006Did a little debugging and I've identified the source of the problem.
Join 10 channels, join #11, result: event="CHAT_MSG_CHANNEL_NOTICE", arg1="YOU_JOINED", arg8=0
Also it's possible for: event="CHAT_MSG_CHANNEL", arg8=0
fix: if (event == "CHAT_MSG_CHANNEL_NOTICE" and arg8~=0) then if (event == "CHAT_MSG_CHANNEL" and arg8~=0) then
-
View User Profile
-
Send Message
Posted Aug 17, 2006New bug discovered: the AddOn does not actually "cut" the table when its size goes over 200 lines. I have 20438 lines saved in my ChatLog.lua file !
The good thing is that it seems that ChatLog is able to log so many lines without any problems, the bad is that a new bug has to be fixed ;p I'm working on it.
EDIT: This is only true for custom channels.
-
View User Profile
-
Send Message
Posted Aug 17, 2006Hum... It seems the problem with the "bad argument #1 to `lower' (string expected, got nil)" error is not completely fixed, this is why it maybe gives this error sometimes. I don't know exactly why, but it seems that sometimes the Blizzard UI doesn't give the name of the channel when you join/quit a channel or else.
I couldn't reproduce consecutively this bug with the AddOn, so I still don't know very well where the problem is. I hope we will find something in the next few weeks (the users & me).
Thanks for the bug report though :)
-
View User Profile
-
Send Message
Posted Aug 17, 2006I dont know how it happened but I had the following entry in my savedvariables: [36] = { ["enabled"] = 1, ["logs"] = { }, },
And was getting nil errors, perhaps you can validate the saved data on load and toss out any invalid channels; ie ["name"] = nil.
-
View User Profile
-
Send Message
Posted Aug 13, 2006I discovered a very big bug in the Enable/Disable logs functionnality. If you disable logs for a specific channel, it still logs it. I will fix this bug in the next release.
Thanks to NiGHTsC for this report ;)
-
View User Profile
-
Send Message
Posted Aug 13, 2006Ok, I also had this error but I can't find where the problem is. What I will do is just add a check function to prevent this error from displaying. It will be available in the next release. I have fortunately one week to work on it ;)
-
View User Profile
-
Send Message
Posted Jul 30, 2006i'm alos getting this error and i'm using the english client
Count: 2 Error: Interface\AddOns\ChatLog\ChatLog.lua:242: bad argument #1 to `lower' (string expected, got nil)
-
View User Profile
-
Send Message
Posted Jul 26, 2006It was what I was thinking: this problem appears only on German clients. I don't really know how to fix it, maybe it is quite simple, but unfortunately I don't have the German client installed on my computer. If someone has a bit of knowledge in AddOns, maybe you could help me find how to delete this bug.
Additionaly to this, I wanted to say that I am currently working (and I will do so for the whole hollidays) and that I consequently don't have much time to work on the AddOn. I will obviously continue to develop it when I will have a bit of free time.
-
View User Profile
-
Send Message
Posted Jul 24, 2006The following error message popped up when speaking in a party (no private chats were going on): "ChatLog.lua:242: bad argument #1 to 'lower' (string expected, got nil)"
--> same prob! (maybe prob with german umlauts eg specialchars?)
-
View User Profile
-
Send Message
Posted Jul 19, 2006How does "Enable/Disable all logs" works? I disabled them but it still log all chats in Chatlog screen.
-
View User Profile
-
Send Message
Posted Jul 15, 2006I didn't have this problem, this is quite strange... I am going to look closely to this :/
(You can use an older release instead ;) )
-
View User Profile
-
Send Message
Posted Jul 15, 2006ChatLog 1.1.4, WoW 1.11.2.
The following error message popped up when speaking in a party (no private chats were going on): "ChatLog.lua:242: bad argument #1 to 'lower' (string expected, got nil)"
i have the same problem occurs when im in a a raid and the party speaks i believe or could be cause i am in a raid not sure. had to disable chatlog like log out and stop it from loading to prevent this just disabling the mod didnt fix it. thx
-
View User Profile
-
Send Message
Posted Jul 14, 2006The only way to display the log file into a readable way is to develop a program under Windows that does this ;) It is impossible at the moment to log only what you would like.
Just check four posts under this one, I explained where was the problem :)
-
View User Profile
-
Send Message
Posted Jul 14, 2006So no chance to actually use the chatlog function corretyl? LOL really. How the hell should I suppose to read the log files? I see lots of jiberish only. :( Should I decode it or something? :\
-
View User Profile
-
Send Message
Posted Jul 14, 2006Elcromo, which client are you using? Did you join a specific channel during this discussion? Are you using channels with special characters (â, ë, è, é, ...)?
It's quite difficult to know where the problem is coming from with the information you gave ;)
-
View User Profile
-
Send Message
Posted Jul 13, 2006ChatLog 1.1.4, WoW 1.11.2.
The following error message popped up when speaking in a party (no private chats were going on): "ChatLog.lua:242: bad argument #1 to 'lower' (string expected, got nil)"
-
View User Profile
-
Send Message
Posted Jul 12, 2006There is a big problem with the option of saving to a file: these functions are Blizzard functions, not mine, and you can't change anything to them. You can just enable or disable the logging. And in fact, these functions do log everything that appears (or even not) on your screen, and I can't change anything to this.
It is exactly the same than typing /chatlog or /combatlog at the chat prompt (it will only work if you haven't enabled ChatLog - the AddOn automaticaly disables these command). So you can't log only certain chats except if you leave the ones you don't want to log, and I can't really tell when the log is saved (but I'm pretty sure it is saved at the same times than your variables, so it should be when you log out).
I'll add an option to enable/disable logging by default when you join a new channel, or only to do this if it is a General, etc. channels. I'm really upset to say this, but I don't have time at the moment to work on the AddOn. I'll try to do something during the weekends ;)
@ metal: A - Increasing the limit so much will surely slow down the AddOn too much, and it will take something like 1 minute to log only ChatLog. I don't want this to happen, so until I don't change the code a bit, I won't increase the maximum log size ;)
B - Good idea, added to the ToDo list.
C - I just talked about it above ;)
D - Good idea too, I'll add this if I find some space on the window :P