Roaming Bosses don't have the right to Reset!

[Freebird]

They are roaming, not bound to a location. So why do they always reset, when I try to kite them just a bit. That is not correct. Tristan is a prime example.

It is so annoying when you try to find them, find a good location and daytime to fight them, and then they just reset all the time when you move a bit in the fight.

[Luisian320]

Would you rather have them chase you over the entire map because they don't reset?

[biosmonkey]

I think the problem here is that for patrolling bosses, it seems the internal pathing keeps running even when you are fighting them. This means that if you keep the boss in the same place, their invisible "towline" will get too far ahead ... so they will stop fighting, reset and run to catch back up to where they are supposed to be.

I had this happen several times. This is bad design. Sorry but it is. Pathing should pause while boss is engaged in combat.

[Freebird]

Luisian320: You seem to have no clue what I'm talking about.

biosmonkey: You on the other hand seem to be spot on. I think that is the problem.

The pathfinding of those roaming bosses should be altered when you attack them and deal a certain amount of damage to them.

[[CULT] Siren]

They reset to prevent you from simply kiting them to death and the boss never touching you.

its a fair mechanic

[[CULT] Siren]

Originally posted by biosmonkey:

I think the problem here is that for patrolling bosses, it seems the internal pathing keeps running even when you are fighting them. This means that if you keep the boss in the same place, their invisible "towline" will get too far ahead ... so they will stop fighting, reset and run to catch back up to where they are supposed to be.

I had this happen several times. This is bad design. Sorry but it is. Pathing should pause while boss is engaged in combat.

Its designed to prevent you from abusing ranged mechanics and simply kiting the boss around the entire map while you cast spells at them. this is intended and totally fair.

[EthanT]

Originally posted by CC Siren:

Originally posted by biosmonkey:

I think the problem here is that for patrolling bosses, it seems the internal pathing keeps running even when you are fighting them. This means that if you keep the boss in the same place, their invisible "towline" will get too far ahead ... so they will stop fighting, reset and run to catch back up to where they are supposed to be.

I had this happen several times. This is bad design. Sorry but it is. Pathing should pause while boss is engaged in combat.

Its designed to prevent you from abusing ranged mechanics and simply kiting the boss around the entire map while you cast spells at them. this is intended and totally fair.

This isnt what theyre saying, I suggest you brush up on comprehension. If you engage Tristan at X location, and never leave X location, he can still reset because his pathing will continue even after the fight has started. Eventually X becomes too far away from where hes "supposed" to be according to his pathing, so he just resets and runs away, even though you havent moved or kited him away from where you engaged him. Jade does the same thing.

[Rhapsody]

Originally posted by CC Siren:

Originally posted by biosmonkey:

I think the problem here is that for patrolling bosses, it seems the internal pathing keeps running even when you are fighting them. This means that if you keep the boss in the same place, their invisible "towline" will get too far ahead ... so they will stop fighting, reset and run to catch back up to where they are supposed to be.

I had this happen several times. This is bad design. Sorry but it is. Pathing should pause while boss is engaged in combat.

Its designed to prevent you from abusing ranged mechanics and simply kiting the boss around the entire map while you cast spells at them. this is intended and totally fair.

+ pulling them to other powerful and unfriendly enemies, although that can still be done if you're lucky or planned for such occasion.

[Rhapsody]

Originally posted by Toxic:

Originally posted by CC Siren:

Its designed to prevent you from abusing ranged mechanics and simply kiting the boss around the entire map while you cast spells at them. this is intended and totally fair.

This isnt what theyre saying, I suggest you brush up on comprehension. If you engage Tristan at X location, and never leave X location, he can still reset because his pathing will continue even after the fight has started. Eventually X becomes too far away from where hes "supposed" to be according to his pathing, so he just resets and runs away, even though you havent moved or kited him away from where you engaged him. Jade does the same thing.

Accidental reset won't happen that easily though. The first (and only) time I solo'd Tristan I was like level 40, and pulled him into stone golem, literally circling around a large rock which blocked line of sight, luring him way off the beaten path, and whittled down his health by abusing the golem.

The tailor boss can also flee quite far away from the village she roams. But maybe some other bosses (Meredith?) are more prone to resetting. Never had such serious issues myself though.

[[CULT] Siren]

Originally posted by Toxic:

Originally posted by CC Siren:

Its designed to prevent you from abusing ranged mechanics and simply kiting the boss around the entire map while you cast spells at them. this is intended and totally fair.

This isnt what theyre saying, I suggest you brush up on comprehension. If you engage Tristan at X location, and never leave X location, he can still reset because his pathing will continue even after the fight has started. Eventually X becomes too far away from where hes "supposed" to be according to his pathing, so he just resets and runs away, even though you havent moved or kited him away from where you engaged him. Jade does the same thing.

my statement was correctly completely. what ever issues your having is you lot pushing your bosses to far away from there engagement location. and i abuse roaming bosses on many occasions.

[Senki]

Originally posted by CC Siren:

Originally posted by biosmonkey:

I think the problem here is that for patrolling bosses, it seems the internal pathing keeps running even when you are fighting them. This means that if you keep the boss in the same place, their invisible "towline" will get too far ahead ... so they will stop fighting, reset and run to catch back up to where they are supposed to be.

I had this happen several times. This is bad design. Sorry but it is. Pathing should pause while boss is engaged in combat.

Its designed to prevent you from abusing ranged mechanics and simply kiting the boss around the entire map while you cast spells at them. this is intended and totally fair.

you can already abuse ranged mechanics and simply kite bosses as long as you have a crossbow already.

Whatever they intended isn't working at fixing what they consider a problem and it only creates more.

[EthanT]

Originally posted by CC Siren:

Originally posted by Toxic:

This isnt what theyre saying, I suggest you brush up on comprehension. If you engage Tristan at X location, and never leave X location, he can still reset because his pathing will continue even after the fight has started. Eventually X becomes too far away from where hes "supposed" to be according to his pathing, so he just resets and runs away, even though you havent moved or kited him away from where you engaged him. Jade does the same thing.

my statement was correctly completely. what ever issues your having is you lot pushing your bosses to far away from there engagement location. and i abuse roaming bosses on many occasions.

Ive already beaten every boss multiple times. This is incredibly easy to test for yourself if youre so confident. Engage Tristan anywhere, and dont leave that tiny area you engaged him in. He will eventually reset EVEN IF YOUVE NEVER MOVED HIM FROM WHERE YOU ENGAGED HIM.

This is what it being discussed, again, learn to comprehend what you read before you spout your nonsense.

The pathing on roaming bosses continues to track even if theyre engaged. Eventually, EVEN IF YOU HAVENT MOVED, they will reset to catch up to their pathing.

This is very simple logic to follow, please grow something between your ears.

[Tanyon]

I think your theories are rubbish.. this is not a joke.. my friends and I fought Tristan for 2 entire nights and a day cycle.. like 15-20 minutes straight and he NEVER reset once.. I think you have to understand you can pull them off the road.. to a NEARBY place and fight them just stop acting like a chump and running too far away. there is no way you are staying within the allotted area and just fighting them. You have to be pulling them too far away.. I've never had a boss "magically" reset that patrols.. not Lidia, alpha wolf, Tristan, Jade, Vincent, Meredith, ZERO.. you are simply moving too far away..

[Freebird]

Toxic and biosmonkey: You understood what I was talking about. Thank you.

All the others: You did not.

[Tanyon]

I understand what you are talking about but I reject it. in the 230 hours I have in this game I have NEVER seen it.. maybe you are taking too long to kill them??? Like I said I've fought Tristan for like 20 minutes and he never reset and ran away.. I've killed all bosses multiple times.. none have ran away UNLESS I pulled them too far from the original spot in which I engaged them in which case I understand and respect.

[Freebird]

Originally posted by DarthTanyon:

none have ran away UNLESS I pulled them too far from the original spot in which I engaged them

This is the whole topic here. Why are you even writing. Pull and kite them "too far" away, which is basically nothing, and they reset. I pulled Tristan one screen size and he reseted all the time.

This is the whole talking point. They are roaming bosses, hard to find and hard to engange. So we should have the right to use the environment to fight them. Other than arena fights like Quincey.