PDA

View Full Version : Class System


Rogean
08-01-2015, 10:27 PM
The class system has been suspended effective immediately. This will be evaluated in the future and re-implemented if necessary. The play nice policy still applies.

Pint
08-01-2015, 10:38 PM
please address the 2 mob bag limit going into velious. if we choose to kill 2 kunark mobs are we then time locked from killing velious targets as per the rules? is velious open ffa w/o bag limit?

arsenalpow
08-01-2015, 10:43 PM
please address the 2 mob bag limit going into velious. if we choose to kill 2 kunark mobs are we then time locked from killing velious targets as per the rules? is velious open ffa w/o bag limit?

Yup, could use clarifying.

arsenalpow
08-01-2015, 11:00 PM
Unless the only parts that stay relevant are respecting FTE and the PNP considering the bag limit used to exclude VP dragons which is now irrelevant.

Anichek
08-01-2015, 11:08 PM
Plus, Raid.php says it's suspended "as of the release of Velious"

So if a mob spawns before Velious launches, does the raid system still apply?

Assuming you mean it's dead effective the minute of your post (and the removal of the tracking tools on Raid.php) and everything is complete FFA - but we all want to make sure so we can all adjust accordingly.

Also, need to make sure that any and all agreements previously in Class R are null and void, and any and all agreements in Class C are null and void. The specifics of Cothing, Foot Races, etc etc etc.

Server staff (if they have validated certain agreements as part of the raid rules under the class structure) should clarify which agreements are considered permanent raid rules, and which are null and void with the dissolution of the Class System.

Hokushin
08-01-2015, 11:13 PM
Raid Policy
Play Nice Policy
Intentional training will be severely disciplined.
Guilds are encouraged to work out disputes among themselves before involving the staff.
All raid mobs provide an "FTE Shout" that show what guild has engaged. Kill stealing will be severely disciplined.
Guilds may not have any more than two representatives present at a raid spawn location.
To encourage competitive racing, guilds may not camp players out in the vicinity of raid targets.
Invulnerability spells used on engagement may only be for mechanic strategies, and may not be used to stall engagement.

+ http://www.project1999.com/forums/showthread.php?t=189856




All ya gotta worry about now

Anichek
08-01-2015, 11:16 PM
Hoku that's what we're going on the assumption with - but looking to make sure there's no other wrinkles.

And to clarify that it's the M.O. effective of Rogean's post in here, and not "as of the release of Velious" or whatever it says on .PHP

Ella`Ella
08-02-2015, 01:01 AM
Raid Policy
Play Nice Policy
Intentional training will be severely disciplined.
Guilds are encouraged to work out disputes among themselves before involving the staff.
All raid mobs provide an "FTE Shout" that show what guild has engaged. Kill stealing will be severely disciplined.
Guilds may not have any more than two representatives present at a raid spawn location.
To encourage competitive racing, guilds may not camp players out in the vicinity of raid targets.
Invulnerability spells used on engagement may only be for mechanic strategies, and may not be used to stall engagement.

+ http://www.project1999.com/forums/showthread.php?t=189856




All ya gotta worry about now

Hoku, how do you want to proceed in cases where a group is farming trash in kael/tov for faction/armor and raid targets spawn? Typically, that would clearly violate the 2 tracker rule by technicality, but I don't think poopsocking is going to be as pronounced/effective as it was in kunark and shouldn't be a problem if we maintain our no-stalling rules.

Anichek
08-02-2015, 09:56 AM
Hoku, how do you want to proceed in cases where a group is farming trash in kael/tov for faction/armor and raid targets spawn? Typically, that would clearly violate the 2 tracker rule by technicality, but I don't think poopsocking is going to be as pronounced/effective as it was in kunark and shouldn't be a problem if we maintain our no-stalling rules.

Addressed for Hoku - but applies to all other raid guilds too.

What seems reasonable/easiest is: If you have more than 2 in zone and the mob spawns, you're out. If you roll the dice and go farm up some faction and trash, knowing full well that the window is open/opening and a spawn may occur - that's the risk you run.

Without that remaining established, there'll be a lot of conveniently timed gear/faction farming going on as windows start to open up.....

Erati
08-02-2015, 11:20 AM
windows are gonna b much harder to know however, something to consider in terms of examining intent / ease of access to move a force to freshly popped mob

i dont think it should make u "out" but maybe a "cool down" to engage and well if no other trackers then thats not ur fault, no conceding needed

arsenalpow
08-02-2015, 11:35 AM
Having easy access to windows made it so everyone basically knew when something was going to potentially pop, that made it simple to police. Without that transparency I don't see how you can justify the DQ unless the intent is relatively blatant; like keeping the arena clear with a raid force to spike a statue or something like that.

Erati
08-02-2015, 12:15 PM
what Chest said - it would b great to not have raid forces poopsocking spawn points as "armor farming" sessions

Pint
08-02-2015, 02:47 PM
Maybe you just can't have first attempt? Agreed that it will be impossible to keep up with every mobs window now, ain't nobody got time for that.

Erati
08-02-2015, 03:32 PM
Maybe you just can't have first attempt? Agreed that it will be impossible to keep up with every mobs window now, ain't nobody got time for that.

my point being - if there is no one else even tracking to notice - theres not much the guild in zone can really do TBH

bktroost
08-03-2015, 03:00 PM
my point being - if there is no one else even tracking to notice - theres not much the guild in zone can really do TBH

Other than stare at a mob that just popped while they had no idea it was in window and now cannot engage it... sounds a lot like a good mechanics for dispersal of resources.

I like it a lot. A byproduct of a rule to not cause train wrecks inadvertently disperses pixels to the third or fourth tier competitive guilds out there because first or second just got nixed off the potential kill list. Sounds like a really good idea.

PS: That is not a sarcastic comment. It's a system that benefits the guild with the most knowledge, clears up space for other guilds to do armor runs when the knowledgeable guilds are staying out and allows for a greater variety in the guilds that take down end game content. No downside.

Anichek
08-03-2015, 05:15 PM
So:

a) If a guild is in a zone, and a mob spawns, and they are the only guild there - they can kill.
b) If a guild is in a zone, and a mob spawns, and it was being tracked by another guild - they forfeit rights to the first attempt.

Sounds pretty clear, easy to police. Downside is if a guild wants to capitalize on that rule, they place trackers in every zone to enforce forfeited 1st engage rights, which is insane to do.

Erati
08-03-2015, 05:16 PM
guilds just need to be upfront it seems about whether they are tracking or not

so others can 'contest'

the problem will become in the secrecy BS