Jump to content


Photo

[Fixed] DBM Error in Shadopan monastery


  • Please log in to reply
1 reply to this topic

#1 Aneko

Aneko

    Glass Joe

  • Members
  • 16 posts
  • LocationCalifornia

Posted 07 July 2013 - 02:30 AM

Received this error several times during the first fight in shadopan monastery

7x DBM-Core\DBM-Core-5.3.4-16-gbfbb6d6.lua:4100: Usage: UnitGUID("unit")
<in C code>
DBM-Core\DBM-Core-5.3.4-16-gbfbb6d6.lua:4100: in function <DBM-Core\DBM-Core.lua:4099>
(tail call): ?
DBM-Core\DBM-Core-5.3.4-16-gbfbb6d6.lua:4123: in function "GetBossTarget"
DBM-Party-MoP-5.3.4-16-gbfbb6d6\ShadoPanMonastery\GuCloudStrike.lua:45: in function "func"
DBM-Core\DBM-Core-5.3.4-16-gbfbb6d6.lua:942: in function <DBM-Core\DBM-Core.lua:935>

Locals:
self = <table> {
stats = <table> {}
SPELL_AURA_REMOVED = <func> @DBM-Party-MoP\ShadoPanMonastery\GuCloudStrike.lua:76
inCombatOnlyEventsRegistered = 1
ignoreBestkill = false
modId = "DBM-Party-MoP"
UNIT_DIED = <func> @DBM-Party-MoP\ShadoPanMonastery\GuCloudStrike.lua:101
revision = 9469
creatureId = 56747
OnCombatStart = <func> @DBM-Party-MoP\ShadoPanMonastery\GuCloudStrike.lua:59
StaticFieldTarget = <func> @DBM-Party-MoP\ShadoPanMonastery\GuCloudStrike.lua:44
localization = <table> {}
announces = <table> {}
subTab = 3
SPELL_CAST_START = <func> @DBM-Party-MoP\ShadoPanMonastery\GuCloudStrike.lua:83
categorySort = <table> {}
instanceId = 312
modelId = 39489
hasFlex = false
inCombat = true
noHeroic = false
zones = <table> {}
combatInfo = <table> {}
Options = <table> {}
hasChallenge = true
id = "673"
timers = <table> {}
specwarns = <table> {}
countdowns = <table> {}
addon = <table> {}
hasLFR = false
oneFormat = false
type = "PARTY"
SPELL_AURA_APPLIED = <func> @DBM-Party-MoP\ShadoPanMonastery\GuCloudStrike.lua:64
DefaultOptions = <table> {}
optionCategories = <table> {}
inCombatOnlyEvents = <table> {}
}
uId = nil

#2 MysticalOS

MysticalOS

    French Hacker

  • ♦ Administrators
  • 774 posts
  • LocationGeorgia

Posted 07 July 2013 - 06:12 PM

alpha version error, but is that fixed in latest? i have been unable to test if that's fixed




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users