Leapfrogging

[Melias]

During Luclin the first guild to kill Blob 1 in VT had claim to the rest of the zone until they left.

Also, single group clears for a raid were never really acknowledged.

GMs didn't intervene unless training occured (in which case it was ultimately just hearsay), or the other guild tried to killsteal the raid mob. They let the community sort it out 95% of the time.

[Bumamgar]

I never had GMs enforce any sort of leapfrogging rules for single named (ie: trash clearing in Fear or clearing down to the Royals in Chardok, etc). There were only two cases on EMarr where there were leapfrogging standards that were upheld by GMs: NToV in Velious and Vex Thal in Luclin. In both cases there was a "key mob" that once killed was considered claim to the rest of the wing/zone. For NToV it was Aary, and for VT it was Blob 1.

To avoid getting leapfrogged on single mobs guilds developed strategies to minimize the risk of being leapfrogged. For example, instead of clearing down to the royals, a common tactic was to pull them to the zoneline. Other tactics involved training away the trash so that the raid could move in to the main target without clearing, etc.

[Reiker]

Originally Posted by Bumamgar [You must be logged in to view images. Log in or Register.]

I never had GMs enforce any sort of leapfrogging rules for single named (ie: trash clearing in Fear or clearing down to the Royals in Chardok, etc). There were only two cases on EMarr where there were leapfrogging standards that were upheld by GMs: NToV in Velious and Vex Thal in Luclin. In both cases there was a "key mob" that once killed was considered claim to the rest of the wing/zone. For NToV it was Aary, and for VT it was Blob 1.

Pretty much my experiences in classic. In progression on one ever cared about "rights mobs" it was a complete free-for-all.

[xorbier]

Originally Posted by Bumamgar [You must be logged in to view images. Log in or Register.]

I never had GMs enforce any sort of leapfrogging rules for single named (ie: trash clearing in Fear or clearing down to the Royals in Chardok, etc). There were only two cases on EMarr where there were leapfrogging standards that were upheld by GMs: NToV in Velious and Vex Thal in Luclin. In both cases there was a "key mob" that once killed was considered claim to the rest of the wing/zone. For NToV it was Aary, and for VT it was Blob 1.

To avoid getting leapfrogged on single mobs guilds developed strategies to minimize the risk of being leapfrogged. For example, instead of clearing down to the royals, a common tactic was to pull them to the zoneline. Other tactics involved training away the trash so that the raid could move in to the main target without clearing, etc.

It was like this on my server too. You learned tactics to reduce leapfrogging and mobilizing quickly was key. Sometimes it was a fun race to the target!

[azeth]

Originally Posted by xorbier [You must be logged in to view images. Log in or Register.]

It was like this on my server too. You learned tactics to reduce leapfrogging and mobilizing quickly was key. Sometimes it was a fun race to the target!

The race, to me, is concluded the moment a viable "Trash" target is pulled/killed by a raid-sized group.

example - Trakanon's "viable trash" of course would be the golems (golems right?). A guild who's started clearing (with a feasible Trakanon sized raid) from the Fungus Covered Scale Tunic area down to Trak cannot then be "leapfrogged" by a separate guild.

[Tronjer]

My old server had two top guilds claiming all current content and there was an unwritten rule between us to not involve GM's, since nobody really wanted some kind of forced rotation or stuff.

So when we got leapfrogged in Vex Thal once, we just sucked it up.

[Humerox]

Found a link to a 3 day Guild Summit in San Diego hosted my Smed and crew. The problem is going to be your involvement in server issues and how they are handled. Your time is important...you don't need to be babysitting 24/7, and a system needs to be in place for the azzhats. Designing rules for submission of problems may be a start:



Policy:

The following issues may be submitted for a Guild Critical issue.
1) Spawn Disputes (When NPC triggers or Targets are spawned)
2) Raid Disruption (Training, Harassment, Kill Stealing, Leap Frogging, and Ninjalooting)
3) Character Flag Issues (NPC being under the world or not spawning). This may only be used if this affects a significant portion of your guild.
4) Incorrect Event Functionality

Guild Leaders will be limited to submitting a request 3 times a week during In-Game business hours Monday through Sunday (designate a time). We will be able to verify that the Guild Leaders are sending in the request based on their email address. If you have a new email address, please update your registration information, and let us know.

Procedure:
1) The Guild Leader submits a request to : <email>
2) Provide the one of the following text on the subject line: Guild Critical – Spawn Dispute, Guild Critical – NPC Name spawned, Guild Critical – Raid Disruption, Guild Critical – Flagging Issue, or Guild Critical – Event Dysfunction
3) Provide the Guild Leader, Guild, and Server name.
4) Please be as detailed as possible in your message by providing all parties involved including character names, NPC names, zone

Original article is:

HERE