Hitting “t” to start attack, which it’s done since vanilla and why I’ve never changed the keybind, is now giving me an error:
Message: [string “STARTATTACK”]:1: Usage: StartAttack(name [, exactMatch])
Time: Sat Mar 23 14:35:49 2024
Count: 3
Stack: [string “STARTATTACK”]:1: Usage: StartAttack(name [, exactMatch])
[string “=[C]”]: ?
[string “=[C]”]: in function `StartAttack’
[string “STARTATTACK”]:1: in function <[string “STARTATTACK”]:1>
Locals: (*temporary) = defined =[C]:-1
Any ideas?
I’m experiencing the same error, although I have rebound that to the tilde key. Were you ever able to solve this?
I’m having the same problem
I started having this error after the April 4th update. This error comes up no matter what I key I bind to it.
No 
No known solution so far, and quite annoying considering this is a default Blizzard setting, not like a custom addon option or anything.
Adding to this to hopefully help visibility. What ever your keybind regardless of if it’s default or not is causing a LUA error when pressed.
Still happening in WoW Classic Season of Discovery.
Blizzard support blatantly ignored the ticket I submitted, despite the fact that I provided the detailed error log.
This is a blatantly broken feature of a game client that costs $15/month to use. Why is there no technical or developer support to resolve this?
This is a critical feature that allows for comfortable and efficient play, especially for players who alt-tab between targets and need to be able to reliably ensure auto-attack doesn’t get turned off.
Error: ERROR #141 (0x8512008d) Script assertion failure!
Description: Script exception: [string “STARTATTACK”]:1: Usage: StartAttack(name [, exactMatch])
Locals:
File: D:\BuildServer\C\work-git\wow\WoW\Source\UIUtil\ExceptionScript.cpp
Line: 78
ProcessID: 13636
ThreadID: 5764
Any update on this?
Still broken. Basically impossible to play a hunter smoothly.
And for melee classes, having to switch the keybinding to Attack Target instead, which is a toggle, so I keep accidentally turning attack off in the middle of a busy fight.
Support tickets literally get ignored. I don’t understand how Blizzard can take $15 a month and have no avenue for getting this fixed.
Having same issue on all my toons. Very annoying.
From BugSack:
18x [string “STARTATTACK”]:1: Usage: StartAttack(name [, exactMatch])
[string “=[C]”]: in function `StartAttack’
[string “STARTATTACK”]:1: in function <[string “STARTATTACK”]:1>Locals:
Could an addon be causing the issue? I use startattack macros and T key without issues on my rogue.
Nope. I completely uninstalled WoW Classic, all of Battle.net, and all AppData files related to them, then reinstalled, and no addons – still broken.
It may work in other versions, but WoW Classic SoD has been like this for months now.
According to the full error log this issue produces, it’s an exception in the code.
having the same issue in classic era
Message: [string “STARTATTACK”]:1: Usage: StartAttack(name [, exactMatch])
Time: Wed May 1 10:30:24 2024
Count: 5
Stack: [string “STARTATTACK”]:1: Usage: StartAttack(name [, exactMatch])
[string “=[C]”]: in function `StartAttack’
[string “STARTATTACK”]:1: in function <[string “STARTATTACK”]:1>
It’s harder to play like this because I’m disabled
So it’s happening in Cataclysm Classic as well.
Unlike in SoD, in Cataclysm, every hit of the Start Attack key produces an error: “There is nothing to attack.”
WoW Classic is blatantly broken in both forms, and support tickets just get shut down.
Honestly it seems like the function is broken all together. /startattack slash command and the keybind don’t function like they’re supposed to, or how they used to.
So it seems to me that Start Attack is completely broken and the /startattack is actually just using the attack target function instead.