This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
I'm getting this error in 12.0.0 with the latest RangeDisplay.
1x RangeDisplay/RangeDisplay.lua:233: attempt to perform boolean test on a secret value[RangeDisplay/RangeDisplay.lua]:233: in function 'checkTarget'[RangeDisplay/RangeDisplay.lua]:253: in function 'targetChanged'[RangeDisplay/RangeDisplay.lua]:799: in function <RangeDisplay/RangeDisplay.lua:798>[C]: ?[AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua]:19: in function <...ons/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>[AdvancedInterfaceOptions/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua]:54: in function 'Fire'[BlizzMove/Libs/AceEvent-3.0-4/AceEvent-3.0.lua]:120: in function <BlizzMove/Libs/AceEvent-3.0/AceEvent-3.0.lua:119>[C]: in function 'CameraOrSelectOrMoveStop'[CAMERAORSELECTORMOVE]:4: in function <[string "CAMERAORSELECTORMOVE"]:1>
UPDATE:
Addon updated - v6.3.0 - contains this fix
Just download or update it via your addon manager of choice :)
Thanks to the author for the quick reaction.
_____________
FAN FIX (unofficial, use at your own risk):
- Just resolved it. So far no further errors on prepatch for me. Tested in dungeons too.
- Additionally, I've submitted a pull request on github for the author to review, test and if he's confident in the fix to push it officially. Here's a link to it: https://github.com/mitchnull/RangeDisplay/pull/9
If you wanna try my custom fix, follow these steps:
1. Find and open the file `RangeDisplay.lua` inside the RangeDisplay addon folder. (You can use any text editor, I use vscode or notepad++ for these things)
2. On line 231 - Find the function `local function = checkTarget(ud)`
3. Replace the whole function with this code: https://pastebin.com/3nKf7FJt#3Df72Zqx
4. Lastly, open the `RangeDisplay.toc` file and make sure 120000,120001 versions are listed on the #Interface line
That's it. This is an UNOFFICIAL fix that I made, because I wanted to stop getting errors and still have the addon work for me.
You are using this at your own risk if you choose to give it a try, like with all fan fixes. :)
Hope the Author confirms everything's good and publishes an official update, either with mine or any other fix that prevents errors and restores functionality to the addon.
Have a good one! o/
To post a comment, please login or register a new account.