이 사이트는 자바스크립트를 사용합니다.
브라우저에서 자바스크립트를 활성화 해주십시오.
라이브
PTR
10.2.7
PTR
10.2.6
베타
"Inspect UI" LUA error
답글 달기
보드 인덱스로 돌아가기
lockspwnbruh
의 게시글
Message: ...face\AddOns\Blizzard_InspectUI\InspectGuildFrame.lua:18: Usage: GetGuildInfo("unit")
Time: 02/24/11 18:00:12
Count: 5
Stack: : in function `GetGuildInfo'
...face\AddOns\Blizzard_InspectUI\InspectGuildFrame.lua:18: in function `InspectGuildFrame_Update'
...face\AddOns\Blizzard_InspectUI\InspectGuildFrame.lua:8: in function <...face\AddOns\Blizzard_InspectUI\InspectGuildFrame.lua:6>
Locals: (*temporary) = nil
Been getting it randomly all day, tried repair, no mods nothing seemed to stop it, any tips?(##RESPBREAK##)12##DELIM##MasterOfDisguise##DELIM##Moved to UI & Macros.
Wanderingfox
의 게시글
Trash your wtf and interface folders. Let wow rebuild them from scratch. Try again.
lockspwnbruh
의 게시글
Have tried it, still getting it. Seems like more often now even.
Wanderingfox
의 게시글
Run repair.exe then. Something is corrupting the files since trashing your interface folder should have forced that to rebuild from scratch.
lockspwnbruh
의 게시글
Still happens, seems to occur in groups. Increasing in frequency with more players nearby.
Wanderingfox
의 게시글
Just to clarify, this is with no addons after deleting your WTF and Interface folders, as well as running the repair.exe file?
If that's the case, then it sounds like a corruption in the mpq files... which means you need to reinstall.
296835
의 게시글
This post was from a user who has deleted their account.
lockspwnbruh
의 게시글
This is a bug in Blizzard code. Repairing/reinstalling will not fix it.
Then what's your reccomendation?
pelf
의 게시글
This is a bug in Blizzard code. Repairing/reinstalling will not fix it.
If the reason for your assessment is the stack trace, that's not enough to pin it on Blizzard code. If you're combining that with the previous recommendation that the WTF/Interface folders be regenerated, it wasn't yet confirmed that was done and that the error occurs not only after a regenerate, but also without any addons running.
oscarucb
의 게시글
I know this thread is old, but didn't see the right answer posted anywhere on this site, so here it is for future users searching the threads:
These errors are caused by poor API design leading to interference between the Blizzard Inspect frame and other addons.
A workaround/fix addon is available on curse (InspectFix):
http://wow.curse.com/downloads/wow-addons/details/inspectfix.aspx
답글 달기
로그인이 되어있지 않습니다. 답글을 달려면
로그인
하거나, 계정이 없다면
회원가입
을 해 주세요.