Project 1999

Go Back   Project 1999 > General Community > Off Topic

Closed Thread
 
Thread Tools Display Modes
  #1  
Old 09-25-2015, 05:39 PM
xate xate is offline
Skeleton


Join Date: Jan 2011
Posts: 16
Default

Quote:
Originally Posted by BossThunderace [You must be logged in to view images. Log in or Register.]
This is where it started..some people from A&H went to Starvald, said members jumped a day or two before a planned A&H Vox Raid. Starvald exploited vox and got the kill 1 day before A&H planned raid. Also appeared that Starvaled boxed one of A&Hs mages for the kill. Next Vox pop, A&H is in prep room, Starvald jumps ahead and uses levi trick to get to vox backdoor. GM appears and says you cannot use levi trick to get to vox backdoor, and tells starvald to go to prep. A&H proceeds to clear IGs > Engages Vox > Wipes. Starvald jumps in and kills Vox during A&H wipe. GM shows up and resets Vox. i don't remember the details after that. This is essentially the start to takp drama + "GM enforced raid rot"
Your details are a little muddied with time, it was more like both A&H and SD were in the King area when Vox window was due, with 1 or 2 ultra-bored players on both sides playing around with levitate when the GM came along and asked both sides not to do it. After a short while A&H suicide & ressed past the 4 mobs between king and the rock to Vox's lair, Vox coincidentally spawned shortly after they finished that manouver.

SD, who was a guild with 4-5 people in it who had already resigned themselves to probably hardly ever getting any dragon kills with the behemoth A&H on the server, proceeded with their strategy of implied pressure and tactically bunny-hopped a&h at the boulder, after clearing up from king while a&h cleared the giants in the lair. The plan worked perfectly, a&h paniced and Main Tank the Warlord led a flimsy poorly executed charge on Vox with most of the guild still sitting around outside in prep. After the dust settled, SD went back in (after falling back on the a&h engage) to fight Vox in a 4 minute fight cause of their low #s, the entire time in which A&H was petitioning and /tell'ing the GMs trying to pretend that normal codes of conduct on EQ emus insist that the guild to clear the lair of giants has some kind of kill window, which they eventually succeeded in as the GMs #kill'd vox as SD was about to finish her and began enforcing rotation discussions.

I'm not as familiar with the (unrelated) banning events that happened, but the bans were still probably the major part of the reason the a&h officers left the server though, understandably.
  #2  
Old 09-28-2015, 07:34 PM
apio apio is offline
Banned


Join Date: May 2010
Location: Spain
Posts: 288
Default

Quote:
Originally Posted by xate [You must be logged in to view images. Log in or Register.]
Your details are a little muddied with time, it was more like both A&H and SD were in the King area when Vox window was due, with 1 or 2 ultra-bored players on both sides playing around with levitate when the GM came along and asked both sides not to do it. After a short while A&H suicide & ressed past the 4 mobs between king and the rock to Vox's lair, Vox coincidentally spawned shortly after they finished that manouver.

SD, who was a guild with 4-5 people in it who had already resigned themselves to probably hardly ever getting any dragon kills with the behemoth A&H on the server, proceeded with their strategy of implied pressure and tactically bunny-hopped a&h at the boulder, after clearing up from king while a&h cleared the giants in the lair. The plan worked perfectly, a&h paniced and Main Tank the Warlord led a flimsy poorly executed charge on Vox with most of the guild still sitting around outside in prep. After the dust settled, SD went back in (after falling back on the a&h engage) to fight Vox in a 4 minute fight cause of their low #s, the entire time in which A&H was petitioning and /tell'ing the GMs trying to pretend that normal codes of conduct on EQ emus insist that the guild to clear the lair of giants has some kind of kill window, which they eventually succeeded in as the GMs #kill'd vox as SD was about to finish her and began enforcing rotation discussions.

I'm not as familiar with the (unrelated) banning events that happened, but the bans were still probably the major part of the reason the a&h officers left the server though, understandably.
You are describing the incident that occurred a week after the scenario that you are commenting on: The first Vox respawn. She wouldn't have been "due" if nobody had killed her the week prior [You must be logged in to view images. Log in or Register.]

The first Vox kill was indeed only possible because 2 of our members jumped ship without explanation the evening before our planned raid (at the time we were the only guild capable of killing Naggy and Vox), and joined Starvald. They then used another of our guildmember's mage boxes to get enough firepower to get the server first with another guild. Very poor sportsmanship indeed.

Just wanted to point out why there's confusion, it's 2 separate incidents
  #3  
Old 09-28-2015, 09:22 PM
xate xate is offline
Skeleton


Join Date: Jan 2011
Posts: 16
Default

Quote:
Originally Posted by apio [You must be logged in to view images. Log in or Register.]
Just wanted to point out why there's confusion, it's 2 separate incidents
Not sure what confusion you're referring to, I was simply correcting BossThunderace's inaccurate history that Vox was "exploited" by starvald, presuming he referred to our week 2 kill, but works for our week 1 kill too.

Quote:
Originally Posted by apio [You must be logged in to view images. Log in or Register.]
(at the time we were the only guild capable of killing Naggy and Vox)
That's a silly thing to say on a triple boxing server about such an easy mob (unless you're the only guild on the server), but it would explain where the exploiting rumours probably started from.
  #4  
Old 09-28-2015, 09:44 PM
apio apio is offline
Banned


Join Date: May 2010
Location: Spain
Posts: 288
Default

Quote:
Originally Posted by xate [You must be logged in to view images. Log in or Register.]
Not sure what confusion you're referring to, I was simply correcting BossThunderace's inaccurate history that Vox was "exploited" by starvald, presuming he referred to our week 2 kill, but works for our week 1 kill too.
IIRC those Vox kills both were only possible because pets inside walls were not getting hit by Vox Cold AE and Fears. But that's just what the GM team at the time were telling us. I wasn't present at either of those kills.

Quote:

That's a silly thing to say on a triple boxing server about such an easy mob (unless you're the only guild on the server), but it would explain where the exploiting rumours probably started from.
It is a perfectly valid thing to say, seeing as you recruited two of our level 60 members (boxing 6 characters in total, including an extra Mage that didn't belong to your guild, or those 2 players) before you attempted Vox.

Thanks to that, we will never truly know whether or not you would have been able to down Vox at that point. But the fact that you did NOT prior to recruiting from our ranks, and the fact that your server first kill includes a Mage with the <Armed & Hammered> tag is painting quite a picture.
  #5  
Old 09-28-2015, 10:52 PM
xate xate is offline
Skeleton


Join Date: Jan 2011
Posts: 16
Default

Quote:
Originally Posted by apio [You must be logged in to view images. Log in or Register.]
IIRC those Vox kills both were only possible because pets inside walls were not getting hit by Vox Cold AE and Fears. But that's just what the GM team at the time were telling us. I wasn't present at either of those kills.
It is unfortunate that melee push code wasn't put in at the time, which does dramatically lessen the effectiveness of pets on Vox, but hardly evidence that she wouldn't have been killable by us, especially when we still kill her with roughly the same numbers and class composition even though pets are feared most of the fight.

The "recruiting from our guild" is conveniantly leaving lots out of context. A&H had a strategy of recruiting everyone on the server they could, supposedly so they could be "the only guild capable of killing naggy or vox" by way of having 80%+ of the 50s tagged. Unfortunately this was a double edged sword, why would your best players stay and share loot with a mass of people when there's other options? Picking off your best players was as easy as a one line /tell, fair game is fair game.
  #6  
Old 09-29-2015, 12:21 AM
apio apio is offline
Banned


Join Date: May 2010
Location: Spain
Posts: 288
Default

Quote:
Originally Posted by xate [You must be logged in to view images. Log in or Register.]
The "recruiting from our guild" is conveniantly leaving lots out of context. A&H had a strategy of recruiting everyone on the server they could, supposedly so they could be "the only guild capable of killing naggy or vox" by way of having 80%+ of the 50s tagged. Unfortunately this was a double edged sword, why would your best players stay and share loot with a mass of people when there's other options? Picking off your best players was as easy as a one line /tell, fair game is fair game.
I am sure besides being pissed off about the obvious backstabbing and bad sportsmanship on the server first, nobody in our guild really was upset about those people leaving after the fact. If your only answer to a difference in opinion is to betray your guild for a chance at pixels, you are obviously a terrible guild mate and only in it for yourself. The fact that you seem to encourage this kind of behavior and would want these kind of people in your guild speaks volumes.
Closed Thread


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 11:55 AM.


Everquest is a registered trademark of Daybreak Game Company LLC.
Project 1999 is not associated or affiliated in any way with Daybreak Game Company LLC.
Powered by vBulletin®
Copyright ©2000 - 2026, Jelsoft Enterprises Ltd.