Nerf monks?!

[REMEZ]

https://www.youtube.com/watch?v=xAa10CY-dT0

WTF?

[Fragged]

Lucky memblur on both mobs with the FD, the continued channeling doesn't reagro if you are out of agro range when the nuke hits or if you are out of line of sight (if you get off the agro table during the channeling that is).

[REMEZ]

Good to know! I have seen strange things like this happen when using FD earlier, but I managed to capture this situation so figured I would share.

[derpcake]

nerf people that use 3rd party tools to keep track of buff timers instead

[Jimjam]

The spell didn't break memblur because she /stand before the spell finished casting, right?

[derpcake]

The spell didn't break memblur because she /stand before the spell finished casting, right?

not really

memblur occured when he used FD, when he stood back up he didn't have agro

the caster mob did not re-agro because it was mid cast

even if it had not been casting, the caster and melee mob didn't re-agro, because he was in range for a very short period, and this was in the correct timeframe (mobs don't agro all the time, its based on a delay, maybe its a quarter of a tick or something, dunno exactly)

enjoy

[EQBallzz]

I think it has to do with being out of LOS when the spell lands. If you were to stay FD or just stand (but still be in LOS) the spell would break FD and because you are still in LOS they re-aggro. Since you got off a successful FD and then moved out of LOS before the spell landed they didn't re-aggro. I'm not sure why there wasn't a re-aggro after standing, however. You looked too close to them for at least one to not re-aggro upon standing (before you got out of LOS).

Also, love your other video pulling the Corrupter of Life. What was the point of that? lol. Here I am pulling the Corrupter of Life from second floor to first floor with cancel magic. Here I am dying to the train I caused from pulling the Corrupter of Life and all the other stuff that aggro'd along the way. lol.

[REMEZ]

I suicide pulled Corrupter so our monks could split/tag it and bring to our raid. I needed the part he drops for the Natures Defender (https://wiki.project1999.com/Natures_Defender) on my alt. I had no idea if it would work when we tried it, but I have done similar pulls in other zones.
I uploaded the video to show a buddy how it could be done since he wanted the sword aswell.

Clearing your way to him on 2nd floor can be time consuming and many guilds dont bother with it. This was an alternative to clearing 2nd floor :)

[Izmael]

Just discovered your videos and have to say I had a lot of fun watching some of them.

Make more!

[EQBallzz]

I suicide pulled Corrupter so our monks could split/tag it and bring to our raid. I needed the part he drops for the Natures Defender (https://wiki.project1999.com/Natures_Defender) on my alt. I had no idea if it would work when we tried it, but I have done similar pulls in other zones.
I uploaded the video to show a buddy how it could be done since he wanted the sword aswell.

Clearing your way to him on 2nd floor can be time consuming and many guilds dont bother with it. This was an alternative to clearing 2nd floor :)

Ahh ok. The context gives it more meaning. I was like..wtf was the point of that? lol.

[Tupakk]

Just discovered your videos and have to say I had a lot of fun watching some of them.

Make more!

lol right. Didnt think REMEZ had videos of stuff. I watched til auto play played something else.

[REMEZ]

Well I had a plan to edit the clips more and not just paste the raw footage, I wanted to describe the situation in detail as most players wont understand what is going on unless they have played an enchanter. But it takes time, skill and patience I dont have. If there is interest I may do some more recordings during my travels.

Looking at these clips myself today makes me realise how bad I played at times..

[Doctor Jeff]

The spell didn't break memblur because she /stand before the spell finished casting, right?

a spell landing on you does not generate aggro
There's no such thing as breaking memblur, just re-aggroing the mob.

the sneak memblurred and he stood up on the tick to move out of range before the server checked for aggro

[derpcake]

a spell landing on you does not generate aggro
There's no such thing as breaking memblur, just re-aggroing the mob.

the sneak memblurred and he stood up on the tick to move out of range before the server checked for aggro

a/s/l pls

<3

[fastboy21]

a spell landing on you does not generate aggro
There's no such thing as breaking memblur, just re-aggroing the mob.

the sneak memblurred and he stood up on the tick to move out of range before the server checked for aggro

This, but replace the word sneak with FD.

This is what happened.

1. monk aggros both mobs
2. caster begins to cast on monk
3. monk FDs. This FD was successful in memblurring both mobs (caster is still casting though)***
4. the monk stands up.
5. the monk moves out of line of sight before the mobs (re) aggro him***
6. the caster's spell lands on the monk (this has no effect on aggro)

***the fact that the FD memblurred is random. it is likely that one or both of the mobs not be memblurred by the FD (especially since the sneak nerf). the server doesn't check for aggro instantly, so you have a small window (which you can't really predict) to be in aggro range and not get aggro. If the FD had not memblurred both mobs and the window for the aggro check didn't work out in the monk's favor this result wouldn't be achieved.

(Its also possible to achieve a similiar result with sneak which would increase the window to move out of range before the spell lands as the the caster's spell would break sneak, which would have caused reaggro if still in range.)

[Skydash]

I never saw this happen on live during this era... when a mob was mid cast and you FD, he would re-agro after the spell hit no matter what. They had to introduce a specific AA later on to deal with remaining FD after a spell hit you to not re-agro. Why would they add that if the mechanic worked like this?

[Jimjam]

I think it has to do with being out of LOS when the spell lands. If you were to stay FD or just stand (but still be in LOS) the spell would break FD and because you are still in LOS they re-aggro. Since you got off a successful FD and then moved out of LOS before the spell landed they didn't re-aggro. I'm not sure why there wasn't a re-aggro after standing, however. You looked too close to them for at least one to not re-aggro upon standing (before you got out of LOS).

Also, love your other video pulling the Corrupter of Life. What was the point of that? lol. Here I am pulling the Corrupter of Life from second floor to first floor with cancel magic. Here I am dying to the train I caused from pulling the Corrupter of Life and all the other stuff that aggro'd along the way. lol.

Suicide pulling a train to a manageable place and working from there is a good way of pulling out the names in Hate. Obviously, it is preferable to get CoTHed, but a quick /corpse and a rez is a passable second option.

[surron]

no idea how a gfx overlay is allowed on p99 lol

[fastboy21]

I never saw this happen on live during this era... when a mob was mid cast and you FD, he would re-agro after the spell hit no matter what. They had to introduce a specific AA later on to deal with remaining FD after a spell hit you to not re-agro. Why would they add that if the mechanic worked like this?

I'm not certain about this.

I think the biggest issue on p99 versus live with aggro has to do with the ticking in getting aggro, which contributes significantly to getting this type of result in the video.

It was iirc much worse at launch on p99 because you could actually figure out the timing of the aggro ticks and run past things quickly if you were clever. They fixed it so that it was either random (not associated with the regular server tick for regen, etc.) or was a faster tick. In any case, it is still relatively large on p99 compared to live.

On live if you were being cast on and ran out of los, hit FD, stood up, spell hit you did you ALWAYS reaggro the original mob? I believe there was a chance to avoid the reaggro if your FD had wiped the caster and you were out of distance of a fresh aggro. Its the sort of thing that I don't trust my memory on completely from live, especially since my main wasn't a monk.

[Bessy]

[QUOTE=fastboy21;2488914]I'm not certain about this.

I think the biggest issue on p99 versus live with aggro has to do with the ticking in getting aggro, which contributes significantly to getting this type of result in the video.

It was iirc much worse at launch on p99 because you could actually figure out the timing of the aggro ticks and run past things quickly if you were clever. They fixed it so that it was either random (not associated with the regular server tick for regen, etc.) or was a faster tick. In any case, it is still relatively large on p99 compared to live.

On live if you were being cast on and ran out of los, hit FD, stood up, spell hit you did you ALWAYS reaggro the original mob? I believe there was a chance to avoid the reaggro if your FD had wiped the caster and you were out of distance of a fresh aggro. Its the sort of thing that I don't trust my memory on completely f

rom live, especially since my main wasn't a monk.[/QUOTEd

Nerd

[prc018100]

I'm not certain about this.

I think the biggest issue on p99 versus live with aggro has to do with the ticking in getting aggro, which contributes significantly to getting this type of result in the video.

It was iirc much worse at launch on p99 because you could actually figure out the timing of the aggro ticks and run past things quickly if you were clever. They fixed it so that it was either random (not associated with the regular server tick for regen, etc.) or was a faster tick. In any case, it is still relatively large on p99 compared to live.

On live if you were being cast on and ran out of los, hit FD, stood up, spell hit you did you ALWAYS reaggro the original mob? I believe there was a chance to avoid the reaggro if your FD had wiped the caster and you were out of distance of a fresh aggro. Its the sort of thing that I don't trust my memory on completely from live, especially since my main wasn't a monk.

I played a monk and pulled for a major guild and the way it works on P99 seems very different from live. Once the mob started casting on you on live, you could not avoid the re-agro when the spell hit you. Being out of LOS did not matter. The trick was to get out of LOS when the spell hit so you could quickly FD again and avoid a re-cast / re-agro. With a single mob or multiples casting at the same time, sometimes you could perfectly time your FD after the spell hit you and avoid the mob re-casting / re-agroing.

Also, if you didn't get the FD fail message "fallen etc." then the FD was successful for all mobs. Not sure if that is how it works here as I haven't played around with the recent changes, but the way I read it was that you have a memblur chance for each individual mob. On live, I remember it being more all or nothing.

[mickmoranis]

ahaha this one has a hilarious ending, saw it coming with the second mez cast XD

https://youtu.be/VzloQIuvGVY

[derpcake]

I think the biggest issue on p99 versus live with aggro has to do with the ticking in getting aggro, which contributes significantly to getting this type of result in the video.

The info you are posting is flat out incorrect.

Try running through a zone on eqlive with a bard with fading memories.

Stuff agroes you, you hit fade (instantly dropping all agro), no other stuff wil agro you for 5 seconds, at which point you fade again.

Works exactly on live as on p1999, lets not state that bit of the code was even touched on this server.