Describe the bug
There was a new WOTLK Classic update Sept 2 and it introduced the following bug on startup:

3x AdiBags\core\EventHandlers.lua:44: Attempt to register unknown event "CURSOR_UPDATE"
[string "=[C]"]: in function `RegisterEvent'
[string "@AdiBags\core\EventHandlers.lua"]:44: in function `OnUsed'
[string "@Scrap\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua"]:76: in function <...rap\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:59>
[string "=(tail call)"]: ?

Locals:
(*temporary) = <unnamed> {
 0 = <userdata>
}
(*temporary) = "CURSOR_UPDATE"

To Reproduce
Steps to reproduce the behavior:

1. Log into the world with Adibags enabled

World of Warcraft Release and Version (Retail 9.2.7, etc)

• Wotlk Classic

AdiBags Version

• v1.9.35

Have you tried disabling all your other addons to ensure only this addon causes the issue?

• Yes

Yeah, it seems like that's the case. Oh well.

Push fixed in 1.9.37 -- should show up on curse within the hour, or directly from this repo in a few seconds under Releases.

Yeah it looks like they added the WOW_PROJECT_WRATH_CLASSIC project ID. Was that just added today but missed with the prepatch?

TY for the fast response. I figured it out pretty quick. Lots of other addons breaking probably due to this today.