Tried everything from reloading my ui, logging on and off, toggling my num lock (walk/run), and unbinding my macros for it, but for some reason my character keeps walking or running to the side, which is very cumbersome, especially in a combat when I want to go one way, but my character moves the other direction.
Not sure what is causing it. Any feedback would be wonderful: thank you in advance 
Have you moved the strafe keybind to another key and see if it stops? Your key on the keyboard could be sticking.
That’s just it, outside of the arrow buttons for direction, I really don’t use my keyboard. I have a gaming mouse with macros (razer naga) I primarily use.
I noticed the problem started earlier when I toggled my number lock button on- that seems to have triggered the issue if that helps any?
I checked my bindings and apparently num lock is my auto run button
When you reloaded your UI, did you do a /reload or a full UI reset?
I’d try a full reset (if you didn’t) and see if that helps. It’s reversible afterwards if it doesn’t help, just rename or move the original folders back into place.
Both- at first I did just a reload, but after that didn’t work, I just finished doing a full UI reset:
No luck 
I wish I could take a video of my character as that might help (I’m terrible at explaining things) but I just swapped to my fury warrior to look over the ui and it looks as if it’s running and walking at an angle? Hard to describe…
But it’s making me think it’s something with the keyboard or mouse if the resetting and reloading the UI didn’t work
I don’t think this is the same issue but I’m mentioning it in case someone behind the scenes sees this and suspects it is related and therefore relevant:
Currently in Necrotic Wake, taking the angel up to Surgeon Stitchflesh will cause a very similar bug. /Reload or relogging does fix it in this circumstance, but if you don’t do either, the issue will persist on that session.
I’ve done NW literally hundreds and hundreds of times between SL and last season and only seen this issue now that I’ve gone back to running it during the Bounty event, so something somewhere recently changed to cause the issue.