Ragefire Agreement/Rotation

[Splorf22]

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

I'm done trying to explain the situation. We left the glare lord arch past the graveyard up and a few mobs near boogey house up. There should have been no reason for any sort of spotter.

Bottom line is VD benefitted from a raid banned guild training Draco on our entering raid force. I don't understand how you can defend this with a straight face.

Look the reality is that shit happens. Hell, the reason Eabon has his epic is that IB trained VD in hate on that Maestro [You must be logged in to view images. Log in or Register.] Half the problem on this server is that people get stupid/careless/thoughtless and then the other side assumes it was deliberate and goes all Hatfield/McCoy - the other half of the problem is TMO (just kidding, <3 you guys).

I think it's too bad you guys didn't get a crack at Draco that time, and if I could go back and GM delete those other trash mobs I would. As far as I know from listening to VD guild chat during the event there was no collusion, shit just happened (although I have no idea why the hell IB was running around in there with a train, its hardly like they were trying to play denial for us with Draco having a large window). In the end we got a Bone Razor and a Totem of Widdershins so from a loot perspective at least you guys didn't lose out.

[falkun]

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

The problem is that, in the interim, this is exactly what you're forcing every other guild to do. The consequence is that guilds whose clerics are unwilling to engage in an asinine clickfest will be bullied out of getting their epic, while those who do take part in the clickfest end up wasting insane amounts of time.

Not hating or anything, I don't think VD are bad people at all, I just think this isn't every well thought out.

This happened because the rotation as implemented is complete/on hold due to the raid suspension of all members of the original rotation before it was updated to include guilds outside of the raid suspension. Cold tried to work on the rotation agreement prior to the raid suspension and she was flatly refused by one member of the rotation. I cannot speak to the efforts of other guilds with respect to the rotation, but I would assume other guild leaders were also pushing to get their members added to the rotation. But that effort did not result in a rotation. Since the rotation is not happening atm, we are back to the chaos. Do not be niave enough to think that VD clerics will waste a ragefire. Get your guild leaders to force the rotation talks. VD isn't stopping you from joining the rotation, but we will work within established agreements (or the lack thereof in this case).

[Autotune]

Rotation Order:

Div, BDA, Taken, VD, TMO, IB

this is on a 1-1-1-1-1-1

Rules:

1) 30mins to engage for the kill
2) can be assisted if you can get the help within the time allowed
3) If you can't engage in 30mins and kill your Ragefire, you forfeit your turn to the next guild on the rotation.
4) If you fail twice in a row, you will be removed from the rotation.

How to get on the rotation:

To get on the rotation, a guild will have to apply to be considered. Then a guild will allow them to attempt to kill a Ragefire. This will be done by a guild willing currently on the rotation spawning the Ragefire for the guild. The applying guild will then a chance to kill the Ragefire to prove they deserve the spot on the rotation. ALL LOOT WILL GO TO THE GUILD THAT SPAWNED RAGEFIRE. If the guild fails, they must wait 2 weeks to reapply for consideration. The applying guild cannot receive outside help to be added and will be bound by all other rules described above. (any attempt to ninjaloot drops will remove the guild from any consideration to be added permanently)

This rotation will allow the guilds with the most completed cleric epics to keep the most, while everyone also obtains a cleric epic at the same rate.

Guilds will not be required to kill a naggy.


Any problems with this?

[Metallikus]

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

Rotation Order:

Div, BDA, Taken, VD, TMO, IB

this is on a 1-1-1-1-1-1

Rules:

1) 30mins to engage for the kill
2) can be assisted if you can get the help within the time allowed
3) If you can't engage in 30mins and kill your Ragefire, you forfeit your turn to the next guild on the rotation.
4) If you fail twice in a row, you will be removed from the rotation.

How to get on the rotation:

To get on the rotation, a guild will have to apply to be considered. Then a guild will allow them to attempt to kill a Ragefire. This will be done by a guild willing currently on the rotation spawning the Ragefire for the guild. The applying guild will then a chance to kill the Ragefire to prove they deserve the spot on the rotation. ALL LOOT WILL GO TO THE GUILD THAT SPAWNED RAGEFIRE. If the guild fails, they must wait 2 weeks to reapply for consideration. The applying guild cannot receive outside help to be added and will be bound by all other rules described above. (any attempt to ninjaloot drops will remove the guild from any consideration to be added permanently)

This rotation will allow the guilds with the most completed cleric epics to keep the most, while everyone also obtains a cleric epic at the same rate.

Guilds will not be required to kill a naggy.


Any problems with this?

I like it. As far as multiple vendor spawns during windows, where are people going to be directed to post when a ragefire spawns/is killed as in to notify the next on rotation?

[Bruman]

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

Any problems with this?

My only problem is that it's a sensible, clear, straight-forward, easy to monitor rotation, that would stop drama problems and calm down poop-socking and RnF posts.

Aka, way too sane for this server full of children.

But it definitely has my (worthless) vote.

[Autotune]

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

I like it. As far as multiple vendor spawns during windows, where are people going to be directed to post when a ragefire spawns/is killed as in to notify the next on rotation?

I'd like for all guilds to communicate on kill times. However, I suspect guilds that follow another guild while Ragefire is in window will keep track of them as well to keep up with the time limit.

AKA, BDA's turn to kill ragefire, i would encourage Taken to have a tracker to help watch for BDA's spawn.

And so forth.

[ownrage]

How long to engage until their slot is forfeit?

[Zapatos]

I really hope you're not trolling stealin. It looks good.

Just need the 6 main guild leaders to sign the stamp of approval asap, with NO PRECONDITIONS. no "just a few more for guild X to balance it out" or else it will never start.

And then all the GMs return to put on a big event to celebrate the server coming together on something!

[maverixdamighty]

Rules:

1) 30mins to engage for the kill
2) can be assisted if you can get the help within the time allowed
3) If you can't engage in 30mins and kill your Ragefire, you forfeit your turn to the next guild on the rotation.
4) If you fail twice in a row, you will be removed from the rotation.

[falkun]

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

How to get on the rotation:

To get on the rotation, a guild will have to apply to be considered. Then a guild will allow them to attempt to kill a Ragefire. This will be done by a guild willing currently on the rotation spawning the Ragefire for the guild. The applying guild will then a chance to kill the Ragefire to prove they deserve the spot on the rotation. ALL LOOT WILL GO TO THE GUILD THAT SPAWNED RAGEFIRE. If the guild fails, they must wait 2 weeks to reapply for consideration. The applying guild cannot receive outside help to be added and will be bound by all other rules described above. (any attempt to ninjaloot drops will remove the guild from any consideration to be added permanently)

Any problems with this?

One point of clarification: will the established guild who permits the test guild an attempt spawn the test ragefire and then the test guild must kill it or will the test guild spawn and then kill the test ragefire? Basically, does the established guild get that ragefire loot and the test guild only gets added to the rotation or does the test guild get added to the rotation and immediate loot? I do not feel any cleric should be forced to forfeit their pearl for a test ragefire (within the 30min stipulation).

Also, clarify where the test guild is added to the rotation should they succeed. I would suggest: the new guild will be added to the rotation immediately prior the the guild that permitted them the chance to join, starting on the next cycle assuming they succeed.