You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
When addon is enabled, opening any profession window causes the game to crash with more recent Nampower releases #42
Hello, thank you for this addon I cannot play without. This is a bit of a longshot, but as I asked the nampower dev about this issue and we couldn't figure out a solution, I also thought to ask here in case you might know of anything.
After nampower update 2.11.1, every new release has caused my game to crash to desktop any time I open a profession window with this addon enabled. If I disable the addon, this issue stops happening. Not sure if it's related but the nampower releases around 2.11 also seem to cause my game to freeze when I open a profession window for a split second, although it does not cause a crash.
I made a thread on the nampower dev's Gitea about it. If you'd like to look at it, it's from this post down. I attempted a lot of troubleshooting steps in it and posted nampower logs if that helps. The nampower dev is also using this addon and is unable to replicate this issue or figure out what the cause might be exactly. We tried changing some lines of code in one of the addon's lua files but that didn't seem to do anything. Appreciate if you could take a look and let me know if this is definitely an issue on nampower's side and nothing caused by this addon itself. Thank you!
I read the issue #4. Try disabling the calling of the function LoadAllProfessionsOnce() in the beginning of function ATSW_Show() inside the file AdvancedTradeSkillWindow2.lua. This function is useful only when the player have no WDB filled with the data of all professions, like icons for example. It makes the first show seamless, instant.
I also installed nampower and VanillaFixes that utilizes it. It worked fine for me with the function LoadAllProfessionsOnce().
I read the issue #4. Try disabling the calling of the function LoadAllProfessionsOnce() in the beginning of function ATSW_Show() inside the file AdvancedTradeSkillWindow2.lua. This function is useful only when the player have no WDB filled with the data of all professions, like icons for example. It makes the first show seamless, instant.
I also installed nampower and VanillaFixes that utilizes it. It worked fine for me with the function LoadAllProfessionsOnce().
Thank you! So with that disabled it's normal for the game to freeze the first time you open a profession window, but after that it is stored in the WDB cache and will load much quicker?
That seems to have mostly fixed it for most of my profession windows. however I'm still immediately crashing when I try to open the Survival profession window. Tried opening it from a button on my action bar and from the ATSW tab. You're also saying that it works fine for you with that function enabled, so I wonder just what about my specific setup is causing this issue.
Activity
Shellyoung commentedon Feb 1, 2026
I read the issue #4. Try disabling the calling of the function
LoadAllProfessionsOnce()in the beginning of functionATSW_Show()inside the fileAdvancedTradeSkillWindow2.lua. This function is useful only when the player have no WDB filled with the data of all professions, like icons for example. It makes the first show seamless, instant.I also installed nampower and VanillaFixes that utilizes it. It worked fine for me with the function
LoadAllProfessionsOnce().apav commentedon Feb 2, 2026
Thank you! So with that disabled it's normal for the game to freeze the first time you open a profession window, but after that it is stored in the WDB cache and will load much quicker?
That seems to have mostly fixed it for most of my profession windows. however I'm still immediately crashing when I try to open the Survival profession window. Tried opening it from a button on my action bar and from the ATSW tab. You're also saying that it works fine for you with that function enabled, so I wonder just what about my specific setup is causing this issue.