Project 1999

Go Back   Project 1999 > Blue Community > Blue Raid Discussion

Closed Thread
 
Thread Tools Display Modes
  #1  
Old 07-02-2023, 04:55 PM
Ambrogio Ambrogio is offline
Senior Server Guide

Ambrogio's Avatar

Join Date: Jun 2021
Posts: 5,709
Default Project 1999 Raid Rules FAQ

Project 1999 Raid Rules FAQ
(updated 2/8/24)

Quote:
In addition to our main Discord Server, we have UN channels that were designed for guilds and their leadership to discuss and, ideally, resolve raid disputes before they are submitted for CSR Staff mediation. The permalink links to those servers are below:

Blue UN: https://discord.gg/TqmEFZwxUv
Green UN: https://discord.gg/GDMhcNDWb2
Red UN: https://discord.gg/8Xp3gvtmSA

The following raid rules are in addition to the expectations contained in our Play Nice Policy: https://www.project1999.com/forums/s...d.php?t=325349

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. Project 1999 will never be a utopia - nor do we strive for that goal. 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.

New Guilds

If you are leading a guild that is not in the UN and you want to participate in the draft, please join the UN and message CSR to be tagged as such.

A drafting entity is defined as a guild or alliance of guilds that has, without outside help and, in order to participate in the draft, guilds and/or guild alliances must qualify based on the following criteria:
A) Killed Derakor the Vindicator within 2 months of the draft lockout date

AND

B) Killed one of the following: Wuoshi, Velketor, Queen Bee, Hoshkar, Nexona, Inny, Dain, KT, Sev, Talendor, Trak, or any inner ring ToV dragon within 2 months of the draft lockout date

AND

C) Has been a raiding entity for at least 3 months or a merger including at least one qualifying drafting entity.

OR

D) Killed ALL of their selected targets in the prior draft
CSR remains the ultimate decider of who can and cannot participate.
Quote:
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 NPCs 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 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 a mistake was made, take responsibility and accountability for what transpired and work with the other involved guild(s) for an amicable resolution. Conceding a mob should not be mistaken for weakness or inadequacy. It is a powerful tool that, if used properly, can highlight strengths in leadership and also the willingness to correct a misstep with the ultimate goal being conflict resolution.

Q4: If we feel another guild/party is breaking raid rules what actions may we take?
A: It is always preferred to reach resolution with the other involved party either in-game or in the appropriate discord UN channel. A raid petition should be the absolute last-resort.

Q5: What about in cases where the mob dies before anyone is sure who is at fault?
A: See Q4.

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 their guild’s disputes, submit a raid petition in the appropriate P99 Discord UN server. Please limit raid petitions and responses to 2 pages, font size 11. Equally important is the use of clear formatting, cohesive sentences, and paragraphs. A full and detailed description of the event must be submitted. If a video is included to support a raid petition and is more than a couple minutes in length, please include important timestamps. 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. These negotiations can be included in the video or as screenshots.
Note on Meritless Petitions – If a raid petition is submitted, especially those deemed frivolous by CSR Staff, disciplinary options may include but not be limited to full week suspensions from an area, zone, or the entire server’s raid content.

Note on Rule Lawyering/Lawyer-Questing – Please do not engage in behavior designed to interpret or alter our rules in order to support and/or justify nefarious actions as those 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 circumvent a raid suspension on a loop hole or technicality.
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 (FTE).
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 by obtaining a fresh FTE message. 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 communicating 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. We want 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. 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: 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 disqualified (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: 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.

Q18: What if I have a legitimate complaint against a Staff member?
A: Any complaints against a Staff member should be sent to Menden via a private message on the Project 1999 forums. Any complaints against Menden 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.

Q19: 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 have 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.

Q20: 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.

Q21: What exactly is off limits during a Raid Suspension?
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. PoM is permitted, as long as you are bound there.
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.
Q22: 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.

Q23: What exactly does the staff consider a Raid mob?
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).

Q24: 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.

Q25: Where are the starting lines for FTE racers?
A: See specific encounter and raid target rules below.
Dain Frostreaver IV: 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.
Faydedar: On the island with the Ogre camp (#1 on wiki map).
Gorenaire: At the druid rings.
Kael Drakkel: Behind the ice/snow line at the Wakening Lands zone line.
Kelorek`Dar: At the zone in rings or Siren's Grotto zone line.
Lady Vox: Before the ladder at the zone in.
Lord Nagafen: In the entrance tunnel from Lavastorm.
Lord Yelinak: At the fountain to Cobalt Scar or Wakening Lands zone line.
Severilous: At the Field of Bone or Trakanon's Teeth zone lines.
Sleeper's Tomb: Behind the entrance door.
Talendor: At the Burning Woods or Overthere zone lines.
Temple of Veeshan: Behind the bottom step just past the entrance door.
Trakanon: At the zone in.
Veeshan's Peak: On the blue entrance pad.
Venril Sathir: The hallway between the entrance zone lines.
Zlandicar: Behind the zone-in portal.
---
Plane of Fear: At the PoF portal in Feerrott.
Plane of Hate: Anywhere not in Hate unless actively clearing with a raid force.

Q26: 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.

Q27: What can a tracker do?
Trackers are for tracking. They cannot kite, pull, DPS, heal, buff 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.
The Two Tracker Rule Explained:
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 that 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).

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 and or heal any players that are part of the encounter.

Q28: What is a concession? Are there any specific rules around concessions?
Player autonomy is of significant importance and CSR Staff would prefer our player base utilize civil communication for conflict resolution as our involvement should only be requested for a last-resort effort. As much as we are called upon to intervene, due diligence is also expected from all involved parties to settle differences amongst themselves. CSR intervention could yield, at best, a win-lose scenario or, conversely, a lose-lose outcome.

EverQuest is an incredibly social experience, regularly eliciting some degree of communication, especially during disagreements. In terms of raiding disputes, players possess a variety of options in order to provide desired, timely, resolutions on their own. For example, guilds have agreed upon some of the following:
  • In-game currency or DKP
  • Recovery assistance
  • Server wide concessions
  • Providing additional opportunities to engage the raid’s target(s)

The aforementioned selections are neither limited to nor all-inclusive of all available possibilities during remediation discussions. From our perspective, they are agreements between guild leaders, are binding, and may be enforced by CSR Staff.

If an agreement is breached, guild leaders will be considered defrauding the other party. As a reminder, defrauding other players and/or Staff is a violation of guidelines in our Play Nice Policy. Guild leaders found breaking an agreement may earn disciplinary action against every member of that guild's leadership, regardless of their presence at the encounter. The server GM will decide which account(s) to apply suspensions and/or bans.

If a raid petition is submitted, especially those deemed frivolous by CSR Staff, disciplinary options may include but not be limited to full week suspensions from an area, zone, or the entire server’s raid content.

Please do not allow a refusal to engage in civil communication and/or other violations culminate in actions that could affect the playability of guild leader accounts and/or their guild's participation in server content.

Conceding three natural spawns of a target after killing it is considered standard. Conceding more or less is acceptable if agreed on by players.

ToV Specific 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.\

Training and/or harming another guild in any zone:
It is expected the guild at fault will do everything reasonably within their power to recover the other guild. Including, but not limited to: rezzing, buffing, and twitching players.

Memory Blur and the Lull Spell Line in Raiding:
The use of Memory Blur, or any spell with this effect, is strictly prohibited on raid targets. If a player lands this spell on a raid target, their guild must drop the raid target and let it completely reset. If a player lands Memory Blur on a raid target while another guild has FTE, their guild must concede the raid target. "Lull pulling" raid targets through walls is prohibited. Certain instances may be allowed at the sole discretion of P99 staff.

Q29: What if I witness or have information about a pathing exploit?
A: If you witness, discover, or hear of an exploit it becomes your responsibility to report it in the forum’s Petition / Exploit thread. Some exploits include but may not be limited to monetary gain from improperly dropping loot, pathing exploits allowing avoidance from being harmed by and easy dispatching of NPCs, and quest abuse that depends on deceptive tactics in gaining an improper amount of experience that also includes repetitious generating of quest items. We ask for everyone’s cooperation in this matter. It is important for us to correct these behaviors as quickly as possible.

Quote:
Encounter Guidelines
Last Updated: 7/2/23


Key Terms:
Translocate Allotment - ex) COTH/ABSCOND/Gate/REZ BOX/SUCCOR
Run Speed Consideration(s) - ex) SoW, SELO’s, Bard Speed, Spirit of Cheetah
Location of Engagement - ex) Start Line, Pull Spot, Fighting Area/Kill Area

Old World

Phinigel Autropos
Zone: Kedge Keep
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: With the release of Velious on both servers, this mob can be claimed as a camp if the players are consistently holding down the room, area, and/or guards.

Noble Dojorn
Zone: Plane of Sky
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement: Isle 1.5 Plane of Sky
Additional Rule Consideration: Blue and Green each have player agreements in place on this mob. Please see your server’s UN Discord server or ask your guild’s leadership for details.

Lord Nagafen
Zone: Nagafen’s Lair
Translocate Allotment: No COTH.
Run Speed Consideration(s): SoW max.
Location of Engagement: In lair.
Additional Rule Consideration:
Additional Notes: If you are XP’ing in zone, you must physically zone out before helping at all with the engage.

Lady Vox
Zone: Permafrost
Translocate Allotment: No FTE COTH, but COTHing raid force outside of lair allowed.
Run Speed Consideration(s): SoW max.
Location of Engagement: Must be fought in the lair.
Additional Rule Consideration: FTE must be from someone running from zone in.
Additional Notes: If you are XP’ing in zone, you must physically zone out before helping at all with the engage

Plane of Hate Mini Bosses, Maestro of Rancor, and Innoruuk
Zone: Plane of Hate
Translocate Allotment: No COTH
Run Speed Consideration(s):
Location of Engagement: May pull to entrance.
Additional Rule Consideration:
Additional Notes:
- You must port up after any of these mobs have spawned.
- If you were in the zone before any of these mobs spawned, you must leave the zone and come back.
- If you are actively clearing hate trash and/or a Mini spawns as part of a Plane of Hate guild raid you don't have to port down and back up.
- Dying and resurrecting does not meet these requirements. Example: you cannot die at the fountain/stairs safe spot, get ressed by a cleric who was camped out there, and come back into the zone.

Dracoliche
Zone: Plane of Fear
Translocate Allotment: Not allowed
Run Speed Consideration(s): Can use bard speed.
Location of Engagement: Must be pulled directly to camp.
Additional Rule Consideration:
Additional Note: Can’t be in zone & engage if he spawns. Everyone must vacate the zone & re-enter unless they are a tracker (max of 2).

Cazic Thule
Zone: Plane of Fear
Translocate Allotment: None allowed
Run Speed Consideration(s): Can use bard speed.
Location of Engagement: Must be pulled directly to camp.
Can’t be in-zone & engage if he spawns. Everyone must vacate the zone & re-enter unless they are a tracker (max of 2). All trash mobs, within reason, must be pulled directly to camp if CT’s call mechanic is broken.

Dread, Fright, Terror
Zone: Plane of Fear
Translocate Allotment: Not allowed
Run Speed Consideration(s): Can use Bard speed.
Location of Engagement: Pull directly to camp
Additional Rule Consideration:
Additional Notes: Your entire raid force must vacate the zone before engaging with the exception of your 2 max trackers. Those trackers may not assist at all with the pull or engage.

Plane of Sky
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: Gwan kills and Thunder Spirit Princess quest turn-ins only on your guild's assigned Sky day unless another guild gives you permission.
Additional Notes: Sky dates are determined in each servers' UN Discord servers.

Ragefire
Zone: Nagafen’s Lair
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes: Whoever turns in "Shimmering Pearl" to Zordak Ragefire has 20 minutes to engage Zordakalicus Ragefire, after 20 minutes has elapsed, it goes FFA.


Kunark Era


Venril Sathir
Zone: Karnor’s Castle
Translocate Allotment: Not allowed.
Run Speed Consideration(s): SoW
Location of Engagement: Must kill in his lair or the room right outside of it.
Additional Rule Consideration:
Additional Notes: Able to XP in zone during window, but anyone past zone line must zone out if they are XPing (ex: rogues can’t sneak down from their xp camp or people can’t get coth’d if they are XPing before zoning out).

Trakanon
Zone: Old Sebilis
Translocate Allotment: Able to COTH to “poopsock” mountain. 2 tracker max, can both be mages. Can’t camp/log in at the hill (Poop Mountain).
Run Speed Consideration(s): Bard speed allowed.
Location of Engagement: In lair.
Start line: Zone in.
Additional Rule Consideration: Able to XP in zone during window, but anyone past zone line must zone out if they are XPing (ex: rogues can’t sneak down from their xp camp or people can’t get coth’d if they are XPing before zoning out). Training poopsock mountain on wipe is an automatic concede.

Faydedar
Zone: Timorous Deep
Translocate Allotment: Not allowed.
Run Speed Consideration(s): Bard speed ok
Location of Engagement:
Start line: On the island with the Ogre camp (#1 on wiki map).
Must pull with your FTE & not kite.
Additional Rule Consideration:

Talendor
Zone:Skyfire Mountains
Translocate Allotment: Not allowed
Run Speed Consideration(s): Spirit of Wolf Maximum Speed
Location of Engagement:
Start line: At the Burning Woods or Overthere zone lines.
Must pull with your FTE & not kite
Additional Rule Consideration:
Additional Notes:

Gorenaire
Zone: Dreadlands
Translocate Allotment: No COTH
Run Speed Consideration(s): Selos max run speed.
Location of Engagement:
Start line: At the druid rings. After 5 minutes, anyone can FTE.
Additional Rule Consideration: Unlimited racers. Levitate required on racers.
Additional Notes:

Severilous
Zone: Emerald Jungle
Translocate Allotment: No COTH
Run Speed Consideration(s): Spirit of the Wolf max run speed.
Location of Engagement:
Start line: At the Field of Bone zone line (see blue start line).
Additional Rule Consideration: Unlimited racers. Levitate required on racers.
Additional Notes:

Veeshan’s Peak
Targets:
Druushk
Hoshkar
Nexona
Phara Dar
Silverwing
Xygoz
Zone: Veeshan’s Peak
Translocate Allotment: COTH can only be used to zone out.

Run Speed Consideration(s): Bard speed.
Location of Engagement:
Start line: Blue pad
Must pull with your FTE & not kite
Additional Rule Consideration: Must drop your pull if it goes past the bridge towards Hoshkar lair. https://www.project1999.com/forums/s...d.php?t=191682

Velious Era


Derakor the Vindicator*
Zone: Kael
Translocate Allotment:
Run Speed Consideration(s): Spirit of the Wolf max run speed.
Location of Engagement:
Additional Rule Consideration: For the first months of Velious, Vindi will be a FTE race from Wakening Land. You may have your raid in the arena farming giants, but may not FTE Vindi unless your racers are in Wakening land. This is due to past experiences on Blue where there were nightly issues. DO NOT FTE AND KITE UNTIL YOUR RAID FORCE SHOWS UP. YOU NEED TO PULL TO YOUR CAMP IMMEDIATELY OR DROP THE PULL.
Additional Notes: Vindi is a constant source of contention, expect these rules to change every now and then. Generally viewed as somewhere between a raid target and a high tier target.
May camp at his spawn, FTE rules.
May pull to either zone line.
Standard raid target FTE rules apply.

King Tormax
Zone: Kael
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:
  1. May be killed at any chosen location.
  2. All trackers must be members of an eligible raiding entity, with a visible guild tag.
  3. COTH FTE is permitted, but a mage tracker may not be logged in at the time of a raid target’s initial spawn.
  4. In the occurrence of a quake, any mage, near a raid target, must immediately gate to avoid a penalty for their guild.
  5. All rule details and enforcement, including number of concessions and additional punishments, are at the sole discretion of Project 1999 staff.

Statue of Rallos Zek / Avatar of War
Zone: Kael
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
The guild who kills The Statue of Rallos Zek locks out all other guilds from engaging The Avatar of War for 20 minutes from Statue's time of death.
The guild who kills Statue may not engage or obtain an FTE on another raid mob during this 20 minute period unless AoW is killed or conceded.
Additional Notes:
  1. May be killed at any chosen location.
  2. All trackers must be members of an eligible raiding entity, with a visible guild tag.
  3. COTH FTE is permitted, but a mage tracker may not be logged in at the time of a raid target’s initial spawn.
  4. In the occurrence of a quake, any mage, near a raid target, must immediately gate to avoid a penalty for their guild.
  5. All rule details and enforcement, including number of concessions and additional punishments, are at the sole discretion of Project 1999 staff.

Dain Frostreaver IV
Zone: Icewell
Translocate Allotment: No COTH
Run Speed Consideration(s): Spirit of the Wolf max run speed.
Location of Engagement: Anywhere in the zone.
Additional Rule Consideration: Race line in Great Divide. Unlimited racers. Levitate required on racers.
Additional Notes:https://www.project1999.com/forums/s...d.php?t=401140

Guardian Kozzalym
Zone: Western Wastes
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: First To Engage (yellow, zone-wide text). Able to camp at spawn.
Additional Notes: High tier mob.

Keldor Dek'Torek
Zone: Kael
Translocate Allotment: No COTH
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: Engage on spawn.
Additional Notes: High tier mob.

Kelorek`Dar
Zone: Cobalt Scar
Translocate Allotment: No COTH
Run Speed Consideration(s): Spirit of the Wolf max run speed.
Location of Engagement:
Additional Rule Consideration: Race from Druid port-in.
Additional Notes:

Klandicar
Zone: Western Wastes
Translocate Allotment: No COTH
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: Able to kite & disengage to land slow.
Additional Notes:

Lord Yelinak
Zone: SkyShrine
Translocate Allotment: 2x tracker (COTH Mage).
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: Able to COTH your engage force up.
Green Server only - Must get Yelinak to 97% within 1 minute of engage. If you don't, you must drop your engage and wait 3 minutes once dropped to try again.
Additional Notes:

Tunare
Zone: Plane of Growth
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Green - First guild to kill Guardian of Takish gets 24 hours to kill Tunare.
Blue - First guild to kill Guardian of Takish gets 12 hours to kill Tunare
Additional Notes: https://www.project1999.com/forums/s...d.php?t=413864

Vaniki
Zone: Dragon Necropolis
Translocate Allotment: No COTH.
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: Similar rules to Lodizal. Must engage in a reasonable amount of time.
Additional Notes: High tier mob.

Lodizal
Zone: Iceclad
Translocate Allotment:
Run Speed Consideration(s): .
Location of Engagement:
Additional Rule Consideration: Excessive kiting, not engaging or kiting after death will result in PNP violations. 5 minutes max to stop kite & engage after FTE.
Additional Notes: High tier mob.

Vilefang
Zone: Dragon Necropolis
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes: High tier mob. This mob can be claimed as a camp if the players are consistently holding down the room, area, and/or guards.

Velketor The Sorcerer
Zone: Velketor's Labyrinth
Translocate Allotment: COTH allowed.
Run Speed Consideration(s): SOW Max Speed
Location of Engagement: Must be killed somewhere in the castle including the “secret” tunnel and can’t pull to zoneline.
Additional Rule Consideration:
Additional Notes:

Wuoshi
Zone: Wakening Land
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Zlandicar
Zone: Dragon Necropolis
Translocate Allotment: COTH allowed.
Run Speed Consideration(s):
Location of Engagement: In his lair
Additional Rule Consideration: Green Server only -Must get Zlandicar to 97% within 1 minute. If not, you must drop engage & wait 3 minutes to engage again.
Additional Notes:

Sleeper's Tomb
Zone:
Translocate Allotment:
Run Speed Consideration(s): SoW
Location of Engagement: Anywhere.
Additional Rule Consideration: Master of the Guard and the Progenitor are foot races. Start line is behind the double doors at the zone-in.
Guilds may COTH down to the tunnel leading up to The Final Arbiter.
Additional Notes:

The Temple of Veeshan


General rules:
-COTHing throughout the zone is allowed.

-If one raid force trains or wipes another raid force in ToV, they must concede the contested raid target and vacate the wing before engaging another target.

Must leave the wing entirely, less two trackers, when a raid target spawns in that wing.

Aaryonar
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Cekenar
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Dagarn the Destroyer
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Eashen of the Sky
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Ikatiar the Venom
Zone:
Translocate Allotment: No COTH.
Run Speed Consideration(s): SOW max Speed
Location of Engagement: FTE must come from racers from TOV entrance.
Additional Rule Consideration:
Additional Notes: Able to pull to zone.

Jorlleag
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Lady Mirenilla
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Lady Nevederia
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Lord Feshlak
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Lord Koi'Doken
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Lord Kreizenn
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Lord Vyemm
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Sevalak
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Vulak`Aerr
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes: After a Vulak Blocker dies, everyone contesting Vulak must vacate north. A 10 minute timer begins at the death of the blocker. After 10 minutes has lapsed, CoTH’s can occur again.

The death of the blocker should be announced in /shout for all competitive guilds to be put on notice, with an accompanying time.
This only applies to the last blocker.

Zlexak
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Dozekar the Cursed
Zone:
Translocate Allotment: Able to COTH engage force, but not FTE racers.
Run Speed Consideration(s): SOW Max Speed
Location of Engagement:
Additional Rule Consideration: FTE must come from racers from TOV entrance.
Green Server only -Must get to 97% within 1 minute of FTE, otherwise must drop pull & wait at least 3 minutes.
Additional Notes:

Gozzrem
Zone:
Translocate Allotment: No COTH
Run Speed Consideration(s): SOW Max Speed
Location of Engagement: FTE must come from racers from TOV entrance.
Additional Rule Consideration: Able to pull to zone, SOW max speed on FTE.
Additional Notes:

Lendiniara the Keeper
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:

Telkorenar
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:
Quote:
Server Staff Enforced Scout Roll


Scout Roll ( https://wiki.project1999.com/Leuz%27s_Task) Winner must be the one to do the turn-in & loot broken disc. Green Server only: level 55 minimum requirement to roll.

Checklist
  • Talk to Commander Leuz to receive Scout Tools (requires amiable faction or higher. If you don't have amiable faction you cannot complete the quest and will agro and train Scout/Dragons to the others at turn-in).
  • Give Scout Tools to Scout Charisa (v1) (to spawn a Kromzek Captain, several giants, and Scout Charisa v2)
  • Loot Broken Disk from Kromzek Captain
  • Give Broken Disk to Charisa v2 (to receive Scout Report & Robe of Benevolence)
  • OPTIONAL: Return the Robe to Charisa v2 (to receive Bracer of Benevolence)
  • OPTIONAL: Return the Bracer to Charisa v2 (to receive Talisman of Benevolence)
  • OPTIONAL: Give Scout Report to Commander Leuz (to receive faction & experience)
Quote:
Server Staff Enforced Coldain Ring 10 Roll

As of 3/30/2021 the server staff are enforcing a server rule regarding the Sentry Badain turn in for Coldain Ring 10.[1]
See details of quest here: 10th Coldain Ring Quest
See details about the actual ring war here: Coldain Ring War
Quote:
Coldain Ring 8 Roll Player Agreement


The quest to acquire the eighth Coldain ring (Velium Coldain Insignia Ring) involves a significant scaling bottleneck wherein one player must trigger (and succeed at winning) an event, enabling the next step in the quest. The respawn timer for the triggering mob is 24 hours, essentially meaning one player may attempt this step in the quest each day. Due to this bottleneck, a roll has been established at which interested players will roll and the winner of the roll is the player that gets to make the attempt. Hence: the ring 8 roll. Below are details of the player-made agreement governing the roll and event attempt.

Since the encounter can be difficult, the roll happens earlier than the triggering spawn appears in order for the winning player to recruit help and for that help to arrive. The winning player should turn-in to the triggering mob immediately upon spawning, otherwise the turn-in time will shift later and later.

Players generally keep track of the exact spawn and turn-in timers. This is not updated by Staff.
Quote:
Blue and Green Agreement Details

  • The ring 8 roll time will be established the day after an earthquake by those present, approximately a half hour before the time of the quake. The roll will remain at that time until the next earthquake.*
  • Players will /random 1000 and the highest dice number roll wins.
  • Time limit to roll is 30 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 2 minutes of Gloradin spawning. After that point any player present may turn in to trigger the encounter.
  • The player who wins the roll must also loot Chief Ry`Gorr's Head. Winning the roll to sell ring 8 MQ is against this agreement.
  • Turning in, or looting Chief Ry`Gorr's Head if NOT roll winner will be petitioned, as per the current player agreement (to be handled by GMs)
  • Attacking, casting on, or aggroing Gloradin will be petitioned, as per the current player agreement (to be handled by GMs)
  • In the case of tie winning rolls, the involved players will /random 1000 again, until a winner is decided.
  • In the case of Daylight Savings, the ring roll shall be moved by 1 hour to maintain the integrity of the Roll to Gloradin spawn timer. The roll time/spawn time above should be updated by 1 hour to reflect this change.
Quote:
Blue Server Specific Rules


Badain and the Ring War
  • 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

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 a bad internet connection 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 spawning 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.

Rewards
These rewards are assuming the series of turn-ins are completed correctly.
  • Ring of Dain Frostreaver IV (for the winner of the roll)
  • Protection of the Dain (for the winner of the roll)
  • Crown of Narandi
  • Eye of Narandi
  • Earring of the Frozen Skull
  • Faceguard of Bentos the Hero
  • Choker of the Wretched
Quote:
Red Server

Recent Policy Confusion & Clarifications

P99 Red Community,
We’ve recently responded to a number of situations that have been the result of some truly toxic behavior. In light of that, we wanted to take a moment to provide clarification on some of the rules that seem to have “creative” interpretations from some of the players involved. Although none of these are new policies, we wanted to provide this clarification in writing.

We absolutely want PvP to reign supreme on P99 Red. However, “PvP” is NOT an excuse to break other rules that are defined in the Play Nice Policy.

Most notably, intentionally causing experience-loss to other players in the PvP environment is illegal in all cases. This INCLUDES:
  • Dispelling mobs that are currently attacking another player(s) - You are welcome to use dispells while engaging other players in PvP. However, the target of those dispells MUST be the other players. Dispelling the mobs that are currently engaged with the intent to remove debuffs is considered an attempt at intentionally causing experience loss.
  • Training other players - If you wish to PvP other players while they are engaging a mob, whether that is in a raid setting or a group setting, you must ensure that you are not bringing a train with you prior to entering the area of the other players. You are responsible for your own agro, and if you pass that agro off to others incorrectly, you are subject to violations as set forth in the Play Nice Policy for zone disruption as well as causing experience death.

We are hopeful that the above clarifications will help curb this behavior. Please be aware that until we see this issue reduced overall, the server staff has been asked to handle confirmed situations of the above more severely than we have in the past. Due to the number of accounts many players on P99 Red have access to, this toxic behavior will be handled at a blanket level, up to and including blanket bans.


Red Server Specific PnP Rules (Loot and Scoot)


All of the rules stated in the Project 1999 Play Nice Policy still apply to Project 1999 Red PvP, with the following exceptions:

The PvP Servers are a special case for many of the policies listed here. When one makes the decision to play on a PvP Server, they are in essence agreeing to play on a server where compromise is decided on the basis of who has the power to kill whom.

By the same token, we expect that the people on those servers will apply PvP combat in all situations where it is called for, as a resolution to the problem. As such, the Project 1999 Customer Service Staff will decline to intervene in cases where a PvP alternative exists, such as at disputed spawns where the parties involved have the ability to attack each other.

Please note that this means that kill stealing is still against the rules on Project 1999 Red. If you wish to steal someone's kill, it is recommended you kill the player first and then kill their mob.

Though the PvP environment does eliminate a few of the problems experienced on the normal blue server, there are a few more PvP-specific problems that are created.

Causing Experience Loss.

Intentionally causing experience-loss to other players in the PvP environment is illegal in all cases and may result in disciplinary action when witnessed by a P99CSR. This includes things such as intentionally training NPCs and dispelling mobs that another player is engaged in. We do understand that there are cases where the experience-loss is unintentional, and no disciplinary action will be taken in those cases.

Much like how the Kill Stealing rule applies to those on the blue servers, this rule is designed to discourage and make note of those who do it habitually, thus betraying the spirit of PvP. This is one of the dangers of playing on a PvP server.

To encourage more actual PvP combat and less just griefing each other, and due to the previous standard of a couple players interfering with a raid target while having no actual raid or PvP force present in game to contest or kill, we have added this rule:

"A player that interferes with a raid target with no raid force present to kill or contest the target is against the rules and will be addressed swiftly."

A Raid Force is 12 or more players - Again we are talking about the RAID TARGET, if you only have a couple of players and want to attack players that's fine, but you can't interfere with the raid target unless you have a RAID FORCE

This above rule may be revisited at a later date to adjust if needed.

Also, guilds will be held accountable for their members' actions. We are adding this to deter the constant trains and griefing that has gone on in the past.

Example: If Guild A is engaged on a raid target, and a player from Guild B trains Guild A on purpose, Guild B will be held accountable for that train.

Bind-point/Corpse Camping and Loot and Scoot (LnS)

Killing someone over and over again while at his or her bind-point or while they are in the process of looting and scooting is illegal and may result in disciplinary action taken against your account.

Conversely, the person recovering their corpse is expected to do so and retreat to safety promptly. In other words, sitting next to your corpse and taunting someone while daring them to attack you so that you can /petition them is bad form, and may result in disciplinary action taken against your account.

A player is 'Looting and Scooting' (LnSing) when he has died to an opponent and opts to call Loot and Scoot. You must make your intentions clear that you are looting and scooting by communicating with the other people in the zone(s) you move through, as well as with the person who killed you, or your LnS claim will not be valid, and you can be killed. You may call Loot and Scoot in any zone after respawning from death so long as you head straight for your corpse. If you need to move across multiple zones in order to Loot and Scoot, you must call LnS as you move through each zone. If a new player enters the zone, you must call Loot and Scoot so they are aware of your intentions. You may not attack or be attacked while Loot and Scooting. After retrieving your corpse, you are allowed a short amount of time to med enough mana to safely get out of the zone (ie, enough for a couple casts of invisibility, FD, or a port spell), memorize those spells, and then must leave the zone immediately for 1 hour. This timer will start after the last person has exited the zone. If multiple players died in PvP and all choose to LnS, they may come to a mutual agreement to help each other do so (IE, res each other, drag corpses, port, etc) unless they have already opted out of LnS by fighting after death. After you have left the zone, you are considered to have finished Loot and Scooting, and may again be attacked.

calling LnS from pure PvE deaths is not allowed.

If you are killed and opt to fight instead of calling Loot and Scoot, you forfeit any later opportunities to invoke LnS. If you log out you may return in 1 hour and call Loot and Scoot.

In large scale PvP (7 or more players on both sides), LnS must be called by a force as a whole. Individuals may not invoke Loot and Scoot. LnS may be called by the force at any time, this option may never be forfeited. If a fight took place across multiple zones, the force is considered to have finished LnS'ing once all of their players have left the zones affected. Only the Force Leader or an Officer of the force may call Force LNS. If a force is on LNS they are allowed a small amount of time to gain mana to allow them mobility in order to leave the zone, camping out is not allowed while on LNS. All other LnS rules still apply.


If LnS is called, it may not be denied by the opposing player, or force. (ie: if i zone up to hate and get ganked by 30 members of <tinfoil hat>, i can call LnS without having to call force LnS, as force requires 7 or more players on both sides)

In regular PvP, you can only ever have one zone lockout active per group of players at any time. If a fight occurred across multiple zones, the winning group picks which zone the lockout will apply to.

In large scale PvP there is no limit to the number of zones a force can be locked out of. If a fight took place across multiple zones the lockout will apply to all zones a PvP related death occurred in.

Excessive bind point camping (killing a player over and over at their bind point) is against the rules.

Excessive killing of a player or group after they have finished LnSing may be stopped by a Project 1999 CSR, if it becomes excessive.

NPC corpse(s) are open to all players so long as said players are within range or the zone is flagged FFA. Do keep in mind, if you enter into a player agreement with the purpose of killing a target and decide to loot items that do not belong to you, this will be considered a PNP violation.

The P99CSR in attendance will decide what is reasonable in these cases. It is highly recommended that the people involved make equitable arrangements prior to involving the Project 1999 Customer Service Staff.
__________________
Last edited by Ambrogio; 02-08-2024 at 02:41 PM.. Reason: Revised language used in third question under Badain and the Ring War
  #2  
Old 07-12-2023, 11:47 AM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Added:
Quote:
Memory Blur in Raiding:
The use of this spell is strictly prohibited on raid targets. If a player lands this spell on a raid target, their guild must drop the raid target and let it completely reset. If a player lands Memory Blur on a raid target while another guild has FTE, their guild must concede the raid target.
Quote:
Plane of Sky
Zone:
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration: Gwan kills and Thunder Spirit Princess quest turn-ins only on your guild's assigned Sky day unless another guild gives you permission.
Additional Notes: Sky dates are determined in each servers' UN Discord servers.
Last edited by Blistig; 07-12-2023 at 02:30 PM..
  #3  
Old 07-12-2023, 06:26 PM
Ambrogio Ambrogio is offline
Senior Server Guide

Ambrogio's Avatar

Join Date: Jun 2021
Posts: 5,709
Default

Added:
Quote:
Q29: What if I witness or have information about a pathing exploit?
A: If you witness, discover, or hear of an exploit it becomes your responsibility to report it in the forum’s Petition / Exploit thread. Some exploits include but may not be limited to monetary gain from improperly dropping loot, pathing exploits allowing avoidance from being harmed by and easy dispatching of NPCs, and quest abuse that depends on deceptive tactics in gaining an improper amount of experience that also includes repetitious generating of quest items. We ask for everyone’s cooperation in this matter. It is important for us to correct these behaviors as quickly as possible.
__________________
Last edited by Ambrogio; 07-12-2023 at 06:28 PM..
  #4  
Old 07-31-2023, 07:55 PM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Added:
Quote:
Plane of Hate Mini Bosses, Maestro of Rancor, and Innoruuk
- Dispel pulling through the walls of the zone is prohibited.
Quote:
Sleeper's Tomb
Zone:
Translocate Allotment:
Run Speed Consideration(s): SoW
Location of Engagement: Anywhere
Additional Rule Consideration: Master of the Guard and the Progenitor are foot races. Start line is behind the double doors at the zone-in.
Guilds may COTH down to the tunnel leading up to The Final Arbiter.
Additional Notes:
Quote:
Memory Blur and the Lull Spell Line in Raiding:
The use of Memory Blur is strictly prohibited on raid targets. If a player lands this spell on a raid target, their guild must drop the raid target and let it completely reset. If a player lands Memory Blur on a raid target while another guild has FTE, their guild must concede the raid target. "Lull pulling" raid targets through walls is prohibited. Certain instances may be allowed at the sole discretion of P99 staff.
Last edited by Blistig; 08-12-2023 at 04:39 PM..
  #5  
Old 08-02-2023, 11:12 PM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Removed:
Quote:
Plane of Hate Mini Bosses, Maestro of Rancor, and Innoruuk
- Dispel pulling through the walls of the zone is prohibited.
Previously added due to statement and subsequent clarification from previous GM. No longer conducive to current raid scene and staff enforcement.
  #6  
Old 08-12-2023, 04:38 PM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Added:
Quote:
Statue of Rallos Zek / Avatar of War
Zone: Kael
Translocate Allotment: No COTH.
Run Speed Consideration(s): Spirit of the Wolf max run speed.
Location of Engagement: See forum post below.
Additional Rule Consideration:
Unlimited racers. Levitate required on racers. Race from Wakening Land zone line.
The guild who kills The Statue of Rallos Zek locks out all other guilds from engaging The Avatar of War for 20 minutes from Statue's time of death.
The guild who kills Statue may not engage or obtain an FTE on another raid mob during this 20 minute period unless AoW is killed or conceded.
  #7  
Old 08-16-2023, 11:59 PM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Fixed:
Quote:
Venril Sathir
Zone: Karnor’s Castle
Translocate Allotment: Not allowed.
Run Speed Consideration(s): SoW
Location of Engagement: Must kill in his lair or the room right outside of it.
Additional Rule Consideration:
Additional Notes: Able to XP in zone during window, but anyone past zone line must zone out if they are XPing (ex: rogues can’t sneak down from their xp camp or people can’t get coth’d if they are XPing before zoning out).
  #8  
Old 08-31-2023, 12:20 AM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Added:
Quote:
King Tormax
Zone: Kael
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes:
  1. May be killed at any chosen location.
  2. All trackers must be members of an eligible raiding entity, with a visible guild tag.
  3. COTH FTE is permitted, but a mage tracker may not be logged in at the time of a raid target’s initial spawn.
  4. If a mage tracker is seen in-game, near a raid target, their guild will receive a penalty and must concede 3 of that target.
  5. In the occurrence of a quake, any mage, near a raid target, must immediately gate to avoid a penalty for their guild.
  6. All rule details and enforcement, including number of concessions and additional punishments, are at the sole discretion of Project 1999 staff.

Statue of Rallos Zek / Avatar of War
Zone: Kael
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
The guild who kills The Statue of Rallos Zek locks out all other guilds from engaging The Avatar of War for 20 minutes from Statue's time of death.
The guild who kills Statue may not engage or obtain an FTE on another raid mob during this 20 minute period unless AoW is killed or conceded.
Additional Notes:
  1. May be killed at any chosen location.
  2. All trackers must be members of an eligible raiding entity, with a visible guild tag.
  3. COTH FTE is permitted, but a mage tracker may not be logged in at the time of a raid target’s initial spawn.
  4. If a mage tracker is seen in-game, near a raid target, their guild will receive a penalty and must concede 3 of that target.
  5. In the occurrence of a quake, any mage, near a raid target, must immediately gate to avoid a penalty for their guild.
  6. All rule details and enforcement, including number of concessions and additional punishments, are at the sole discretion of Project 1999 staff.
  #9  
Old 10-02-2023, 11:21 AM
Blistig Blistig is offline
Senior Server Guide


Join Date: May 2020
Posts: 3,329
Default

Added Ragefire rules. Previously under Q9 "Spawned Mobs" of Sirken's FAQ thread.

Quote:
Ragefire
Zone: Nagafen’s Lair
Translocate Allotment:
Run Speed Consideration(s):
Location of Engagement:
Additional Rule Consideration:
Additional Notes: Whoever turns in "Shimmering Pearl" to Zordak Ragefire has 20 minutes to engage Zordakalicus Ragefire, after 20 minutes has elapsed, it goes FFA.
  #10  
Old 12-20-2023, 05:14 PM
Visceryn Visceryn is offline
Senior Server Guide

Visceryn's Avatar

Join Date: Jun 2021
Posts: 1,932
Default

Updated Kael rules to take out the 3x concede for tracker FTE. It will not follow the same tracker FTE for all other raid mobs.
__________________
Closed Thread

Thread Tools
Display Modes

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 03:26 PM.


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 - 2024, Jelsoft Enterprises Ltd.