Sorry am a big fan of razor. But can you honestly say razor and by razor I am refering to a clean unbroken version, be as automated as uosteam? I remember when razor came out we could hold 1 button down to heal or ma fb the shit out of it but they fixed that.
Let's be honest. There's two major reasons Razor is weak in comparison to Steam, and it's not because Steam was coded to be a cheat-like application.
- Legacy code. It's a 10yo piece of software. It has a lot of memory hogs in it (which can be compensated by having low ping)
- It wasn't being updated for a long time, with only client compatibility being added.
I can do the same stuff I do with Steam on Razor. The main difference lies on my lack of client lag that comes from using Steam. If I pinged low, I have simple Razor macros that can outcast Steam and recast instantly if I get disrupted (and here is the "problem" with RunUO AOS casting. Some people like it this way, some don't). Steam can't do that.
The thing with uosteam is when it was created dgassist was used on shards by a certain group of people to have the upper hand once a few got banned chun and Diego came to ryan and changed the name to uoassist and sold it.
I may be mistaken, but only three people had DGAssist. How is it that people got banned for it, then?
Now, for the RunUO part... Ryan saw potential in DGA and figured Razor would eventually die because of the lack of updates. Luckily for those who like Razor, it didn't.
You cant say the program was created in mind to play fair.
It was created to counter EUO and Razor target-glitch macros which only a handful of people had and used (china, for example). So yes, fair play was the goal of it.
2 options really.
1 ban uosteam and say runuo server are perfect and deal with a massive razor loops and target loops.
2 keep both razor and uosteam and someone codes a server fix.
I say we should do option 2.
I agree that combat should be fixed, but only if it gets fixed all at once in a big update. Otherwise, as Id-remains puts it, we will be just passing the stick to the next bug-based template.