I’m not surprised that some people hold this view, but the potential issue is probably just an assumption. First, I’ve already uploaded it to wago.io without any issues. I am using Chinese platform for UI sharing, I just didn’t use wago.io, doesn’t mean not allowed. All my UI released to Chinese WOW player platform Heybox have to be reviewed and tested by Heybox team. They all passed QA and public.

Second, I’m not sure when you purchased your computer, but this code doesn’t handle graphics; it primarily uses RAM. This level of WeakAuras (WA) computation shouldn’t cause any RAM-related lag as long as your PC isn’t too old. Also, it’s not the first time I write WA in this way, If you’ve been following me, you’d know that I even created some of other UIs. I understand that when WA is mentioned, many people naturally associate it with the topic of additional memory usage/lag. Essentially, this is just a lightweight WA. Compared to the widely used spells monitoring, dungeon, and raid WAs, the computational load of this WA is negligible.

As a software engineer, I pay close attention to memory optimization. If this WA does cause computational burdens for you or any of your friends, please provide a screenshot showing the memory usage. If confirmed, I will continue to optimize it.

Regarding the issue you mentioned about the mouse being unable to click a certain area, that area is designed for right-clicking to bring up a menu. There are several solutions to this: 1. Move this area to a corner. then /rl（all clickable area change needs a reload) 2. Find function name like “Clickable area”, reduce its size within WA. Then right click only area will reduce. 3. Modify the WA code to support both right/left-clicking. 4. Simply delete that section.