Issues with "Block War on" options
Classic Client option > Reputation System tab
Option reads "Block war on Friendly"
According to the colour options in the same tab "friendly" is defined as guild, however checking this option blocks war on innocent.
So should read "Block war on Innocent"
(this cost me 1million gold under bug bounty)
I tell you the truth, tis better to do 10 damage on the right target than 100 damage on the wrong target.
Breaking in the young since 2002
This discussion has been closed.
Comments
However if checking block war on friendly worked correctly, this would solve the issue with “target hostile”
Sorry I have nothing else to contribute to this thread.
"Merus: I come tonight about an issue we have visited in this forum about a few times
Merus: going back almost a year
Merus: it is the issue of the classic client targeting
Merus: the select nearest hostile is very broken
Merus: has there been any progress on this?
Mesanna: I have two things to comment on this
Mesanna: it might have been reported
Mesanna: but 80% of the time we just do not have the information to reproduce it
Mesanna: if we can not reproduce something we can't fix it"
Is this some kind of joke??
@misk, if you're having difficulty reproducing anything on this thread, please let us know. All you need to do is press the "select nearest hostile" macro key...
Please note, this issue affects EC too.
Can test target nearest there also. Select nearest target and you target something 8 squares away when there are 3 mobs 1 square away. This happens so often, how can someone not see it. And it could be linked to the Pet AI, since toon AI is prob the same.
Farmer: and friendlys and such
Farmer: could u add also summoned reds like
Farmer: rcs
Farmer: and vortexes
If you press attack nearest hostile and it flags on your own grey/red guild mate, all following area effect spells that either party casts will then affect each other and you will continue to reflag each other, so one player will have to sit out a fight until they're fully unflagged"
1- when in a war mode with "block war on pets" ON I accidently double click on my pet - I start attacking it. It is quite devastating wit Thrower and 2* Elemental slayer against Triton.
I am trying to avoid it by some macroing , anyway happens 1-2 times per day. Opening doors, looting corpses in heat of the battle, etc.
2- even in peace mode with ""block war on pets"ON you can discord your pet. fter this pet feels that something hostile was made and go to attack you. There are some training times when you need to discord pet (to train healing for example). But normally my tamer defenitely dont want to discord a pet.
All happens Iin EC with no mods or interfaces..
2, this is actually working as intended, the option only blocks war on pets (preventing you from accidentally attacking it with attack nearest etc or double clicking), if you use a target effect and specifically target a pet, this is not intended to be blocked"
but I’m not sure why they are offering it on the uo.com website even if it doesn’t work”
therefore it is already entirely possible for the classic client to distinguish between hostile and non hostile using factors other than Color”
Note "not select your own summoned red drone" is very different than "not select other red player summoned red drone". The client knows that your own followers are not hostiles, at least in some cases.
You should create a table representing various permutations for the observations here.
e.g. you can have a column representing behavior for the "your own", another column for "guilded player", another for "blue", another for "VVV", etc. Then have a row for each scenario "summoned EV", "pet", "animated undead", "targeted area effect spell", "blind area effect spell (e.g. EQ/thunderstorm", etc.
One problem with the various threads on these targeting topics is the broadsword team appears to be homing in on permutations that may not match up with what players are concerned with.
however I am confident that all targeting issues and solutions to these issues are detailed in this one thread.”
--
From the Meet & Greet on 10/17/2022:
NEWS - Developer Meet and Greet, October 17th, 2022 | Stratics Community Forums
"...
[Napoleon]: there is a bug in classic client
..."
[Kyronix]: So what you are reporting isn't a bug
--
You are not going to get a more direct answer from the team. This thread needs to be closed as a bug report.
@Mariah @Rorschach
(I personally agree with Yoshi and think both clients should have better filters, but that is a feature request. The current behavior is clearly not a bug and it's time to stop badgering the team about it.)