Last Object Type for Stealing Wrong
Forum rules
Posts in this forum are expected to be constructive, realistic and civil. Inflamatory or off topic posts will be removed.
Posts in this forum are expected to be constructive, realistic and civil. Inflamatory or off topic posts will be removed.
Re: Last Object Type for Stealing Wrong
how else can you connect to UOSA without using Razor?
Re: Last Object Type for Stealing Wrong
UOE shouldn't be a reason why things are kept in Razor or not, with features like bank anywhere and seeing hidden people, it wasn't so much a helper program but a cheating program.Faust wrote:If this idea is ever forced some of those features should not be removed...
Light Levels
Spell Format
Auto-unequip hands before casting
Scavenger
Were all features of UOE or UOP making them accurate to the era.
Light levels shouldn't be allowed in Razor, it negates the entire function of Nightsight or nightsight potions. Spell format is redundant on the older folks, and creates ignorance in the newer ones by not forcing them to learn the game world. Auto-unequip hands before casting makes fighting that little bit less skillful. And Scavenger... something that enables someone to machinegun loot everything off a corpse in before anybody else can even open it should not be allowed.
If a function in Razor totally bypasses an inherit game mechanic, it shouldn't be allowed, many of which the above do.
Re: Last Object Type for Stealing Wrong
This isn't a matter of "how things should be" scythe, but instead a matter of accuracy. The majority of the exploits with UOE were fixed in late '98. This included the bank anywhere exploit that you mentioned. The program itself through out '99 was no different than UOA with some slight differences. The scavenger feature in UOE wasn't very good at all from what I recall. I will have to look it over again to verify the extent of the feature. However, these features existed in the era that we are recplicating, and thus should not be excluded based on bias or opinions.
Re: Last Object Type for Stealing Wrong
ConnectUO app still works, you can also use UO_Rice to patch out the encryption on the client, and modify your login.cfg file to connect to UOSA.Prurk wrote:how else can you connect to UOSA without using Razor?
Re: Last Object Type for Stealing Wrong
I'm not sure why keep referencing UOE and UOP which were bannable in T2A. They were considered hacks, cheats, exploits, whatever. Because an exploit is "era accurate" should we include it on UOSA? If so, I have a list of "era accurate" dupes I'd like implemented.Faust wrote:If this idea is ever forced some of those features should not be removed...
Light Levels
Spell Format
Auto-unequip hands before casting
Scavenger
Were all features of UOE or UOP making them accurate to the era.
Re: Last Object Type for Stealing Wrong
Scythe wrote:I doubt anyone connects to UOSA without Razor. I mean, the instructions to connect are with Razor, and I can't foresee anybody using anything other than Razor to connect with servers now that UOGateway is gone.
There are some features which should be disabled
Light Levels
Spell Format
Show Health above people/creatues
Auto-open doors
Auto-unequip hands before casting
Auto Un/Re-equip hands for potions
Force game size
Binding Macros to keys (Prevents macroed maneuvers in fighting, but allows macroing characters)
Scavenger
And the aforementioned Last Target - by type
the majority of this list was possible with uo assist.
Re: Last Object Type for Stealing Wrong
You people must be remembering an entire different program, because UO Assist didn't have nearly the amount of features that Razor has now. The only reason people got UO Assist/UOE when they were bannable for using was because Last Target and Arm/Unarm wasn't available in the client yet. When UOA was approved, I can guarantee Light Levels and auto-unequip on cast were not features in the program anymore.
Re: Last Object Type for Stealing Wrong
UOE had a feature that would let you make items "disappear" on your screen.
Even if you did bury a pouch underneath a blessed or newbied item, there was a way to steal it.
Another note on stealing, when you snooped someone their backpack stayed on your screen even if they moved out of range, or you moved. They currently disappear when the victim moves too far away.
Even if you did bury a pouch underneath a blessed or newbied item, there was a way to steal it.
Another note on stealing, when you snooped someone their backpack stayed on your screen even if they moved out of range, or you moved. They currently disappear when the victim moves too far away.

Re: Last Object Type for Stealing Wrong
UOE features aren't really something we'd want on this shard is it?Eulogy wrote:UOE had a feature that would let you make items "disappear" on your screen.
Yeah, but you had to find the object to target it unless you did a random steal. That was your only legal options.Eulogy wrote:Even if you did bury a pouch underneath a blessed or newbied item, there was a way to steal it.
To find and target an object hidden the way I described you had to drag and drop the shield and quickly dbl click the pouch. Clearly something that required lag and some skill...and if you walked away, despite what you are saying below, without a UOE the pack would close and you were back to square one.
Hmmm... I don't remember a pack staying up if a target moved away too far on OSI. At least not while using the client and UOA.Eulogy wrote:Another note on stealing, when you snooped someone their backpack stayed on your screen even if they moved out of range, or you moved. They currently disappear when the victim moves too far away

Re: Last Object Type for Stealing Wrong
Perhaps that was a UOE feature as well, I can't remember.
I'm not arguing for this feature, just sayin..
I'm not arguing for this feature, just sayin..

Re: Last Object Type for Stealing Wrong
The problem with disabling Razor features is that it will encourage people to use other third party programs, which are illegal.

[00:43] <Hemperor> i like turtles
Re: Last Object Type for Stealing Wrong
I don't see the problem with these features if everyone has the same access to them.
Legal unattended macroing is not era accurate either
Legal unattended macroing is not era accurate either

Re: Last Object Type for Stealing Wrong
Kraaug,
No one is arguing for the implementation of every UOE feature. I am saying that the features Razor use should not be removed that existed on other 3rd party applications like UOE, UOP, and UOA. etc... It is actually impossible to implement features that those 3rd party applications had that doesn't exist on Razor without the source code. This is something that the RunUO team will unlikely ever distribute to the public though. I honestly don't ever see anything like that happening, which makes it literally impossible pretty much to do this in the first place.
The containers not closing when someone walks away was in fact a UOE feature.
Both of those features were fixed before the demise of UOE in early '00 though.
No one is arguing for the implementation of every UOE feature. I am saying that the features Razor use should not be removed that existed on other 3rd party applications like UOE, UOP, and UOA. etc... It is actually impossible to implement features that those 3rd party applications had that doesn't exist on Razor without the source code. This is something that the RunUO team will unlikely ever distribute to the public though. I honestly don't ever see anything like that happening, which makes it literally impossible pretty much to do this in the first place.
The containers not closing when someone walks away was in fact a UOE feature.
Both of those features were fixed before the demise of UOE in early '00 though.
Re: Last Object Type for Stealing Wrong
I know what you are saying Faust and I agree with you to a point.Faust wrote:Kraaug,
No one is arguing for the implementation of every UOE feature. I am saying that the features Razor use should not be removed that existed on other 3rd party applications like UOE, UOP, and UOA. etc... It is actually impossible to implement features that those 3rd party applications had that doesn't exist on Razor without the source code. This is something that the RunUO team will unlikely ever distribute to the public though. I honestly don't ever see anything like that happening, which makes it literally impossible pretty much to do this in the first place.
The containers not closing when someone walks away was in fact a UOE feature.
Both of those features were fixed before the demise of UOE in early '00 though.
What I am trying to point out is a severe imbalance caused by the ability to steal an object by object type. It creates a situation where stealing bandages, or reagents, or runes is not in keeping with Era accuracy.
It overpowers the stealing skill for combat and should be looked into.

Re: Last Object Type for Stealing Wrong
I had no idea you could do this... thanks for the idea!