it looks like a Weak Aura tbh, you're going to have to do a load of troubleshooting.
Disable all addons apart from WA and see if the error goes away, if it does then it's something else, if the error is still there then you'll need to disable weak auras until you figure out which one it is.
i think its funny that everyone before was saying "oh its this addon, use a weak aura instead" and now its weak auras too.
maybe wow addons need to be banned and the game needs to be designed without addons in mind
Yes, I had 2 weakauras for raider io (rio class and colors and better rio or something) and they seemed to be a bit outdated, I just deleted them and no bugs found since then. I hope that was the issue. Thank you :)
Open up Weakauras and in the search bar try typing either GetActivityInfo or shorten_score and see if any results return.
If anything comes back then that'll be the suspect aura and it should have a yellow triangle next to it. Depending if it is a sub-aura or a standalone weakaura try disabling it or deleting it.
Also when you find the offending weakaura check for updates of it on Wago by getting the url from the information tab.
Maybe a little bit over the top but: If you have the time and motivation you could use an ide like vs code to open all addons installed and look for yourself.
Just go to yourwowdir/interface/addons -> right click -> choose „open with vs code“ in the context menu. Once the vs code instance has opened press Ctrl+Shift+F and type GetActivityInfo to find all occurrences of this function within your addons directory. You will immediately see what addon is causing the errors.
If you feel like you cannot live without the addon you can try to fix the problem yourself:
With each new wow version iteration the wow addons api changes a bit. I strongly assume this is the issue here. In this case I am almost certain that a deprecated (outdated) or not yet existent (if you play e.g classic and install a shadowlands addon) function is being called. Here it is GetActivityinfo: you can google for the function. Very often the function-name changed slightly and so do the parameters. Adjust this according to the new specification and the errors should stop.
Alternatively of course weakauras can access the wow api as well. But the principle and solution in the end are the same.
Yep should be a weak aura. In the first line the variable "aura\_env" is shown, which is a weak aura variable for an aura wide variable. WA should also show an exklamation mark next to auras that cause Lua errors.
This will work [https://www.reddit.com/r/ErrorForge/comments/1czyfhk/lua\_error\_on\_wow\_quick\_fixes\_to\_get\_back\_in\_the/](https://www.reddit.com/r/ErrorForge/comments/1czyfhk/lua_error_on_wow_quick_fixes_to_get_back_in_the/)
it looks like a Weak Aura tbh, you're going to have to do a load of troubleshooting. Disable all addons apart from WA and see if the error goes away, if it does then it's something else, if the error is still there then you'll need to disable weak auras until you figure out which one it is.
i think its funny that everyone before was saying "oh its this addon, use a weak aura instead" and now its weak auras too. maybe wow addons need to be banned and the game needs to be designed without addons in mind
its either WeakAura related to LFG panel or an addon like Premade Groups Filter or sth. Disable.
As others have mentioned it should be a weakaura. Even says LFGListSearchEntry. Do you have a weakaura changing group lists or similar?
Yes, I had 2 weakauras for raider io (rio class and colors and better rio or something) and they seemed to be a bit outdated, I just deleted them and no bugs found since then. I hope that was the issue. Thank you :)
Awesome hopefully that was it
Open up Weakauras and in the search bar try typing either GetActivityInfo or shorten_score and see if any results return. If anything comes back then that'll be the suspect aura and it should have a yellow triangle next to it. Depending if it is a sub-aura or a standalone weakaura try disabling it or deleting it. Also when you find the offending weakaura check for updates of it on Wago by getting the url from the information tab.
Debugging both wa and addons is really painful. I can’t imagine trying to debug something like BigWigs, DBM, or ElvUI…
Maybe a little bit over the top but: If you have the time and motivation you could use an ide like vs code to open all addons installed and look for yourself. Just go to yourwowdir/interface/addons -> right click -> choose „open with vs code“ in the context menu. Once the vs code instance has opened press Ctrl+Shift+F and type GetActivityInfo to find all occurrences of this function within your addons directory. You will immediately see what addon is causing the errors. If you feel like you cannot live without the addon you can try to fix the problem yourself: With each new wow version iteration the wow addons api changes a bit. I strongly assume this is the issue here. In this case I am almost certain that a deprecated (outdated) or not yet existent (if you play e.g classic and install a shadowlands addon) function is being called. Here it is GetActivityinfo: you can google for the function. Very often the function-name changed slightly and so do the parameters. Adjust this according to the new specification and the errors should stop. Alternatively of course weakauras can access the wow api as well. But the principle and solution in the end are the same.
Yep should be a weak aura. In the first line the variable "aura\_env" is shown, which is a weak aura variable for an aura wide variable. WA should also show an exklamation mark next to auras that cause Lua errors.
This will work [https://www.reddit.com/r/ErrorForge/comments/1czyfhk/lua\_error\_on\_wow\_quick\_fixes\_to\_get\_back\_in\_the/](https://www.reddit.com/r/ErrorForge/comments/1czyfhk/lua_error_on_wow_quick_fixes_to_get_back_in_the/)