Closed GoogleCodeExporter closed 8 years ago
I'm not aware of any conflicting addons, but could you list the ones you're
using?
Also, do you have Lua errors enabled in-game? If not, try enabling them and
then
testing _NPCScan with a common mob in Dalaran like Applebough (ID 29547).
Original comment by saiket....@gmail.com
on 29 Jul 2009 at 8:16
I am using so many addons, and have been the entire time I've been using
NPCScan,
even when it was working properly. I do have an error wrangler installed and I
get
some errors when I first log in and mouse over or click certain things, but
only once
and only when I first log in. I'm pretty sure none of them pertain to NPCScan,
but I
will take closer note to them next time I enter game.
Original comment by stealing...@gmail.com
on 29 Jul 2009 at 8:23
Could you try the Test Found Alert button as well to see if the alert can show
at
all? It should work the same way, but if it doesn't, that might mean something.
Original comment by saiket....@gmail.com
on 29 Jul 2009 at 8:28
Yes, I have tested the Found Alert numerous times, all sucessfully. The alert
tests
fine, the addon scans the cache and flags the creatures as found. No alert, no
error, nothing to notify me that the NPC was nearby other than the red x next
to the
name in the settings.
Original comment by stealing...@gmail.com
on 29 Jul 2009 at 8:32
Here are the two errors I get every time I log in (1st) and when I click an
enemy
player (2nd). Neither effect NPCScan as I can see.
Date: 2009-07-29 20:05:32
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\Grid\GridStatusAggro.lua line 159:
attempt to compare number with nil
Debug:
...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:25:
...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:23
...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:1055: ManualEnable()
...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:983:
...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:976
[C]: ?
...rface\AddOns\oRA2\Libs\AceEvent-2.0\AceEvent-2.0.lua:260: TriggerEvent()
...rface\AddOns\oRA2\Libs\AceEvent-2.0\AceEvent-2.0.lua:910:
...rface\AddOns\oRA2\Libs\AceEvent-2.0\AceEvent-2.0.lua:903
AddOns:
Swatter, v3.1.13 (<%codename%>)
NPCScan, v3.1.0.1
Ace3, v
agExtras, vr696-release
agUnitFrames, vr696-release
Atlas, v1.14.1
AtlasBattlegrounds, v1.14.1
AtlasDungeonLocs, v1.14.1
AtlasOutdoorRaids, v1.14.1
AtlasTransportation, v1.14.1
AtlasLoot, vv5.05.00
AtlasLootBurningCrusade, vv5.05.00
AtlasLootCrafting, vv5.05.00
AtlasLootOriginalWoW, vv5.05.00
AtlasLootWorldEvents, vv5.05.00
AtlasLootWrathoftheLichKing, vv5.05.00
AuctionLite, v1.1
Babylonian, v5.1.DEV.130
Bagnon, v1.7.1
BagnonForever, v1.1.1
BagnonTooltips, v
BonusScanner, v4.8
BrokerBonusScanner, v1.1
ButtonFacade, v3.0.211
ButtonFacadeCaith, v3.0.44
CBHViewport, v100
ClassTimer, v2.2
Configator, v5.1.DEV.190
CowTip, v
DBMBurningCrusade, v
DBMCore, v
DHUD, vv1.5.30000k
FlightMap, v
Gatherer, v3.1.13
GathererHUD, v3.1.13
Grid, v1.30000.2009021101
ItemDataCache, v1.13
ItemRack, v
Macaroon, v30100.1.10
MacaroonBound, v30100.1
MacaroonExtensions, vbeta.1
MacaroonXP, v30100.1
MacaroonXtras, v30100.1
MikScrollingBattleText, v5.4.58
Omen, v3.0.7
oRA2, v2.0.$Revision: 657 $
Prat30, v3.1.0
Prat30HighCPUUsageModules, v
Prat30Libraries, v
QBar, v09.03.08
RatingBuster, v
Rawr, v3.0.3.3
SellJunk, v2.4
simpleMinimap, v30000-5
SlideBar, v3.1.13 (<%codename%>)
TankPoints, v
Titan, v4.1.9.30100 - Revision 216
TitanAmmo, v4.1.9.30100
TitanBag, v4.1.9.30100
TitanClock, v4.1.9.30100
TitanCoords, v4.1.9.30100
TitanDurability, v1.16
TitanGoldTracker, v4.1.9.30100
TitanItemDed, v3.2
TitanLootType, v4.1.9.30100
TitanPerformance, v4.1.9.30100
TitanRegen, v4.1.9.30100
TitanRepair, v4.1.9.30100
TitanVolume, v4.1.9.30100
TitanXP, v4.1.9.30100
XLoot, v0.9
XLootGroup, v0.5
XLootMaster, v0.7
XLootMonitor, v0.7
(ck=716)
Date: 2009-07-29 20:06:20
ID: 3
Error occured in: Global
Count: 1
Message: ..\AddOns\DHUD\DHUD.lua line 2450:
TexCoord out of range
Debug:
[C]: ?
[C]: SetTexCoord()
DHUD\DHUD.lua:2450: SetBarHeight()
DHUD\DHUD.lua:3078: UpdateValues()
DHUD\DHUD.lua:1745: TargetChanged()
DHUD\DHUD.lua:572: OnEvent()
[string "*:OnEvent"]:1:
[string "*:OnEvent"]:1
[C]: CameraOrSelectOrMoveStop()
[string "CAMERAORSELECTORMOVE"]:4:
[string "CAMERAORSELECTORMOVE"]:1
AddOns:
Swatter, v3.1.13 (<%codename%>)
NPCScan, v3.1.0.1
Ace3, v
agExtras, vr696-release
agUnitFrames, vr696-release
Atlas, v1.14.1
AtlasBattlegrounds, v1.14.1
AtlasDungeonLocs, v1.14.1
AtlasOutdoorRaids, v1.14.1
AtlasTransportation, v1.14.1
AtlasLoot, vv5.05.00
AtlasLootBurningCrusade, vv5.05.00
AtlasLootCrafting, vv5.05.00
AtlasLootOriginalWoW, vv5.05.00
AtlasLootWorldEvents, vv5.05.00
AtlasLootWrathoftheLichKing, vv5.05.00
AuctionLite, v1.1
Babylonian, v5.1.DEV.130
Bagnon, v1.7.1
BagnonForever, v1.1.1
BagnonTooltips, v
BonusScanner, v4.8
BrokerBonusScanner, v1.1
ButtonFacade, v3.0.211
ButtonFacadeCaith, v3.0.44
CBHViewport, v100
ClassTimer, v2.2
Configator, v5.1.DEV.190
CowTip, v
DBMBurningCrusade, v
DBMCore, v
DHUD, vv1.5.30000k
FlightMap, v
Gatherer, v3.1.13
GathererHUD, v3.1.13
Grid, v1.30000.2009021101
ItemDataCache, v1.13
ItemRack, v
Macaroon, v30100.1.10
MacaroonBound, v30100.1
MacaroonExtensions, vbeta.1
MacaroonXP, v30100.1
MacaroonXtras, v30100.1
MikScrollingBattleText, v5.4.58
Omen, v3.0.7
oRA2, v2.0.$Revision: 657 $
Prat30, v3.1.0
Prat30HighCPUUsageModules, v
Prat30Libraries, v
QBar, v09.03.08
RatingBuster, v
Rawr, v3.0.3.3
SellJunk, v2.4
simpleMinimap, v30000-5
SlideBar, v3.1.13 (<%codename%>)
TankPoints, v
Titan, v4.1.9.30100 - Revision 216
TitanAmmo, v4.1.9.30100
TitanBag, v4.1.9.30100
TitanClock, v4.1.9.30100
TitanCoords, v4.1.9.30100
TitanDurability, v1.16
TitanGoldTracker, v4.1.9.30100
TitanItemDed, v3.2
TitanLootType, v4.1.9.30100
TitanPerformance, v4.1.9.30100
TitanRegen, v4.1.9.30100
TitanRepair, v4.1.9.30100
TitanVolume, v4.1.9.30100
TitanXP, v4.1.9.30100
XLoot, v0.9
XLootGroup, v0.5
XLootMaster, v0.7
XLootMonitor, v0.7
(ck=716)
Original comment by stealing...@gmail.com
on 30 Jul 2009 at 3:07
Yeah, neither of those would affect it. I'm at a loss for what could be
causing it,
but I put together a special version of the mod to help find the cause. It just
prints a bunch of status messages to your chat window when showing alerts.
Could you
screenshot the results of a quick test with the Test Found Alert button and
finding a
mob after clearing your cache?
Original comment by saiket....@gmail.com
on 30 Jul 2009 at 3:37
Attachments:
Absolutely! I'll install it now and run a test as soon as I can. Wow, I feel
so
honored that you're spending time to troubleshoot this. <.< *looks for a
"donate"
button*
Original comment by stealing...@gmail.com
on 30 Jul 2009 at 4:44
Tested this morning:
Test screen alert works like normal (screen shot attached); added Applebough,
hearthed to Dal, rode around and got the alert for him (also attached). So
either
it's fixed or just the Frostbitten mobs are broken for me. Made a circuit
around
Sholazar but no rares were in attendance, so I suppose I will keep on looking
until I
know I have found one and see if the addon alerts me. I hope that even if the
alert
doesn't sound the text printing to chat will notify me.
Thank you very much again, and I will let you know how it works out.
Original comment by stealing...@gmail.com
on 30 Jul 2009 at 4:10
Attachments:
I feel kind of silly for not thinking of this sooner, but do you have "Search
for
Tamable NPCs" enabled? I forgot that in Sholazar Basin, all three rares are
tamable
(Loque'nahak, Aotona, and King Krush). That would explain why no alert played.
As
for Old Crystalbark not showing an alert, had you already killed him before
testing
the alert out? If so, the "Search for completed Achievement NPCs" option will
let
the alert show even for rares you don't need anymore.
The spam in those screenshots looks normal, so feel free to go back to the
spam-free
version.
Original comment by saiket....@gmail.com
on 30 Jul 2009 at 10:40
You know, I don't think I do have "Tamable NPCs" checked; that makes entirely
too
much sense. BUT, I have "completed Achievement NPCs" checked constantly, as
sometimes the blues sell well and the gold and cloth are nice, but on top of
that,
the example of Crystalbark that I listed was the very first time I'd ever seen
him in
game. Never before had I killed him, seen an alert (back when they were
working) or
had a red x next to his name, so I know that isn't the issue. Similar happened
with
High Thane Jorfus; my girlfriend and I were doing our tourny dailies and she
got an
alert for him and I got nothing, even as we spotted him and killed him. Does
this
verbose version you provided still print the text even if the alert doesn't go
off?
I wonder. I think I'll keep using it just in case, as if it does, I'll still
notice
and won't keep spamming the damn macro I've made in the interim. :-/
Thanks again!
Original comment by stealing...@gmail.com
on 30 Jul 2009 at 11:11
That verbose version will only print something if _NPCScan is actually looking
for
the mob. I suspect that it simply wasn't looking for Crystalbark, since the
button
seems to work properly.
Could you take a screenshot of the Frostbitten rares list? Hopefully it will
reveal
something, because I can't think of what is failing.
Original comment by saiket....@gmail.com
on 31 Jul 2009 at 12:48
Well, it's happened now with two mobs (that I know of; Crystalbark and Jorfus)
that I
had never killed before and are not tamable. I'll send you a screen shot when
I can.
And seriously, is there a donate button somewhere that I'm not seeing on wowinterface?
Original comment by stealing...@gmail.com
on 31 Jul 2009 at 1:04
Usually for WowInterface, there's a little popup thing that appears when you
download, but once you disable one of them, they all get hidden. _NPCScan's
documentation on my website
(http://sites.google.com/site/wowsaiket/Add-Ons/NPCScan)
has a button at the bottom of the page though. I tried to keep them out of the
way,
but I might have hidden them a little too well. ;)
Original comment by saiket....@gmail.com
on 31 Jul 2009 at 2:19
[deleted comment]
I released a new version for 3.2, but it won't affect this issue. Hopefully it
was
just a fluke and won't come back. Thanks for your donation, by the way; I
appreciate
it. :)
Original comment by saiket....@gmail.com
on 6 Aug 2009 at 12:54
I am having the same (or a very similar) issue. I clear the cache regularly and
check it regularly. I have found 4 rare mobs in the last two days for which
there
was no alert. Test button works great. Both tamable and already done boxes
checked. I am running a lot fewer add-ons that the previous poster -
auctioneer,
gatherer, omen, dbm, minicoords, cartographer. Problem since the last patch or
two,
really. Man, I hate spamming those macros again.
This mod was the best when it was working for me :-(
Original comment by allan.br...@gmail.com
on 5 Sep 2009 at 1:15
VINDICATION! :P
Yes, the newer version that you had put out didn't fix the issue for me, but I
haven't been playing much at all for a while, so haven't thought about it.
While I'm
sorry to see that others are having a trouble, it's nice to know that this
error can
be replicated.
Original comment by stealing...@gmail.com
on 5 Sep 2009 at 6:27
Im seeing the same fault since the last big patch (three patchs ago, i.e. first
toc
patch)
Steps taken so far:
Deleted addon
Delete Cache
Deleted WTF folder
Reloaded latest addon
Checked both "Search for Tamable NPCs" enabled? and the killed already box (cos
would want to kill them again for the gold :-)
Test bitton works perfect.
I get no errors when loading wow.
And yet I keep getting new rares marked as seen in the addon...but no alerts
Frustrating as this is a great addon when it worked
The only thing that looks out of place is the wow addon screen (before you
select
your toon and enter the game) the color for _NPCscan is diffrence to all the
other
addons listed (yellow rather than brownie).... I also use the addon called
"addon"
and it also shows _npcscan a different color... might not be relevent but dont
seem
to recall this diffrent color from when it was working?
If you want a full list of my addons or screen shot I will add once I get a few
more
rares spotted and not alerted.
Cheers
Original comment by chrishoo...@xtra.co.nz
on 29 Sep 2009 at 5:08
[deleted comment]
The latest version, 3.2.0.7, is modified slightly to make this bug easier to
find.
It prints more detailed messages to chat when you find tamable mobs. If you
ever see
_NPCScan print a message to chat, could you copy it back to here? I never did
really
find the cause for this issue, but hopefully the new messages will give me a
hint.
Just to be sure however, could you make sure that both achievements are enabled
in
the configuration window? The checkboxes are pretty small, just to the left of
the
text on the achievements' tabs, and might be hard to see when they're unchecked.
Original comment by saiket....@gmail.com
on 29 Sep 2009 at 5:51
Oh, I forgot to mention that the color of the name text is intentional; It's
just a
stylistic trend I name all my mods with. The "_" at the front shows the right
color.
Original comment by saiket....@gmail.com
on 29 Sep 2009 at 5:55
Flying around spamming macro and NPC picked up on rare and alerted first time
in a
month or so.
The only thing I changed was enabling the achivement tracking as you suggested.
I wonder how / why this made a difference?
Original comment by chrishoo...@xtra.co.nz
on 30 Sep 2009 at 9:12
[deleted comment]
That checkbox turns on/off *all* scans for mobs that are part of the
achievement, so
disabling "Frostbitten" would stop scans for all Northrend rares. I'll try and
make
that more prominent, since I think the original poster of this issue might have
missed it too.
Original comment by saiket....@gmail.com
on 30 Sep 2009 at 5:00
Found another one today so with the track achive button checked its all good.
Some suggestions for you.
1. rename this thread back to alert not alerting etc...so other people can find
the
issue.
2. update your install notes to recommend that if your hunting for noc's then
check
the achive box.
Thanks for your help on this much appreciated
Original comment by chrishoo...@xtra.co.nz
on 1 Oct 2009 at 11:16
Achievement search checkboxes now show red "X"s for improved visibility.
Original comment by saiket....@gmail.com
on 5 Dec 2009 at 1:32
Original issue reported on code.google.com by
stealing...@gmail.com
on 29 Jul 2009 at 3:54