Clicked

Clicked

294k Downloads

Cannot add new keybinds

boneyelbow opened this issue · 5 comments

commented

Describe the bug

After importing my Clicked profile string, I am unable to add other keybinds. When I attempt to generate a keybind, it is not populating anything in the status window. When I close the Clicked window, nothing is saved. The keybinds I imported all appear to work fine.

Clicked Version

1.16.11

World of Warcraft Flavor

Retail

Tried with only Clicked enabled

  • Yes
  • No

Lua Errors

No errors or bigs reported in game/bugsack etc

Reproduction Steps

  1. Start fresh with a new Clicked installation.
  2. Import a profile (I'll provide my string for reproduction)
  3. Once the profile is imported, attempt to create new keybinds. You'll notice the status window isn't updating as you create the keybind.

Last Working Version

No response

Screenshots

I can create a video if it'll help? Attached is my import string.

Elaho Clicked.txt

Debug Output

Version 1.16.11.txt

Dump attached

commented

Small update. I was able to add a keybind today by doing the following:

  1. Go to "New" > "Create Spell"
  2. Click "Action" and add the spell in "target spell", in my case Symbiotic Relationship
  3. Add a keybind at the top
  4. At this stage it got weird, ALL my keybinds appeared to be completely missing.
  5. /reloadui without adding anything under "targets" "load conditions" or "macro conditions"

Voila, spell added and I can now add conditions and all my other spells are present.

This was all done with Clicked being the only addon loaded.

commented

Me again. I wiped my Clicked lua files and started over without importing anything and Clicked is working normally. It's possible my variables became corrupted?

Anyway, just wanted to leave as much info as possible for you.

commented

Yeah it's likely there's something going on with your SavedVariables, so perfect that they're attached, hopefully I can find and fix whatever causes it :)

commented

Okay, it appears that I already fixed whatever was causing this, I can reproduce this on 1.16.11 but not on the new version I'm working on. I'll mark this as resolved, but I will look into it some more later as I'm very curious what's going on here

commented

Seems like it was fixed by @m33shoq in #252, thanks again :)