Closed lvangh closed 2 years ago
I suspect some of these issues are with the outdated libraries from 7.x/8.x. Another example error just on a simple target script:
Sorry I just now seen this issue, but if you still have it could you give me your "Script for SP" so I can see the exact function it's calling to generate that error.
I suspect it may be an issue with the event names, however in TBC client this may be fixed by virtue of being the modern client.
I've been trying to take advantage of the scripting events but basically they stop working after the first Lua error. I've been trying to diagnose some of the issues but I'm a Lua beginner at best. Here's an error from one of the equip on target scripts with all addons disabled except Outfitter. I understand this was a quick fix to get it working in Classic and I 100% prefer this over Itemrack. If this is a side project, then that's cool and I'll assume there won't be any major support or re-work for 1.13. Just curious.
My first thought is that it wasn't passing local variables in each script because it kept saying nil value, but I kept disabled all scripts 1 by 1 until I had a simple
UnitName
equip and it still gave an error on the next mouseover in combat. So then I checked "disable in combat" on all of them as well. Still random Lua errors.`
Here is another script that causes a Lua error and stops scripting - have to /reload. (I know you can use tables to list each mob but I'm not focused on efficiency right now.)
I had some early testing/ experimental ones like this which counted the number of mages in a raid and changed for more/less crit (I know this is grasping for assumptions in spec but it was mainly about experimenting)
-- $EVENTS PLAYER_TARGET_CHANGED
-- Equip if it's the specified target