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
plz fix:
Locale-deDE.lua
L['maxlogwords'] = "Maximale Logl/195/164nge"
into
L['maxlogwords'] = "Maximale Logl\195\164nge"
Done.
aloha ,
good day sir :) i dont know if someone asked or not but elephant is wonderful and it shows me the right stuff and also shows the whispers form the battle.net accounts but if i want to copy and paste for example a link someone has sent me then the battle.net whispers dont show up in the "copy/paste" window it only says the time i logged on and thats it...and with normal whispers it does show up in the "copy/paste" window..
so is it something i missed or is this with purpose not working?
thnx for your time :)
The Battle.net messages are not logged for privacy and security purposes. Actually, the WoW API does not permit getting the real names of your contacts when saving to SavedVariables :(
Im using prat and I can make real id and battletag contacts appear with the current toon name. With prat features enabled in elephant, I see the same there. I can also copy the chat using prat without any restrictions.
coolio thnx for the reply :)
Hi,
thanks for the addon, I´m an officer and sometimes need to keep trakck of several conversations at the same time, so it´s a life saver for me :)
I wanted to ask you for a feature though - I use the addon www.curse.com/addons/wow/oqueue which uses a cross-realm meash by sending real ID whispers between the users of this addon every 0.5 seconds. This quickly floods my elephant log so I can´t find older stuff whenever I use the addon.
Each of the whispers starts with OQ, so I wanted to ask if it would be possible to exclude such whispers from being logged?
Thanks*G
Two things to your request:
1) The addon you're using is badly developed. No addon is supposed to use chats for its features, and if it is the case, it's either playing with rules or not coded correctly, especially since the http://www.wowwiki.com/API_SendAddonMessage function now supports WHISPER.
2) You could filter these specific chats if the addon was using a specific channel; but it's not, so I don't have a simple solution for you here, besides contacting the original authors of oQueue and ask them to modify their addon.
Hi,
thanks for the swift reply, I appreciate it :) Unfortunately, I don´t think that the addon can be modified to not use whispers, as the cross-realm meshing can only be done thanks to having users of the addon on individual realms act as relays via Real ID chat. No other channel of communication is available for cross-realm boundaries and since the purpose of the addon is to facilitate creation of cross-realm PUGs, if that feature was removed, the addon would lose its core functionality.
The whispers sent by the addon follow a strict formatting though and the "header" of each whisper is the same. If I could prevent them from being recorded by Elephant via some filter, it would make my life much easier :) Also, the addon has slightly over 250K monthly downloads, so I can imagine that if you were to implement such feature, it would be a great quality of life improvement for many users of Elephant besides me :)
Thanks*G
So I'm pretty sure the addon can be modified to use SendAddonMessage, since it's already sending its messages through the WHISPER pipeline (that's how you contact your real ID friends; see http://www.wowwiki.com/ChatTypeId: it does not contain any specific BATTLE_NET value). Switching from SendChatMessage to SendAddonMessage, while still using WHISPER, should do the trick.
At least, the author should try it out ;)
Thank you very much, I´ll contact the author of the addon and suggest this then :)
I am having a problem. In the System Messages log on this addon, I see something like this:
23:36:40 No player named 'Zilkia' is currently playing.
23:37:18 No player named 'Tathr' is currently playing.
23:37:33 No player named 'Rhilyn' is currently playing.
23:37:46 No player named 'Khazira' is currently playing.
23:37:58 No player named 'Fayndor' is currently playing.
23:38:08 No player named 'Skakin' is currently playing.
23:38:17 No player named 'Corska' is currently playing.
23:38:19 No player named 'Kaieo' is currently playing.
I don't know any of these people. I never know the names. And I only see this spam on the addon, not in my chat box. Is anyone else having this issue?
I think that's another addon that's spam this log and filter the messages for the chat out.
Yep I think this is the problem.
Hi,
I like Elephant very much and it's really great and simple.
But is it possible to log more than 1000 lines of Chat? I modified my Elephant to the maximum of 10.000 lines of chat. Is it possible to make this change in the standard addon too? So I don't have to modify the addon on every update.
I very much agree with this. Elephant is a great addon and I'm very grateful for the effort you put in to it.
But like Zwixx 1000 lines of chat is no where near enough for my needs, and it's a needless hassle to constantly have to modify the code each time an update occurs. If you could consider changing that to allow a much higher limit that would be great.
Even if you might need to add in a warning for high values about "hey, do you really want to do this?"
Personally I set the limit to something like 1,000,000 lines . At least text doesn't take much space to store!
I'm considering it for another release. The concern I had when adding this limit was that it is a memory hog. I think we can kind of ignore this now as most computers have sufficient RAM to handle a much longer log. I think this deserves a warning though, I agree.
NOTE: This issue was not Elephant's fault!
I have file logging (normal chat) enabled on all of my characters, and yet when I went to look at my WoWChatLog.txt file today, I was extremely dismayed to find that none of the chat for the past month or so (since 5/31) had been properly logged except for the server message that pops up first thing when you log in. To wit:
7/7 08:23:17.722 Welcome to Patch 5.3: Escalation!
7/7 08:23:17.722 Please be sure to reset your UI and update
7/7 08:23:17.722 any AddOns. For more information, please
7/7 08:23:17.722 visit: http://battle.net/support
7/7 08:52:43.367 Unknown macro option: focustarget
7/7 08:52:43.367 Welcome to Patch 5.3: Escalation!
7/7 08:52:43.367 Please be sure to reset your UI and update
7/7 08:52:43.367 any AddOns. For more information, please
7/7 08:52:43.367 visit: http://battle.net/support
I did manually use the /chatlog command tonight, and it logged chat properly from when I gave the command until I logged off again.
Having Elephant be the only addon loaded does fix this.
Update: And after two hours of digging (yeeikes) I finally determined that it was Niggles that was causing the issue. Apparently its "log chat" setting FORCED chat to be logged or not logged, so Elephant was loading, and then Niggles was loading, and that was why it only caught a very tiny part of chat. Too bad, because it sure did do a lot of useful things.
NOTE: This issue wasn't either addon's fault!
It was 2 addons trying to do the same thing. Elephant's tooltip even warns 'You shouldn't let two different addons control logging".
This really boils down to initialisation order. Since WoW initialises in alphabetical order, If Elephant had been called 'Zebra' or Niggles had been called 'Complaints', you would seen no issues because Niggles would have been initialised before Elephant, so Elephant's control of the logging would have been last and therefore active.
That being said, I have tweaked Niggle's initialisation code so that it assumes the default position, which is that logging is disabled. It doesn't enforce this by specifically disabling logging, unless it has previously enabled logging and the setting is changed. This should mean less chance of conflict with other addons.
By the way, if Elephant does the same as Niggles and simply turns the logging on, why couldn't you just turn on the option in Niggles as well? Surely that would have achieved your aim, namely all chat logged?
I think a way to avoid that is to mark Nibble as an optional dependency of Elephant. That way, WoW would first load Nibble and then Elephant (since it's an optional dependency). Not sure of this though, I'll have to investigate.