Post a reply

Twinkielock

Posted 01:12PM, Thursday, October 8, 2009 (2 years, 3 months ago) #0

Whenever I log in I get the following error. Any ideas on how to fix? Thanks. Date: 2009-10-08 12:49:24 ID: -6 Error occured in: Global Count: 1 Message: ..\AddOns\CT_Core\CT_Core.lua line 140: attempt to call method 'modupdate' (a nil value) Debug: [C]: modupdate() CT_Core\CT_Core.lua:140: updateFunc() CT_BarMod\CT_Library.lua:241: CT_BarMod\CT_Library.lua:229 CT_BarMod\CT_Library.lua:304: CT_BarMod\CT_Library.lua:302 AddOns: Swatter, v5.6.4386 (KangaII) Ace2, v AckisRecipeList, v1.0 2501 AdvancedTradeSkillWindow, v AucAdvanced, v5.6.4386 (KangaII) AucDb, v5.1.DEV.3583 AucFilterBasic, v5.6.4386 (KangaII) AucFilterOutlier, v5.6.4386.2531 AucMatchUndercut, v5.6.4386.2531 AucStatHistogram, v5.6.4386 (KangaII) AucStatiLevel, v5.6.4386 (KangaII) AucStatPurchased, v5.6.4386 (KangaII) AucStatSales, v5.6.4386.2842 AucStatSimple, v5.6.4386 (KangaII) AucStatStdDev, v5.6.4386 (KangaII) AucStatWOWEcon, v5.6.4386.2530 AucUtilAHWindowControl, v5.6.4386.3311 AucUtilAppraiser, v5.6.4386.2530 AucUtilAskPrice, v5.6.4386.3175 AucUtilAutoMagic, v5.6.4386.3142 AucUtilBigPicture, v3.1.0.1 AucUtilCompactUI, v5.6.4386.2530 AucUtilEasyBuyout, v5.6.4386.3583 AucUtilItemSuggest, v5.6.4386.3108 AucUtilPriceLevel, v5.6.4386.2545 AucUtilScanButton, v5.6.4386.2530 AucUtilScanFinish, v5.6.4386.2530 AucUtilScanProgress, v5.6.4386.2530 AucUtilSearchUI, v5.6.4386.3655 AucUtilSimpleAuction, v5.6.4386.0 AucUtilVendMarkup, v5.6.4386.2530 Babylonian, v5.1.DEV.130 Bagnon, v2.10.0 BagnonForever, v1.1.2 BagnonTooltips, v BulkBuy, v Carbonite, v3.22 Configator, v5.1.DEV.190 CTBarMod, v3.013 (CTMod 3.0) CTCore, v3.013 (CTMod 3.0) DebugLib, v5.1.DEV.130 Stubby, v5.6.4386 (KangaII) TomTom, v199 BlizRuntimeLib_enUS v3.2.2.30200 <us> (ck=55e)

dargen	Posted 03:42PM, Thursday, October 8, 2009 (2 years, 3 months ago) #1
	The first thing I'd suggest is to update your two CTMod addons (CT_BarMod and CT_Core) to the latest versions. The ones shown in your list of addons are from Jan 2009. Other than that, I don't recall seeing that error back in January, and I'm not experiencing it with the current versions of the addons. Last updated by dargen

Quick Reply