|
|
|
|
#3
04-06-2018, 09:03 PM
|
|||
|
My point being with sneak up you can't agro wyvs where Bruize was. Now that I've had time to see all of this I'm more happy that the offer was rejected by AM. The videos in this thread prove only that both AM and Bruize got ganked by Wyvs. What it doesn't show is who actually caused the chain agro on them first of all. The big bully tactic almost won, but maybe you guys realized you would get in potentially more trouble if you took the loot on your wolf crying as well? Probably only worth the risk to you if gharns was on the body.
| ||
|
|
|||
|
#4
04-06-2018, 09:05 PM
|
||||
|
Quote:
| |||
|
|
||||
|
#5
04-06-2018, 09:25 PM
|
||||
|
Quote:
Just so you, and all other monks on the server know: https://imgur.com/a/TRg6r Is -still- in LoS of the wyvern door. What it -DOES- show is what caused the chain agro first of all. Notice how that black ebon hatchling attacks Bruize despite not being kos? That's established social agro. There is no way to force social aggro on to another player. The non-kos hatchling engages him as soon as his big ass train gets in range to social aggro that hatchling. Notice how it doesn't attack anyone else? It's a non-kos mob. It would only engage IF the player it engages has pre-existing threat. Like Bruize. It attacks -no one- else. Notice that there's no "lets out a piercing roar as it charges forward!" messages on to Bruize? That's because the initial trigger of the wyvern trap was out of range for /say to trigger. Notice how there's none at all in the entire video? That's because nobody feigns and drops aggro onto him. If ANYONE had pulled them out and feigned on to him, there would be 14 messages in chatbox saying they had engaged a new target. If someone other than Bruize was to blame, there would be evidence abundant via chat box spams on mobs, or videos of people getting plowed/feigning in wyvern hall. There is none. Also, there's no social aggro for him to have picked up there. He would be a 100% new threat entity, so the triggers would have positively gone off -- and if they hadn't, it would mean he deliberately got on their threat table and pulled into the pull path instead of accidentally. So either he accidentally did it, or deliberately did it. Which would you prefer? Notice how that message about "lets out a piercing cry as it charges forward" goes off when Bruize feigns death in both videos? That's a re-engage message. Those mobs have specific messages to announce when they have acquired someone on their threat table. As soon as Bruize feigns, they begin going out in mass and slaughtering people. But hey man, you keep drinking that Breaken koolaid. PM me when you want off the sinking ship and I'll set up your AM app. | |||
|
|
||||
|
#6
04-06-2018, 09:32 PM
|
||||
|
Quote:
You almost got me to log in my monk to compare Bruize's fraps to my own monk running by. But I will let you figure this one out on your own personal time.
__________________
Dannyl
| |||
|
|
||||
|
#8
04-06-2018, 09:12 PM
|
|||
|
Nacht, you got a clip of the scene your avatar is from? Been lookin for it since I hit level 50 on Kunark.
__________________
Ainton Brutaman - 60 Warlord <Auld Lang Syne>
| ||
|
|
|||
|
#9
04-06-2018, 09:24 PM
|
||||
|
Quote:
__________________
 | |||
|
|
||||
|
#10
04-06-2018, 09:21 PM
|
|||
|
I mean Pezy clicked the mob in the video and assisted. It was on Bruize. There was no way anyone could have flopped it on him because Bruize was with them in the Fraps when the first FD happened well past the mobs he trained.
Looks like Diamondfist is just mad because his guild played bad and the other guild asked for it to be fixed. | ||
|
|
|||
 |
|
|
Hybrid Mode
