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
Count: 30
Call Stack:
[C]: ?
Interface\AddOns\Elephant\Core-Interface.lua:128: in function `SetObjectColorWithCurrentLogColor'
Interface\AddOns\Elephant\Core-Interface.lua:13: in function `ShowCurrentLog'
Interface\AddOns\Elephant\Core-Interface.lua:91: in function `Scroll'
Interface\AddOns\Elephant\Core-Initialize.lua:117: in function <Interface\AddOns\Elephant\Core-Initialize.lua:115>
Heres the error with nothing but Elephant enabled. I was able to "Kind of" re-produce it. On any alliance char (I tried once on horde, didnt work)
It seems to happen when you have multiple custom chans. I started new on a fresh server, joined the chan name that usually gives me the error...and nothing. Joined random chan names, and channel 8 always gave me the error. I tried another toon, and same thing. So that should be able to re-produce it...unless it was a fluke twice. (though sometimes early channels like 4 seem to do it too)
Hope this helps figure out the problem...really love the addon :D
Interface\AddOns\Elephant\Core-Interface.lua:170: attempt to index field '?' (a nil value)
Count: 1
Call Stack:
[C]: ?
Interface\AddOns\Elephant\Core-Interface.lua:170: in function `SetObjectColorWithCurrentLogColor'
Interface\AddOns\Elephant\Core-Interface.lua:13: in function `ShowCurrentLog'
Interface\AddOns\Elephant\Core-Interface.lua:7: in function `ChangeLog'
Interface\AddOns\Elephant\FuBar-Dropdown.lua:26: in function `func'
...erface\AddOns\FuBar\libs\Dewdrop-2.0\Dewdrop-2.0.lua:732: in function <...erface\AddOns\FuBar\libs\Dewdrop-2.0\Dewdrop-2.0.lua:671>
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\Elephant\Event-Handle.lua line 24:
attempt to index field '?' (a nil value)
Debug:
(tail call): ?
...\AddOns\AlwaysLFG\Libs\AceEvent-2.0\AceEvent-2.0.lua:303: TriggerEvent()
...\AddOns\AlwaysLFG\Libs\AceEvent-2.0\AceEvent-2.0.lua:910:
...\AddOns\AlwaysLFG\Libs\AceEvent-2.0\AceEvent-2.0.lua:903
ImpIgnore\ImpIgnore.lua:162:
ImpIgnore\ImpIgnore.lua:134
AddOns:
Swatter, v3.1.9 (<%codename%>)
AdvancedTradeSkillWindow, v
AlwaysLFG, v1.1
Babylonian, v5.1.DEV.130
BadBoy, v2.1.1.0
Baggins, vBeta 1
BulkMail2Inbox, v3.0.2
Configator, v5.1.DEV.130
CrapAway, v
DebugLib, v5.1.DEV.130
DoubleWide, v
Elephant, v2.5
EnhTooltip, v5.1.3715 (SnaggleTooth)
EquipCompare, v2.14
ErrorRedirect2, v
FastZoom, v
Gatherer, v3.1.9
HKQuestInitiators, v1.3
ImpIgnore, v
Informant, v5.1.3897 (SnaggleTooth)
LFGSaver, v1.1
LFGVoyeur, v2.5
Outfitter, v4.3.1
PetPicker, v
Possessions, v2.0.2o v5
QuestHelper, v0.80
RareFinder, v20300.1
RatingBuster, v
Reputation, v1.0
SlideBar, v3.1.9 (<%codename%>)
spitfilter, v
Stubby, v5.1.3897 (SnaggleTooth)
TooManyAddons, v
TurnIn, v2.0.9
(ck=2f9)
@ hellboundheart: try deleting all files named "Elephant.lua" in your WTF folder (use the search function of your OS) and login back again. note: all your logs and preferences will be deleted (you can make a backup of each file).
@ manta53: simply by activating the option in... the options ;) the file will be logged into World of Warcraft/Logs/
@ Ikasaru: I never had the bug, that's the problem. If I can't reproduce it, I can't debug it :(
@ zero6: you need the fubar to use the minimap icon, or the fubar2broker addon if you have a bar but not the fubar one.
"Core-interface.lua:128: attempt to index '?'" Error.
most of the time I use it too share what was said at guildmeetings etc and then it would be handy!
ID: 3
Error occured in: Global
Count: 1
Message: ..\AddOns\Elephant\Event-Handle.lua line 24:
attempt to index field '?' (a nil value)
Debug:
(tail call): ?
Ace2\AceEvent-2.0\AceEvent-2.0.lua:303: TriggerEvent()
Ace2\AceEvent-2.0\AceEvent-2.0.lua:910:
Ace2\AceEvent-2.0\AceEvent-2.0.lua:903
AddOns:
Swatter, v3.1.9 (<%codename%>)
Ace2, v
Ace3, v
ACP, v3.0.r12
Align, v
AlphaMap, v3.50.30000
AlphaMapBattlegrounds, v
AlphaMapExteriors, v
AlphaMapInstances, v
AlphaMapWorldBosses, v
AlphaQuestHelper, v1.01.30000
AnchorsAway, v1.0
ArcHUD2, v2.2
ArkInventory, v3.02
Atlas, v1.13.0
AtlasBattlegrounds, v1.13.0
AtlasDungeonLocs, v1.13.0
AtlasOutdoorRaids, v1.13.0
AtlasTransportation, v1.13.0
AtlasLoot, v5.02.03
AtlasMajorCitiesBeta, vBeta 1
AtlasQuest, v4.3.0
AucAdvanced, v5.1.3715 (SnaggleTooth)
AucFilterBasic, v5.1.3715 (SnaggleTooth)
AucFilterOutlier, v5.1.3715.2531
AucMatchUndercut, v5.1.3715.2531
AucScanData, v5.1.3715 (SnaggleTooth)
AucStatClassic, v5.1.3715 (SnaggleTooth)
AucStatHistogram, v5.1.3715 (SnaggleTooth)
AucStatiLevel, v5.1.3715 (SnaggleTooth)
AucStatPurchased, v5.1.3715 (SnaggleTooth)
AucStatSales, v5.1.3715.2842
AucStatSimple, v5.1.3715 (SnaggleTooth)
AucStatStdDev, v5.1.3715 (SnaggleTooth)
AucStatWOWEcon, v5.1.3715.2530
AucUtilAHWindowControl, v5.1.3715.3311
AucUtilAppraiser, v5.1.3715.2530
AucUtilAskPrice, v5.1.3715.3175
AucUtilAutoMagic, v5.1.3715.3142
AucUtilBigPicture, v2.4.3.1
AucUtilCompactUI, v5.1.3715.2530
AucUtilEasyBuyout, v5.1.3715.3583
AucUtilItemSuggest, v5.1.3715.3108
AucUtilPriceLevel, v5.1.3715.2545
AucUtilScanButton, v5.1.3715.2530
AucUtilScanFinish, v5.1.3715.2530
AucUtilScanProgress, v5.1.3715.2530
AucUtilSearchUI, v5.1.3715.3483
AucUtilSimpleAuction, v5.1.3715.3708
AucUtilVendMarkup, v5.1.3715.2530
Auditor2, v3.2.1
AutoAcceptInvite, v1.3
Babylonian, v5.1.DEV.130
Bartender4, v4.2.1
BigBrother, v
BindingsReminder, v0.8-20400
BonusScanner, v4.1
Broker2FuBar, v1.0
Carbonite, v2.01
CCBreakWarner, v
CharacterInfo, v1.0.$Revision: 63453 $
CharacterInfoStorage, v1.0.$Revision: 63452 $
ChatMats, v
ChatThrottleLib, v19
Chronos, v2.12
CmdHelp, v
cMinimapCoordinates, v
ConcessionStand, v0.9.7(Beta)
Configator, v5.1.DEV.130
CoolDownButtons, v2.1.15
CooldownCount, v3.0
CowTip, v
CTRaidTracker, vv1.5.8 (Guild Launch)
CTRASpy, vv1.6
DBMBurningCrusade, v
DBMCore, v
DBMLDB, v
DBMRaidLeadTools, v
DBMSpellTimers, v
DebugLib, v5.1.DEV.130
Deformat, v1.0 $Revision: 3817 $
DewdropLib, v
DrDamage, v1.6.0b
Elephant, v2.5
if this was already mentioned i apologize
i hope you fix meh favourite addon soon! :P
Model Name: iMac
Model Identifier: iMac8,1
Processor Name: Intel Core 2 Duo
Processor Speed: 3.06 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
System Version: Mac OS X 10.5.5 (9F33)
I kept using the old version of Elephant, until today I used the minimap icon on one of my characters to disable it (due to error messages it was giving her, strangely enough), and have since been unable to bring it back up as while the game shows it as taking memory and being active, it won't respond to any of the slash commands.
This bug occured after using my teleportation stone to go back home, once the ui were reloaded I have caught this error spawning:
[2008/11/16 12:19:02-65-x2]: Elephant-2.5\Event-Handle.lua:24: attempt to index field '?' (a nil value)
---
Thanks in advance,
-K
All better now. Great mod! Thank you.
In 2.5 the code has the following in lines 499-501:
elephantCopyFrameButtonHide:SetFont(Fonts.GameFontNormal.Font[1], Fonts.GameFontNormal.Font[2], "OUTLINE")
elephantCopyFrameButtonHide:SetTextColor(Fonts.ChatFontNormal.TextColor[1], Fonts.ChatFontNormal.TextColor[2], Fonts.ChatFontNormal.TextColor[3], Fonts.ChatFontNormal.TextColor[4])
elephantCopyFrameButtonHide:SetText(CLOSE)
In 2.5.1 lines 499-501 have:
elephantCopyFrameButtonHide:GetFontString():SetFont(Fonts.GameFontNormal.Font[1], Fonts.GameFontNormal.Font[2], "OUTLINE")
elephantCopyFrameButtonHide:GetFontString():SetTextColor(Fonts.ChatFontNormal.TextColor[1], Fonts.ChatFontNormal.TextColor[2], Fonts.ChatFontNormal.TextColor[3], Fonts.ChatFontNormal.TextColor[4])
elephantCopyFrameButtonHide:GetFontString():SetText(CLOSE)
By modifying just those lines to the newer ones from 2.5.1, I was able to get 2.5 to reproduce the same crash. It's possible that these are tied into some other change that causes the crash that I don't understand, but I was hoping this information would be helpful. I checked a bunch of the other files in the mod and this seemed to be the only one that had any noticable difference between the two versions.
@ Rivkah: You should submit this bug to the WoW support. I cannot fix a client crash, since an addon shouldn't be able to do so. I feel sorry for you but I really can't do anything about this :/