3.3 issues on 12.0.5

[mario-64]

Installed the update with all three folders in place. I'm seeing several issues with 3.3:

/ms or /movespeed shortcuts do not work
Right clicking the player speed display to show options does not work and, in fact, after right-clicking a couple of times produced the Blizzard "addon is causing problems" dialog. Had to force kill WoW.
The Options panel within Options -> Addons -> MovementSpeed -> Player Speed is empty. There is no way to change font, etc as before

[Arxareon]

I will investigate immediately.

Crucially, everything works for me. I will try to find out how I can preproduce what you are experiencing to figure out the root cause.

Results of a successful manual install:

---

Likely cause:

• Some folders might be jumbled in some way or they might not have the right name, or, some of them are within container folders so the addon folder is not directly within the Interface/Addons folder.

One error I could cause was with the NoFonts version of Widget Tools. Unfortunately, that does not work and I will be removing that release bundle. Right now, only the version with the extra font files works—but that does dowk. I will rectify that as soon as I can.

I could not fully recreate what you experience as of yet. Could some other addon cause issues in your case as well? I isolated the test to only the Movement Speed-relevant installs by renaming the entire Addons folder to "Addons_old" (but it can be anything) and created an empty Addons folder. Installed manually there, and launched WoW. This makes sure only Movement Speed and Widget Tools (with the Toolbox) are loaded so issues caused by other addons can be eliminated. To restore all addons after the test, simply remove the temporary Addons folder and rename "Addons_old" (or whatever it was renamed to) to Addons and relaunch WoW.

It's a good idea to make an extra copy of the Addons folder too, just to be extra safe of accidents. Creating backups occasionally is a good habit to develop. I keep forgetting it but backups have saved my arse a couple times..

I have uploaded a full install bundle to the latest 3.3 release to help with correct manual installation. Find here.

[mario-64]

Thank you. That's definitely not what I'm seeing. I did verify that the addon folders are not somehow nested within another folder. Also disabled all addons except these 3 and it still isn't working. Let me try your direct download.

[mario-64]

Tested with your full bundle release. All other addons disabled. Still doesn't work. It shouldn't matter for addons but I'm on the Mac client. I do have a Windows PC I can test with as well. I'll report back.

[Arxareon]

That is very interesting. I'm honestly puzzled. It of works on Windows, there are several things that could be the cause, even though that should not matter of Addons, yes. An unsupported Font file seems like an actual possibility.

I honestly did not foresee having to test not only for all versions of WoW but on Mac as well.

[mario-64]

Same issue on Windows. The shortcuts do not work and even player speed display is not shown. When I go into Options -> Addons -> MovementSpeed and expand it, I don't see Target Speed Display, Target or Data Management. And the Player Speed Display panel is empty

[Arxareon]

I believe I thought of what the real oversight was and why it works for me. It is the font but not the files, the absence of a file. I was planning to introduce better custom font management but it'd be a bit of work and I needed to get this milestone update out, so I pushed that feature back. However, I already did make one change that only reliably works once that feature is done:

• The old custom font support expected one specific CUSTOM.ttf font file to be present within the addon's directory. The new system will look for fonts right inside WoW's Fonts folder. I already made that change without finishing the entire custom font management system. The client is trying to find Fonts/CUSTOM.ttf but it can't. On my PC it exists, because I placed during development but failed to remember that it does not exist for everyone else.

Quick workarounds until I can drop the hotfix, either of them should do the trick:

• Dropping in any random TrueTypeFont file inside the main WoW Fonts folder, named exactly CUSTOM.ttf.
• Manually edit Core.lua inside the WidgetTools folder to remove one specific line here:

WidgetToolsDB = us.VerifyData(type(WidgetToolsDB) == "table" and WidgetToolsDB or {}, {
	lite = false,
	positioningAids = true,
	-- customFonts = { "CUSTOM", }, --REPLACE with custom font management
	debugging = false,
	frameAttributes = {
		enabled = false,
		width = 620,
	},
})

Line 535 needs to be removed or commented out like in the example code above.

[mario-64]

Confirmed. Commenting out line 535 fixed it. Thanks for the super fast resppnse!

[Arxareon]

Thank you for the report and the invaluable testing!

[mario-64]

Maybe I spoke too soon. Just went into a Delve, targeted a mob and began killing it. Got the Bliizard "addon is causing problems" dialog. Had to disable MovementSpeed. I don't have Target speed enabled but still am getting this in Delves. Haven't tried raid or dungeons yet.

[Arxareon]

Yes, indeed I can see that. This is an unrelated new issue that cropped up in 12.0.5, apparently Blizzard has actually gotten much stricter. I need to investigate it further.

[Arxareon]

Well, unfortunately, it is a very simple issue but with damning results. Even your own player's speed value is now a secret in combat. Movement Speed can gather that info but it cannot use it in any meaningful way while in combat in a private gamespace (like a Delve). It's quite frustrating because the speed value in yards/sec is there, but it is virtually unusable. I can print it to chat every frame but that's not very useful. There is possibly some whacky roundabout way Blizzard did not yet think of to hack the system and get the value out to be usable but for one, that's a game of what-a-mole and two, that complication just might not worth the trouble.

For now, I will have to disable Player Speed whenever the speed value is a protected secret.

Luckily for us, the Travel Speed estimation feature is completely unaffected (as of yet) and that can still be used in cases where Player Speed is unavailable but Map data is. I will likely have to do some work to meld these features together in the future to get the best of both worlds, perhaps, or find a safe way to use the secret value. Or, convince Blizzard that if I can estimate my speed in the very same private PvE zone no less, locking the speed value stat is completely pointless and counterproductive.

I will post the update with the safeguards in place as soon as I can.
Once gain, thanks a lot for the help!

Correction: Player Speed doesn't work anywhere, even outdoors while in combat, unfortunately.

[mario-64]

Gotta love this whole addon-apocalypse. So frustrating. Thanks for investigating. Funny I haven't noticed that error outdoors. Like while questing, etc. Weird. Maybe I had it disabled when I was questing.

[Arxareon]

Yes, that's the thing.. it is inconsistent. Sometimes it works and sometimes it just doesn't. It seems to be consistently broken in combat right now, so at least that seems to be improvement—in a way..
The current solution I'm testing only cares about whether the speed value is a secret at the time. So, if it woks in combat, it should still be able to use it. If it ever turns into a secret, it will not attempt to.

I would really love if Blizzard could just decide on what they want to kill and be done with it. This flip-flopping & arbitrary useless limitations are the frustrating part, even though I get what they are trying to achieve and I agree with the premise itself, just not exactly the way they are going at it. Again, I can calculate the speed with fairly good accuracy, that is what the Travel Speed feature does, but I can't cleanly get the current player unit speed and be able to do simple calculations with it. Hypothetically, if I ever wanted to abuse the player speed in combat somehow, I could just use this estimated travel speed value instead. I really am waiting for the day Blizzard breaks map size data and player coordinates even outdoors.. hopefully, they won't. It'd be silly to as that info is already disabled where it counts, PvP zones Raids & Dungeons, and has been forever. Player unit speed should be the same. IT should always work in Scenarios, Delves and especially outdoors. There is zero reason I can think of to secret-protect them..

Well anyhow, the update should be available soon. I will just have to do some quick testing in Classic to see if I haven't broken anything there.