![]() |
#91
|
||||
|
![]() Quote:
| |||
|
#93
|
||||
|
![]() Quote:
O_o That seems a little backwards...
__________________
"Everything can at all times be stated, for it will always be understood by those who are able to understand."
- Eliphas Levi | |||
|
#95
|
||||
|
![]() Quote:
I think it goes back to when they were children and if they screamed loud enough, for long enough, their parents would give them whatever they wanted. That obviously won't happen here though.
__________________
![]() Part of me says I can't keep drinking like this. The other part of me says, "Don't listen to that guy. He's drunk" | |||
|
#96
|
||||
|
![]() Quote:
She never said they weren't, she said(if you read what she said) that they weren't in trouble.
__________________
"Everything can at all times be stated, for it will always be understood by those who are able to understand."
- Eliphas Levi | |||
|
#97
|
||||
|
![]() Quote:
However, I suggest you put in a petition to ask her direct opinion. | |||
|
#98
|
|||
|
![]() ITT: People who never fought in Veeshan's Peak on live or here.
| ||
|
#99
|
||||
|
![]() Quote:
| |||
|
#100
|
||||
|
![]() I'm not sure if you missed the post I made earlier about the mechanics of mob pathing, but incase you did- here it is again;
Quote:
In case anyone in this thread is hazy on the details of what has been going on in Veeshan's Peak lately, let me inform you. -Because the encounter logs were at one point (or may still be) cleared by a memory blur, extra code was added to the perl scripts of the raid NPCs. This code essentially stated, if the aggro list is empty, heal the mob to 100% hitpoints. Not, wait a tick and heal the mob, not regen at 50% hp a tick. This was a full-out, 100%, INSTANT complete heal when a memblur successfully landed. This was only for raid level npcs, and is why most players have never noticed it. Why they did it like that? I can only speculate. Perhaps the encounter logs were only designed to be saved when the mob was actually slain because otherwise you would get tons of encounter logs for non-kills. If you only save when the mob is actually killed, then you only need that log to see which guild had first to engage, and of course- which guild was owed the loot. The first "exploiting" started when Vesica Dei decided to use this against us in Veeshan's Peak. Memory blur on live never caused a mob to heal to 100%, in fact, because of the spellfiles here- Vox doesn't even complete heal to 100%. Vox can only cast the cleric version of complete heal which is 7500 hp instead of the 32khp it should be right now. On live, when Vox CH'd, it was a MUCH bigger deal than it was here. but we're straying away from the main point- Which is that memory blurs or empty aggro lists never made mobs regen to 100%hp instantly, or even in a single tick. Yes, uber mobs have uber regen, but it is not 100% hp in one tick. This is supported by so much evidence it's not even worth arguing. So the only reason TMO was using that ledge was because we could not keep Vesica Dei's self-proclaimed "Occupy VP" team of 3-8 people from griefing 30-50 other players out of a deserved kill. With, guess what? An exploit, a side effect of this server's encounter log code that made it terribly easy for anyone with a memory blur spell (clerics, enchanters) or anyone who hung out in Old Sebilis at the shrooms, because they guess what? Drop an item that allows any class to memory blur a mob. Coldblooded even made it a point for her guild to farm these so they could be used to harass us with this completely unintended game mechanic. Am I trying to say exploiting is ok? Fuck no, I found that spot in VP, we got to it with normal means, normal spells. The intent of using that spot was simply to prevent them from being able to constantly resurrection box enchanters into the zone so easily to Complete Heal the mobs we were fighting with an obviously bugged game mechanic. You wanna call anyone exploiters? It's Vesica Dei. For us, shit going through walls is a pain in the ass, we don't like it, we'd prefer it came normally but even in normal pull locations you still have dragons warp behind you and AE your entire raid for no reason. We do not want this, we want all pulls to follow pathing, and the only reason TMO went to that ledge was because we were being literally terrorized by Vesica Dei with a known game exploit. This exploit is currently fixed pending patch. and fighting an exploit with an exploit? Hell no, it was nothing like that. Plenty of the dragons path normally onto the ledge, it simply depends on where in the zone they are located. They have always AE'd, we have fraps to prove it- they have always been able to hit our players when they are next to them, and as some people have pointed out in the past. We can simply dogwalk mobs to the ledge and make them come up without pathing through the walls. It never seemed like a problem to us because with our pull strategy. (Which is entirely legitimate) - We never get adds anyways. The reason we weren't punished? Because it wasn't wrong until they told us not to do it, not because it was an exploit- because they simply did not believe it was the way they wanted VP to be used on their server- and when they did we complied. As the server does belong to nilbog and Rogean, if they decide something we do isn't to their liking we have no problem stopping that activity, but we can't be punished because we found a novel way to prevent another guild from using a known exploit against us. and shit? If you ask me, had people on live been under the pressure TMO was in- they probably would've found the same spot. All of that aside, it's already been stated by the staff; TMO was not exploiting, they are just not allowed to use that spot as it's probably not something the developers on live ever anticipated and they don't know how to deal with it here. That's cool, I understand- The Mystical Order understands, we just hope you can patch that memblur fix in as soon as you can.
__________________
![]() Part of me says I can't keep drinking like this. The other part of me says, "Don't listen to that guy. He's drunk" | |||
|
![]() |
|
|