This is a wiki for a reason. Anyone can contribute. If you see something that is inaccurate or can be improved, don't ask that it be fixed--just improve it.
[ Disclaimer, Create new user --- Wiki markup help, Install P99 ]

Blue Raid Rules

From Project 1999 Wiki
Jump to: navigation, search

P99 staff gave since consolidated the raid rules on this forum post. Likely no updates will be made to this page as long as the forum post is kept up to date.

WARNING: This page is NOT guaranteed to be comprehensive, or endorsed by the Project 1999 staff. Like the rest of the wiki, the only guarantee is that it's a volunteer's best effort. At any time a staff member may make a new ruling that's not included here. In order to avoid rule manipulation, please provide evidence of changes via forums links, screenshots, etc.

The goal of this page is to provide a means of bringing together all the GM decisions, petition replies, and official rules into a single place that guilds may review, learn, and obey when raiding on P1999. If something is missing and you don't want to add it, post on User_Talk:Kaejer.

Contents

Rules For Editing

1. Don't post malicious updates, they will result in you being suspended or banned.
2. Cite your claims. Forum posts, screenshots, copy/paste of evidence, etc.
3. This is supposed to be constructive, so keep the fighting in RNF.
4. If a rule has been contradicted by a GM, the decision most recent is the "Offical" rule until a GM announces something different.
5. Use footnotes for any information that is not 100% confirmed by a GM, but is generally assumed based on GM rulings.
6. This is a wiki, it can be edited by anyone, so don't expect to be able to point at this and scream at a GM. This exists to document their decisions in a clear and concise way, not as an edict for them to follow.

This is to be for rules only, if you are looking for GM past rulings to specific rule descriptions, see Rulings. See also the general Play Nice Policy[1] and the specific Play Nice Policy[2], which applies to raiding.

Raid Rules FAQ

From this forum post: [3].
Last Updated: July 16, 2018

Q1: What is considered a "raid" on Project 1999?

A: A raid is any group of players looking to engage a raid target OR any force consisting of more than one group united in a common goal. This means that three people can be considered a raid if they intend to kill a raid target, or 20 people clearing fear trash. Most epic NPC's are not considered "raid" mobs. The exception to this is Ragefire, which is considered a 'high tier' mob along with mobs like Lodizal and Vindi. For all other intents and purposes, these mobs are treated as a 'high tier' NPC (ie: camp/poopsock rules do not apply). Please keep in mind that because of the need to clear to a raid target, trains enacted on players while on the way to these mobs can be considered raid violations and action could be taken against your guild as a whole, regardless of whether the victims are part of a raid. It is in your best interest to be very careful when racing for a target, especially when it involves training away mobs.

Q2: What exactly is Raid Disruption or Raid Interference?

A: Q3 and Q4 deal with what to do when this happens, but "Raid disruption" and "raid interference" are broad terms that cover a long list of things (near simultaneous FTE, training, kill-stealing, setting of AEs on other people, any violation of the posted raid rules, etc).

Q3: If we feel our own guild/party has violated a rule, what actions should we take?

A: If you screw up, then you should concede the mob you screwed up on.

Q4: If we feel another guild/party is breaking raid rules what actions may we take?

A: It is probably in your best interest to work raid disputes out among yourselves. The other option is the petition forum.

Q5: What about in cases where the mob dies before anyone is sure whom is at fault?

A: See Q4.

Note on Conceding / Forfeiting – You should concede a mob whenever your actions negatively impact another guild’s attempt at a mob, regardless of which zone the mob or the infraction take place in. Also, as far as what to concede / forfeit, if you still have a shot at the current mob, you should concede/forfeit that mob, if you do not still have a chance at the current mob, you should concede/forfeit the next two (it’s silly to try and concede a mob after you no longer have a real chance to kill that mob.

Note on Crying Wolf – if you request that another guild concede a mob, you better be 100% certain that they made an error, otherwise you may be punished harshly.

Note on Lockouts – if you concede a mob, or are suspended from a mob, those mobs will not be the mobs you are locked out from, they will be in addition to the mobs you are locked out from.

Note on Rule Lawyering – I think the spirit of everything we are trying to accomplish here is pretty clear. Anyone that tries to twist the words to support and/or justify nefarious actions will not be rewarded. There will be no “technically this could be that”, or “well it doesn’t exactly say this word for word”. From this point forward we will be actively enforcing the spirit of these rules more so than the exact letter of the law. Don't expect to skirt passed a raid suspension on a loop hole or technicality.

Q6: If we must bring a dispute to the GM's, how do we go about doing this?

A: If a guild breaks a rule, and refuses to remedy the situation as described above, then have one officer or leader with the authority to negotiate disputes for your guild petition in the petition/exploit forum. Please use clear formatting, cohesive sentences, and paragraphs. A full and detailed description of the event must be submitted (if the video is more than a couple minutes then you should include timestamps of importance). Include fraps, screenshots, and logs where applicable. We also request you provide a brief summary of the negotiations that took place (and likely failed) prior to the dispute being escalated to the CSR staff.

Q7: What classifies a mob as "Engaged"?

A: A mob is classified as engaged as long as it has aggro on at least one player. Once a mob has lost aggro on all players on its hate list, it will begin to path back towards its last location prior to being engaged. The mob is considered 'un-engaged' as soon as it is pathing back to where it belongs. You may engage the target as soon as you are able to obtain a new FTE message. You do not have to wait for it to path all the way back to its spawn spot. The intentional manipulation of FD, Charm, DA, and other similar mechanics used to engage/disengage a raid target multiple times in an attempt to prevent other guilds/parties from engaging, or to try and get another guild/party wiped, will be viewed as raid disruption.

Q8: Can we camp raid mobs?

A: No, all raid targets are first to engage. Note* If another guild/party wipes on a raid mob, you may engage that raid mob, as soon as its aggro/hate list is clear. You do not have to wait for it to path back to its spawn spot, nor do you have to wait for it to regen back to full health.

Q9: What rules pertain to raid mobs that are triggered spawns? Either by turn in or the killing of another mob?

A: If a raid mob is triggered to spawn by killing a single mob before it (Example: Statue -> Avatar of War), the guild/party that spawned the mob has 20 minutes to engage it. The mob is open to any other guild/party on a first to engage basis once the first guild/party either no longer has a presence, or the first guild/party has wiped, or has not been engaged within the 20 minute time limit. To clarify, one engage is defined as the mob getting aggro on one or more players from the raid, and then ending after losing aggro/resetting when those players have been killed or forced to abandon the fight. Once a triggered spawn no longer has aggro on anyone, it can be killed by anyone.

Q10: What about a raid mob being indefinitely kited, stalled, or occupied?

A: It is against server policy to indefinitely kite, stall, or otherwise keep occupied a raid mob without intention of killing it. You either bring it to your raid, die, or zone out. Obvious stalling of a raid mob, especially in situations to prevent engagement by another guild/party, is against the rules. Ignorance is not an excuse to break this rule. If you are pulling raid targets, we expect you to know what you’re doing.

Q11: What about training away trash mobs?

A: This is acceptable, but if you choose to use this tactic, you must keep in mind that you are responsible for your trains/mobs. Meaning if your trainer dies or zones, and the mobs go wipe another guild, that’s still training. When the time comes to purposely drop the train, make sure to communicate and coordinate with any other guilds in the zone. This means actually communicate so that both parties have a fair amount of time to work out a safe place, or a safe time to drop the train. Please try not to run your trains within aggro range of another guild or raid party.

Q12: What exactly does the Staff consider a stall?

A: As far as engage stalls, the Staff will grant you one DA, or about that much time on an engage before considering it a stall. So it’s important that guilds do not engage a mob until they are ready to kill it. The spirit of the rule (and what we are looking to do here) is to prevent guilds from locking up a target before they are ready to kill it, just to prevent other guilds that are ready to kill it first/faster. If you stall, you need to drop aggro immediately and concede/forfeit the mob. Any number of players can be considered to be stalling a mob, what we look for is the engage of the kill force. I know some of you want an exact number of seconds, or players, or DPS done. But the fact is that’s just not realistic with guilds being so vastly different in numbers and strength, while also competing for the same content. The most important thing here is the statement about the spirit of this rule stated above.

Q13: Will the planes be open to everyone?

A: Yes. Please be respectful to your fellow players and respect their space. If there is a guild/party in Hate and they start pulling creatures, don't go up there and sit on top of them pulling mobs in their area as well. If Guild A is doing Hate, then perhaps Guild B should be doing something else. Basically, don't be a douche bag. If you insist on being in the same plane at the same time as another guild/party, you may not set up camp on top of where another guild/party has already set up camp. To clarify, there is no limit to the number of guilds/people allowed in the planes at one time.

Q14: Do we have "No-CSR" zones on Project 1999?

A: At the moment, no.

Q15: Are either of my two trackers allowed to get FTE?

A: Absolutely not. If one of your trackers gains FTE, you need to drop aggro immediately and concede/forfeit the mob. Furthermore, if a guild gets FTE, any other guilds that are tracking the mob and end up with tracker FTE as a result of the first guild are not DQd from the mob.

Q16: Are we allowed to bind at raid mobs? And/or camp out toons at raid mobs?

A: Absolutely not.

Q17: How can a guild move from Class C, back to Class R?

A: If a Class C guild does not get a Class C kill for 30 days, then that guild can request that the staff place them back inside Class R. This request will be reviewed and then decided by the staff on a case by case basis.

Q18: Where can I deposit my tears?

A: As always, your tears and crying of favoritism are important to us; for without you we couldn't possibly run things around here.

Q19: What if I think a Staff member made a mistake?

A: If you feel that a Staff member may have made a mistake, we encourage you to politely and respectfully explain the situation in the Petition/Exploit section of our forums.

Q20: What if I have a legitimate complaint against a Staff member?

A: Any complaints against a Staff member should be sent to Llandris via a private message on the Project 1999 forums. Any complaints against Llandris should be directed to Rogean via a private message on the Project 1999 forums. Any complaints against Rogean should be directed to Nilbog via a private message on the Project 1999 forums.

Additional footnote that you can contact Menden instead of Llandris.

Q21: How much time do I have to file a petition?

A: In order to request the review of a dispute, there must be a petition in the petition/exploit forum about the incident no more than one week (seven days) from the time of the dispute in question. The seventh day is the last day a dispute may be escalated to the server GMs. When filing a dispute, please use the "Other" prefix, with the title of the thread relevant to the incident. You must list at least one primary contact from your guild who has the authority to communicate with the staff and the opposing guild, as well as make decisions regarding the incident. Improperly filed petitions will be ignored. While we do accept Fraps that has been edited to point out specific things, you must also include the original unedited version (meaning all video and audio) or it may be ignored.

Q22: Are we allowed to use Rezz or Rezz bot tactics to acquire FTE?

A: In short, no. do not park corpses at raid mobs with the intent of rezzing them in for FTE, do not etc.

Q23: What exactly is off limits during a Raid Suspension?

8/29/2022 update from this post: [4].
A: Anything that has an FTE message and/or is considered more than one group content is a no (except Guardian Kozzalym, Master Yael, Verina Tomb, Vessel Drozlin, Lodizal, and Ragefire), no planes (except Plane of Mischief which is not considered a raid zone), no VP, no ToV, no ST, no Ringwar. Exception: PoM is permitted, as long as you are bound there, or have quick access to this zone. You may not attempt to enter the zone if there's any chance you could interfere or agro ToV content. Violators could be met with a PNP violation.
Note on Plane of Mischief: Players may travel and adventure there normally during a raid suspension, but cannot travel there through the Temple of Veeshan if they are raid suspended from the Temple of Veeshan.

Q24: How many raid targets can a guild be killing, engaged on, or have FTE on at a single time?

A: A guild may only be killing, engaged on, or have FTE on one raid target at a time.

Q25: If my guild FTE's or engages a raid target, how long must we wait before FTE'ing or engaging another raid target?

Removal from this post: [5].
A: If a guild/party FTEs or engages a raid target, they may not FTE or engage a second raid target until the first one is dead or until 30 minutes has passed (this doesn't apply to triggered spawn targets that your guild triggered/spawned). Example: If your guild is in EJ and you have Sev incoming to your raid, but then Vulak pops, you are no longer allowed to just drop the Sev pull to go for Vulak. You must either kill Sev, or wait 30 minutes before FTEing a new target. The only thing this rule does is further force guilds to prioritize which targets they go after. It does not change any other aspect of raiding on the server.

Q26: What exactly does the staff consider a Raid mob?

8/29/2022 update from this post: [6].
A: Aary, Avatar of War, Cazic_Thule, Cekenar, Dagarn, Dain, Dozekar, Druushk, Eashen, Faydedar, Final_Arbiter, Gorenaire, Gozzrem, Hoshkar, Ikatiar, Innoruuk, Jorlleag, Kelorek_Dar, King_Tormax, Derakor the Vindicator, Klandicar, Lady_Mirenilla, Lady_Nev, Lady_Vox, Lendiniara, Lord_Feshlak, Lord_Koi`Doken, Lord_Kreizenn, Lord_Nagafen, Lord_Vyemm, Master_of_the_Guard, Nexona, Phara_Dar, Progenitor, Sevalak, Severilous, Silverwing, Sontalak, Statue_of_Rallos_Zek, Talendor, Telk, Trakanon, Tunare, Velketor, Venril_Sathir, Vulak, Wuoshi, Xygoz, Yelinak, Zlandicar, Zlexak, as well as Fright, Dread, Terror, and Draco in Plane of Fear, all named mobs in Plane of Growth, all of Plane of Sky (this does not apply to island 1.5 in Sky (Noble/Gwan)), along with Maestro and mini bosses in Plane of Hate (if a guild is actively clearing hate when a mini boss spawns, they will not be DQ'd from that mini boss).

Q27: What happens if there's a simulated re-pop while we are currently in a raid zone?

A: As long as the person or persons that were in the zone leave that zone or go back to the race line and come back before doing anything with the desired raid target, you will not be DQ'd from that target (camping/logging out of game does not count). We do not want people socking re-pops, but we also do not want to punish players by preventing them from doing other things (like HoT, Juggs, Vindi, etc) for fear of getting their guild DQ'd. This should accomplish both of those things, but will be updated if/as needed.

Q28: Where are starting lines for FTE racers?

A:

The rules for racing speed are ambiguous for Blue P99. The general social assumption is Spirit of Wolf speed for everything except for Gorenaire, Tunare (FTE on Guardian of Takish), and Veeshan's Peak, which has no speed limit. There is no official raceline starting point for Plane of Growth or Tunare.
Assumed and not confirmed rules listed based on this Discord message and the forums Green raiding post[7]. No further clarification was provided for Blue raiding.
Galach racing rules.png

Q29: Can we use Illusions or Crown of rile on races?

Crown of Rile spam + Jumping is not allowed on any races.

AON or Skeleton Illusion is not allowed on any races.

Q30: What can a tracker do?

Trackers are for tracking. They cannot kite, pull, DPS, heal, or perform any actions that would populate on an encounter log.

For Example: A mage tracker can COTH + lay down rods, but can't nuke or utilize their pet.

Please Note: If utilizing a necromancer as a tracker, be aware their "twitch" spells will create an entry on an encounter log as well.

If utilizing a cleric tracker; they will no longer be able to rez dead bodies or heal any players that are part of the encounter.

For Brevity:
Guilds are only allowed a maximum of two trackers in a zone. It is permissible for a tracker to gate, camp out, or return to the zone line in order to clear their "tracker status" as long as the total number of trackers are two or less. Additionally; we do not want to discover guilds abusing the two tracker rule and create unfair advantages by sneaking in a third tracker. If there are more than two trackers logged in; it would result in a disqualification for their guild.

In the event of a raid target spawning; two trackers are allowed to check a target with their active raid force beyond the entrance; however, that raid force must return to the entrance before being COTHed or moving towards that newly spawned target. We do not want guilds abusing the definition of a raid force by having multiple players online, sitting at spawns claiming to be part of a raid force, when they aren't helping with the target of the primary raid force.

If it is brought to our attention a guild is abusing the two tracker rule and/or participating in actions that would be in violation of our guidelines; we will consider enforcing stricter rules and/or severely punishing the involved guild(s).

Q31: What is a concession? Are there any specific rules around concessions?

The server staff views a concession as an agreement between two Guilds when one of them recognizes that they broke an agreement and/or violated a raid rule. It is a first-line option that should be taken prior to and (hopefully) as an alternative to submitting a petition for a rule being violated. It is generally a better option for all involved, as a Guild who habitually refuses concessions that are deemed appropriate by server staff could eventually be held accountable for crying wolf.

The terms of those concessions are something that would need to be agreed upon by both Guilds as acceptable recompense for the situation. While there is pretty strong past precedence in terms of concessions, the server staff does not mandate specific concessions in specific scenarios.

Once a concession is offered and accepted, it's binding for BOTH Guilds. One of the Guilds agrees to bypass a number of kills of a certain mob or mobs, while the other agrees not to petition for the situation that drove the concession. If an extreme scenario arises where either Guild feels warranted backing out from this agreement, I would strongly recommend discussing it with the other Guild and reaching out to CSR prior to doing so. We could see this as a form of defrauding another player or Guild. In addition to the potential raid violation, it could be considered a PNP infraction.


A lot of you have questions as to crime & punishment; I hope to address that here: If a petition comes to the staff, the offending guild/party will have the loots removed (if they got the kill), and will be suspended from all raid targets for 7 days if found in violation (to be more in line with PNP violations). If a guild wastes the staffs time with false, trumped up, dishonest, or insincere petitions against other guilds, then the petitioning guild will receive the suspension. In addition to this, if the petitioning guild is found to be at fault, the loot will be destroyed and not awarded to anyone. In addition to that, individual blanket suspensions will also be applied (ie: suspended for training if caught training, etc). Habitual offenders of these rules will have their raid suspension time doubled each time they are suspended (counters will reset after 3 months without a suspension).


Any Raid petitions made after the date and time of this post will subject to the guidelines stated in this post.

Raid Behavior

From this forum post: [8].

The Project 1999 Staff are implementing the following changes regarding the behavior of our raid guilds. These updates are effective immediately.

Behavior

We expect raiding guilds - and especially their leadership - to behave in a way that reflects positively on the Project 1999 community. As some of our most senior players, they should be role models. However, we see these players acting in a way that doesn’t represent the server nor its playerbase. Project 1999 will never be a utopia - nor do we strive to. A certain amount of trash talking and banter is part of the game. However, what we’ve recently seen in screenshots, voice recordings and have witnessed has gone too far. If a player chooses not to represent themselves in a civil manner, please know that any discipline is potentially on the table, including blanket PNP violations, forced removal from a guild leadership role, or even suspension of your guild. Our jurisdiction for enforcing these policies will include any channel managed by the P99 staff, including in-game, p99 forums, p99 discord, or UN discord. While DMs through applications are not directly policed by p99 staff, we are often provided with transcripts and it doesn’t help our opinion of players. If you can’t figure out the difference between harmless banter and malicious attacks, you know where the door is.

Raid Petitions

The majority of petitions we processed recently were ridiculous overreactions and have forced us to take these next steps.

Raid petitions and responses are limited to 2 pages, font size 11.

Due to the number of raid petitions received from guilds that are deemed baseless in nature, an updated raid petition policy is now in effect. If we find a complaint to be out of line or an extreme overreaction, the petitioners themselves may be punished. If a history of such frivolous petitions are recognized, the guild’s leadership may be held accountable as a PNP violation. Please note that it is our intent to invoke this discipline more frequently than the current “crying wolf” policy. If your guild has ever submitted a raid petition which was thrown out (most have), we would recommend you take a closer look at your internal decisioning processes regarding what warrants escalation to the server staff.

Additional footnote for petition guidelines link [9].

Discipline Adjustment

The Raid Committee will now look at 7 day zone-specific suspensions or 7 day complete raid suspensions as the standard action taken against the guilty party. An individual PNP violation may also be applied to the players directly responsible for the infraction when applicable and at the discretion of staff.

Scripting and Third Party Software

We’ve had a large influx of reports on scripting and other third party software usage in competitive raiding. There are always accusations of cheating from and against every guild in the raid scene which are largely petty and knee-jerk reactions to something. The recent reports had enough information to warrant CSR investigating. We took action against multiple players in multiple guilds through our standard process for these petition types with the intent of stopping and deterring this behavior. If this type of behavior continues, we will implement methods similar to those used to detect exploiting in Sleeper’s Tomb a couple years ago. For those of you who were not around for that, the action taken against accounts were significantly more aggressive and extensive.

ToV Specific Rule

Due to the significant increase in train-related petitions within ToV, staff has implemented the following rule: 

If one raid force trains or wipes another raid force in ToV, they must concede the contested raid target and vacate the wing, less two trackers, before engaging any other raid target in the entire zone.

Regarding Q31, Staff’s view of concessions remains the same. This exception serves as a bare minimum requirement and all other rules and expectations still apply such as aiding the trained guild in recovering.

Q25 has been temporarily removed

Not ToV specific 

If a guild/party FTEs or engages a raid target, they may not FTE or engage a second raid target until the first one is dead or until 30 minutes has passed (this doesn't apply to triggered spawn targets that your guild triggered/spawned). Example: If your guild is in EJ and you have Sev incoming to your raid, but then Vulak pops, you are no longer allowed to just drop the Sev pull to go for Vulak. You must either kill Sev, or wait 30 minutes before FTEing a new target. The only thing this rule does is further force guilds to prioritize which targets they go after. It does not change any other aspect of raiding on the server.

Encounter Specific Rules

Temple of Veeshan

Plane of Sky

Rotation: There is currently a weekly rotation of guilds who raid sky. See the following threads for up to date info: [10].

Because of the special respawn mechanics of the Efreeti bosses, guilds raiding Sky agreed to the following:

YDYN.png

Kael & Dain

From this forum post: [11].

After a bit of discussion with players and staff, we’ve decided to take a different approach with naturally spawning major Kael targets and Dain Frostreaver IV.

The goal of this change is to reward the entity that can muster a kill force first. Don’t pull any target unless you are ready for it, stalling will be handled appropriately.

Training/trainouts will not be permitted. If you agro a mob outside of a normal split, you are required to kill it. Training mobs outside of their wings will be illegal. Raid rules still apply to training opposing forces. We do not want to see trains weaponized to block other raid force’s pullers. But if you choose to plant your raid force in the general pull path, you do so at your own risk. I.e. Vindi spawn area or ramps.

Statue/AoW and KT are required to be pulled and killed closer to their spawn points. Below are two maps, the yellow highlighted area is your designated pull and slay space. To be clear, no mob must leave their respective wing.

Statue/AoW

Galach kael 1.png
While we understand the general pull/puller path for AoW is not highlighted, that was intended. We do not want players stalling by running targets around in circles through other player’s raid force. You may use the un-highlighted area below arena(3) ONLY for the initial AoW pull.

King Tormax

Galach kael 2.png

Dain

After much discussion, we could not come up with a solution that would be competitive and fun for the players. We’re reverting back to the ruleset prior to the recent /random change. If anyone has any creative ideas, feel free to draft a proposal and submit it to the petitions / exploits forums.

Race will start in the Great Divide at the Thurgadin zone in. Anyone that is to FTE needs to start from this location. They will need to go through Thurgadin A, zone into Thurgadin B (Icewell Keep) before they can get an FTE. Anyone that is not part of the FTE may camp inside Icewell Keep.


Questions
What about on a quake? These rules don’t apply on quakes. You will be able to pull the target out of the restricted area. Please note that excessive kiting, wiping, not dropping your FTE, training and other PNP rules are still in effect.

Why stop the random roll rule set? The random roll rule set was put in place temporarily until staff was able to discuss and determine a fair playing ground to all.


Final thoughts
We as staff are few. You as players are many. If anyone has any well thought out ideas on how to mix up the Blue raid scene, we’ll listen. Please create a post on the petitions / exploits forums.

Tunare

Tunare's call needs to function. If a guild is doing something that de-links the call from Tunare entirely, that's not allowed.

You are allowed to bring the kite into a corner, then start to DPS tunare and have Tunare call bring mobs back. If you are doing something that straight makes the call not work, that will be punishable.

Galach tunare.png

Update from this forum post: [12].

Tunare’s call seems to be broken. Until we determine what exactly is breaking her call, any entity that wishes to kill Tunare, must clear the zone.

Edit 7/19/21: Charming mobs to assist in causing damage to Tunare is fine.

Edit 9/12/22: In its inception; the rationalization for the Tunare rule was to prevent players from training mobs, therefore, they would be required to clear PoG in order to engage Tunare. The utilization of charmed pets against Tunare is acceptable; however, those charmed pets must also be defeated as leaving them standing would violate the spirit of the guidelines governing the requirement to clear PoG.

Coldain Ring 10 Rolls

From forum post: [13].

Server Rule Details

  • The first 7 days of every month will be won by the first player to complete the turn-in. That turn-in must occur after Sentry Badain's has respawned from his original spawn position inside the hut to one of his updated locations. (Wording updated 5/3/2021)
  • Players will /random 1000 and the highest dice number roll wins.
  • Time limit to roll is 20 seconds from the first player roll, to prevent players from having the opportunity to switch to a second character and roll again.
  • Players must honor their roll and turn in themselves, within 5 minutes of Sentry Badain spawning.
  • The character who wins the roll must be the character to perform the turn in and loot the rewards.
  • Attacking, casting on, aggroing Sentry Badain or doing anything to disrupt this event will suffer consequences.
  • In the case of tie winning rolls, the involved players will /random 900, until a winner is decided.
  • In the event of an Earthquake/server reset, FFA rules.

Further Clarifications

These clarifications came from GM responses in the P99 UN Discord (screenshots below).

  • Q: Does Ring War count as an FTE lockout?
    • A: Ring War still counts as a raid lockout, so you cannot have FTE on a raid mob and roll for Ring 10.
  • Q: What happens if a winning roller doesn't have the force to complete a ring war, and foregoes their Ring War winning roll? Is this a violation of server rules by this character? Does that constitute a ring war failure by their respective guild? Will the Badain Turn in go to the 2nd highest roller?
    • A: This will count as a failed attempt, don't roll unless you are sure there's a force ready.
  • Q: What happens if a player with shit internet wins; can they appoint a representative to control the dwarves in their stead?
    • A: So we stand by our original statement, "The character who wins the roll must be the character to perform the turn in and loot the rewards." This line was intended for the initial turn in, not the "Commander" turn in. Anyone can do that portion since the "Commander" role is completely independent of the initial ring turn in and doesn't provide any monetary gain.
  • Q: What happens if only one person rolls, and doesn't turn in? FFA?
    • A: If there's only a single person that rolls, then there's no 2nd or 3rd party to verify it happened. So I would go with FFA, but don't feel like you can clickfest. To avoid any conflict I would wait at least 20 seconds after spawn to allow someone who may be a few seconds away to still take part in the roll if they make it in the technical roll window.

Menden ring10 question.png
Menden ring10 answer.png

Veeshan's Peak

From this forum post: [14].

When a dragon in VP spawns, anyone past the VP entrance Blue Pad may not assist their guild in any way. If another dragon spawns while the first one is still alive, this rule becomes void only to the players who were at the zone in pad before the first dragon spawned

No Call of the Hero allowed in VP Call of the Hero is only allowed to exit the zone. You are not allowed to use this ability to pull, drop aggro, recover corpses or anything else besides exiting the zone immediately. (09-04-20)

No Song of Highsun allowed in VP

Derakor the Vindicator

Derakor is now a raid mob[15], but we are allowed to continue clickfesting and pulling to the zone line as previously done so. "Him" in the below screenshot is refering to Vindi.
Vindi raid.png

Raid Rulings and GM Clarifications

These are raid rulings and GM clarifications from various locations.

Does AOW Lockout persist if the guild who killed statue pivots to another raid target?

They would still have the time limit to pull AOW. If they want to go after another target really quick & risk not being prepared, that's their own choice.

Galach aow.png

Pathing Bugs

From these forum posts: [16] [17].

On 02/25/21, Vanquish engaged The Statue of Rallos Zek. During this pull, Statue became stuck due to a well-known pathing bug. While stuck, a member of Vanquish cast a debuff on the target.

Freedom/AG (now Vanquish) previously submitted a petition against Riot for a very similar situation. In both cases, The Statue of Rallos Zek became bugged on terrain and players exploited the situation by debuffing. When we issued the previous suspension, players were warned not to debuff raid mobs stuck due to pathing.

If you are dealing with a stuck raid mob, please do not cast any debuffs on it. We consider this an exploit. Examples of debuff spells include Malo/Malosini/Tash/OOS, et al.

This has occurred twice in recent history. Punishments may be severely increased if we see this kind of behavior; exploiting bugs is not something we take lightly.

Exploits

From this forum post: [18].

Azure Guard, Kittens Who Say Meow, RenamedGuild, and Riot are under Raid Suspension from All Raid Content starting immediately, and ending at 12:01 AM Saturday, May 2nd.

It has been found that these guilds have benefited from a file manipulation exploit that their members have used in Sleeper's Tomb to divulge the weapons that mobs are wielding visually.

Let me be clear that the staff considers modifying the contents of your EverQuest folder to gain an advantage such as this to be almost as serious as actively hacking the client. It will not be tolerated. All of the characters that were abusing this have been suspended until May 25th.

Temple of Veeshan Vacating

From this forum post: [19]. 

All current raid rules will remain in effect in ToV. This means that your raid force must not have a presence in that raid mob's wing when it spawns. If you are in a wing clearing to one mob and another spawns, you may still kill the original

target mob but then your entire raid force must vacate the wing before re-clearing to the new raid mob. Yes, that means chose your raid mobs carefully if there are other mobs in window.

The staff has received some questions regarding the quoted part here and requested clarification. Our intent behind this rule was that players cannot engage a raid mob which spawned in a wing while they were present. This means it is not required for players to vacate if they have no intention of participating in a fight on a raid mob which spawned while they were in the same wing. In other words, guilds may chose to leave players behind while others clear out (Evac, Gate, etc) and return to fight a newly spawned raid mob. The players staying behind must not assist whatsoever. This means no healing, no buffing, and not even being near the fight at all.

Lull Pulling

From this forum post: [20].

Lull pulling is not allowed on any raid target.

Counting Seconds

From this forum post: [21].

Counting seconds is another example of a petty petition we do not want to see moving forward.

Necro Pets on Naggy/Vox

You can't fd & send a necro pet in. We ruled that in the past on red.

Galach naggy.png

Double FTEs

I don't see where, but I saw I was pinged yesterday regarding multiple FTE's. Again, it's situational and fluid based upon circumstances. If you were COTH'ing a FTE team down to engage Zlandi while killing another raid mob that would be something you would need to concede. Especially if you were contesting another guild that was setting up themselves. The double FTE's that don't count would be truly accidents, social aggro from other mobs, running across zones, afk players etc. Not competitive actions.

Galach double-ftes.png

Dozekar COTH Race

FTE needs to run from entrance. Cannot be COTH'd

Galach doze.png

Vox Zone Pulling

So, I just wanted to ask you directly for moving forward in the future: is Vox 'legal' to pull to zoneline, or must you clear and engage in her lair?

Vox should be fought in the lair. - Ambrogio

Vox pull.png

Killing Conceded Mobs

So maybe answer the other question: What is the proper concession for killing a conceded mob?

2x concession - Visceryn

Kill concede.png

GM Ruling Concessions

In the future just so we are all clear, all raid petition concessions will be naturally spawning.

Gm-ruling-concession.png

Player Agreements

Player agreements made by top raiding guilds in order to avoid GMs making rulings or clarifications on specific rules.

Golem Racing

From Discord post [22]. This is a player agreement that all guilds must agree to to continue existing.

The final set of Golems before CT spawn will be left up by agreed guilds until 2 of the 3 Golems are spawned. 2 guilds who can compete during the window will set a start time after the spawn of the 2nd golem. At the Start time the 2 guilds will have an agreed amount of time to gather and prepare. The 2 guilds will gather in front of the PoF portal and have a good faith race to kill the First Golem. Be sure to have a zone wide count down for when to zone into PoF and keep it honest. Who ever kills the first Golem will also get a 3rd golem uncontested when it spawns. Both guilds will get atleast 1 golem kill.

The Rotation

Guilds will Rotate cycles until each guild has participated in an equal amount of cycles. If a cycle falls in a time frame where you wont compete you pass. Passing once will not count against your participation count. Passing 2 times will count as participating and the guilds will start over on rotating as if you competed for that 2nd passed cycle.

Every 2nd Cycle of Golem spawns after CT guilds who agree will NOT:
1. Kill any of the 3 Final spawned Golems before the agreed Starting time.
2. Have any member of agreed guild participate in any way on alts or unguilded toons in killing any of the 3 golems.

Every 2nd Cycle of Golem spawns after CT guilds who agree WILL:

1. Agree to set a Start time based off of the time the 2nd golem spawns.
2. Be ready to port in and race for the first kill within an agreed amount of time after the start time.
3. Help recover/rez any guild that dies/wipes after the first golem is dead.
4. Acknowledge that all other raid rules per the Server rules are in agreement.
5. Share spawn times and start times in the UN.
6. Pass on windows that will be outside your kill time in a timely manner so the other guilds may plan.

Golem racing.png

Rod of Drones

Riot and Vanquish are removing rods of drones from FTE races. If any other guilds start racing, maybe we'll reconsider this? idk. GL

Furoar drones.png

Removed Raid Rules

These are previously existing rules that have been since cancelled and are unlikely to return. If they are no longer around for a while, this area will be removed.

Bag Limits removed from this post [23].

Bag Limits

From this forum post: [24] and 2/3 limit updated to 4/5 on this post [25].

Due to the number of issues we’ve had over the past few months with raids in the Temple of Veeshan, we will be implementing some policy updates. While we do want to continue to encourage competition, we also believe that a portion of the toxicity we’ve been dealing with is a result of some guilds contesting every spawn, every time.

Effective immediately, we will be shifting to a 2/3 4/5 system for kills in the Temple of Veeshan, with the following ruleset:

We appreciate your cooperation and understanding as we continue to work through tactics to try and improve the P99 Blue experience for the population, and we look forward to reviewing the impact these changes have and making further adjustments, as needed, in the future.


Are quakes included in the "you cannot contest until [x] hours" rule, or do they remain FFA, and do quake kills count towards the 2/3 4/5 count?
They are counted towards the 2/3 4/5 count.

Guild kills 2/3 4/5 and spawn is uncontested for the set amount of time. If Guild kills the new spawn, does the 2/3 4/5 reset, or are they expected to wait [x] time again?</br> Once you serve the lockout, you are done. If you kill a target twice, get locked out and kill the target after the lockout is over, you would be back at 1/3 and would be eligible to kill the next spawn.

Bag Limit Concessions/Suspensions

Can you please confirm if bag limit status freezes upon concessions and suspensions?

  • If you kill 2 and then concede the next mob, that does not count as a resetting your bag limit, correct?
  • If you're CSR suspended from a mob, that pauses your current kill count on a target?

Correct - Galach

Galach bag concessions.png

Retrieved from "https://wiki.project1999.com/index.php?title=Blue_Raid_Rules&oldid=393287"