+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: Script Submissions (/Forum-Script-Submissions)
+--- Thread: Negotiate Features - AssistUO/Razor (/Thread-Negotiate-Features-AssistUO-Razor)
RE: Negotiate Features - AssistUO/Razor - Alaric - 09-25-2013 02:53 AM
(09-25-2013 02:48 AM)Extreme Wrote: Well, you can't control AUO and Razor with this system.EUO can't filter light/weather/sounds/etc as far as i know... but there are another external applications that can.
It will force the players use AUO or Razor.
We can't know if someone is using or not AUO/Razor :/
One question, why do you want to block them?
They will use EasyUO anyway...
RE: Negotiate Features - AssistUO/Razor - Extreme - 09-25-2013 02:57 AM
(09-25-2013 02:53 AM)Alaric Wrote:Well, if he want to block the filters, just use this script and block everything.(09-25-2013 02:48 AM)Extreme Wrote: Well, you can't control AUO and Razor with this system.EUO can't filter light/weather/sounds/etc as far as i know... but there are another external applications that can.
It will force the players use AUO or Razor.
We can't know if someone is using or not AUO/Razor :/
One question, why do you want to block them?
They will use EasyUO anyway...
He will get sure everyone is using AUO/Razor and they can't use the filters...
RE: Negotiate Features - AssistUO/Razor - pinku - 09-25-2013 03:03 AM
Yeah, I didn't want to force them using AUO or Razor, but if they used, the Negotiate Features had to be on.
If there is no way, then let it be..
Yeah, screw EasyUO. >.>
RE: Negotiate Features - AssistUO/Razor - Rizz - 09-25-2013 08:40 AM
Problem found, was anything related to that script.
I have a new question: is possible to block the feature that allow to auto-target a certain graphic on the ground? (i.e. block the macro that allow to auto-carve a body of a player on the ground)
RE: Negotiate Features - AssistUO/Razor - Extreme - 09-25-2013 09:35 AM
(09-25-2013 08:40 AM)Rizz Wrote: Problem found, was anything related to that script.I'm sure that you can't do this.
I have a new question: is possible to block the feature that allow to auto-target a certain graphic on the ground? (i.e. block the macro that allow to auto-carve a body of a player on the ground)
Do you want to block auto-carving?
Make one script to put a timer on body to block carving or something like that..
RE: Negotiate Features - AssistUO/Razor - Rizz - 09-27-2013 04:33 AM
(09-25-2013 09:35 AM)Extreme Wrote:(09-25-2013 08:40 AM)Rizz Wrote: Problem found, was anything related to that script.I'm sure that you can't do this.
I have a new question: is possible to block the feature that allow to auto-target a certain graphic on the ground? (i.e. block the macro that allow to auto-carve a body of a player on the ground)
Do you want to block auto-carving?
Make one script to put a timer on body to block carving or something like that..
Ok, i just hoped that was possible
It's funny that the only way to block some unwanted macroes or features is to use old client like 1.26.4b
RE: Negotiate Features - AssistUO/Razor - Rizz - 10-17-2013 08:16 AM
I would like to ask this:
we have
PHP Code:
FEATURE.15 0,RandomTargets //= 1 << 14, // Random targeting hotkeys and commands
FEATURE.16 0,ClosestTargets //= 1 << 15, // Closest targeting hotkeys and commands
but what about nearest target?
RE: Negotiate Features - AssistUO/Razor - Extreme - 10-17-2013 08:40 AM
No idea...
the features are written on assistants so they tell what can be enabled/disabled.
Maybe closest targets blocks the nearest targets too.
RE: Negotiate Features - AssistUO/Razor - Lazarus - 05-12-2014 04:58 PM
This should be in the add-on folder on default script pack!
RE: Negotiate Features - AssistUO/Razor - Feeh - 05-12-2014 11:06 PM
(10-17-2013 08:40 AM)Extreme Wrote: the features are written on assistants so they tell what can be enabled/disabled.
In addition to what Extreme said, these tools are almost dead, UOSteam stopped the development and Razor is being updated only with minor changes
(05-12-2014 04:58 PM)Lazarus Wrote: This should be in the add-on folder on default script pack!
I agree with you it should, but it uses a protocol that interfere with newer client protocol (that's why it isn't an option in the INI), we (at least me) can't officially release something that conflicts with our main code.
Again, this come back to UOS and Razor problem