Razor 1.5 - Bug/Issue/Release Tracking

1.5.0.5 is available here. Sorry for the bug guys, thanks for reporting it.

https://github.com/markdwags/razor/releases

Is there anyway you could add auto follow to a target? the hold alt to auto follow is VERY lame. its slow and some times you drag a life bar messing you all up!

UOAM was working with my old Razor (The one that comes with UOR client).
When using the new razor, it wasn't tracking any players.
After turning on Compatibility with Windows XP, it began tracking the players with no issues.

I imagine you could, it's probably just a packet you send from the client to the server. Interesting idea.

Yeah, sure is. I don't know why it doesn't with this one. It doesn't work this way "out of the box" -- in other words, the source code I'm working off of, before I even touched it, UOAM doesn't work. I've spent a decent amount of time looking into it, everything flows back identical to the old. You can find more info here -- https://github.com/markdwags/razor/issues/1

Wow, really? UOAM works for you running UOAM in Windows XP mode? What OS are you using?

My mistake, I was actually using another Razor version.
BUT, I was experiencing the 'non tracking' issue with the newest official razor version, and it WAS fixed after using UOAM with Windows XP Compatibility,
Windows 10 x64 Version 1803.
And from what I can see, UOAM doesn't even track the clean UOR client, with no razor working...
I'm going to continue testing this.
I'm pretty sure something is different at a TCP level.
When I have some time I'll do a wireshark trace and try to compare the packets, maybe we can see in what way packets are different that UOAM doesn't catch them...
Do you know, at high level, how does UOAM track the movement of players on the UO client? If it does that by sniffing packets, or injecting somehow into UO's client?
I work as an IT infrastructure engineer, and I have some advanced programming skills too, so hopefully I will be able to provide something useful to troubleshoot this.
Thanks!

If you check the link in my previous post, you'll see how it's done. In this case, Wireshark wouldn't help you since it's not using TCP or any type of injection, it's instead using Windows Messages.

Here are the codes sent from UOAM to Razor:

https://github.com/markdwags/razor/...80ebe6b75abaa/Razor/Network/ClientComm.cs#L65

Each message comes in and is passed here:

https://github.com/markdwags/razor/...0ebe6b75abaa/Razor/Network/ClientComm.cs#L152

I can observe the messages coming into my version of Razor, and sending a response, but that's where UOAM stops.

Again, the link above will have details on what is and what isn't happening. Hopefully UOAM not working will be a moot point when @JimmyTheHand is done with his magic and he upgrades the built in Razor map

I just notice "Target Closest Grey Monster" is not targeting dire wolves or hell hounds.

Looking at mobtypes.txt in the UO folder, wolves (and thus hell hounds and dire wolves) are considered animals, so that makes sense. I think a quick fix on your end that wouldn't require an update to be pushed out is to edit that mobtypes.txt file, go down to 225 and change ANIMAL to MONSTER.

I'll have to look if Razor can look at an animal mob and determine if it's actually a monster.

Ok thanks, I was with some other people and their version of razor was targeting them and mine wasn't so I wasn't sure what the deal was.

Interesting. So obviously Razor can tell the difference and not rely on that file. I'll have to look into it more.

Thanks for reporting it.

I did try this, but the hell hounds actually disappeared! I could hear it and it was hitting me but it was invisible.

Well, shit, that wasn't the right solution. My apologies. Let me come up with a solution. I can push out an update that will have these fix, along with the other stuff, minus the new map system.

Thanks, I switched it back and the hell hounds reappeared. Ha

you could request GM powers on test server. i know some players have that !!!!!

You can download 1.5.0.6 here:

https://s3.amazonaws.com/uorazor/Razor-1.5.0.6.zip

Release notes:

https://bitbucket.org/markdwags/razor/wiki/Release Notes

1.5.0.6

Wait For Gump & GumpResponse doesn't seem to be working.

I also noticed if you record a macro wait for gump isn't recorded either.

Ugh, my bad. I know why. Sorry all. I'll get it fixed.

Ok, if you re-download 1.5.0.6 it should now handle gumps again correctly.

My apologies again, I was exploring some gump stuff and didn't disable something. I mentioned this is still in beta, right?

Working much better thanks!

Are Kirins and Unicorns in the Grey Monster section?

I don't know if it wasn't working or my macro went nuts...