OPie: Issues
Known issues
[Classic] OPie may not appear in the AddOns list or function correctly after manually installing an update.
If OPie does not appear in the AddOns list after installing an update, restart the World of Warcraft classic client. If OPie appears in the AddOns list but does not function correctly, delete the existing Interface\
Fixed recently
Some /commands used in OPie macros may result in an "action blocked" error.
This is due to an error in OPie, and should be resolved in Ørred 2a. Affected commands include /logout, /quit, /petdismiss, /petautocaston, /yield, and guild management /commands, as well as alternate variants of these commands.
[Patch 11.0.2] Opening an OPie ring or hovering over a nested OPie ring may cause the client to become unresponsive, or exit with a memory protection fault.
This is caused by an error in the Patch 11.0.2 client. A mitigation is included in OPie Ælling 3 (and later versions); if you are using a third-party appearance for OPie and the issue persists, you may need to switch to the default OPie appearance in /opie options.
Reducing the number of visible slices in the ring may reduce the chances of this condition occurring. While the WoW client is non-responsive, it may help to close the OPie ring, e.g. by right clicking or pressing Escape.
Report an issue
First, please check that you are using the latest version of the addon available from this site – some issues may have already been fixed.
If the issue persists when using the latest version, please make sure you have Lua errors enabled in the game client. You can turn on the built-in error display by typing /console scriptErrors 1 and then /console reloadui in chat. Some specialized error-capturing addons may offer similar functionality.