Einherjar Setup and Thoughts

[Ikonic]

Macros:

PCMD commands:
/pcmd add name -- invites name to pt
/pcmd add <r> -- invites last person who sent you a /tell
/pcmd leave -- leaves the current pt
/join -- accepts pt invite or alliance invite

BRD Macro for leaving a pt and telling next pt leader to invite:
/p PT_LEADER invite -- have 3 macros, one for each pt leader
/t PT_LEADER invite
/pcmd leave

Required Items:

Everyone should bring the following:
- food
- poison pots
- echos
- antidotes

Alliance Setup:

Ideally this is the setup I'd like to take to Einherjar:

Each Alliance:
WHM, BRD, melee x4
WHM, BRD, melee x4
RDM, COR or SMN or BRD, BLM x4

Since we have so many melee I think this will allow us to power through the trash mobs fairly quickly.

If we have more than 20 people I think 2 assists will make the run go faster and smoother since we can keep the 2 alliances apart and cut down on some of the lag. We may need 2 pullers with this if 1 cannot keep the flow constant enough. A PLD or BLU would work well as a single puller as they can buff up to survive a few more hits.

I think we should have no less than 2 RDM/DRKs for zerging the boss.

BRD swap can help a great deal, but I feel should be limited to no more than 3 pts so songs can be active at all times. If we have more BRDs swapping we could have more pts (ie. 2 BRDs = 3 pts, 3 BRDs = 4 pts, and so on).

I would like to have sub-leaders for Einherjar to go over different parts of the fights so one person doesn't get overburdened.

I was thinking leaders for these parts:
BRD leader - invite order, what songs, when to 2hr
RDM leader - CS+Stun order
BLM leader - stun order, -ga order/setup, sleeps, tell which nukes to use
melee leader - probably the /assist(s), watch to make sure people are attacking only 1 mob, tell when to pull next mob, keep an eye out for the special mob

If you have any thoughts or suggestions about what I've posted or want to be a sub-leader please let me know through reply, PM, or /tell.

[JG!]

I think that we need to bring 1 pld for zerg. 1. reason that we lost was due to both rdms getting killed really early in CS. I think that after boss pull pld should grab mob and 2hr getting hate so that rdm can have a chance at CS with out mob attking them also then rdms should stagger there stuns. I lagged hard and bet I didnt get many stuns off.

2. reason for struggle was what IK said melee should be broken up in atleast 2 groups.. I bet most melee didnt even get to engage mobs 1/2 time before they died. or got 1 hit in at the most. So that just nullified our numbers. 1 puller is good enough tho.. problem was not the amount of mobs at all.. just that killing them took to long because of inactive dd.

2-3 dd kill /assist groups and blm pty would work great with that many people. And maximize our numbers.

[Tarage]

People complained about lag. I suspect that this could be fixed if people turned on filters and turned down effects. This should be mentioned to people who lagged too hard.

[Aleve]

I'm not a melee, but it seems to me, that if melee is only getting 1 hit per mob, maybe we should have 2 pullers and 2 mobs too.
As blm several mobs just died before I could get my nuke off. Spending half the zone weakened was not the way to go either. The first death was my fault due to not maintaining buffs as I should. Then there was the "Blm's sleepga" command that somehow killed all the blm's. Being in the wrong place at the wrong time didn't help much either.
Why was it that Crunch was not able to be slept?
On bosses like this one, would having a bind rotation help?

[Mnementh]

Personally, I think the setup should include at least a total of 3 melee parties set up like this:

brd, rdm, whm, melee x3
brd, rdm, whm, melee x3
rdm, whm, melee x3

with swaps.


We should have more rdms. Whms are being overburdened it seems and with rdm support hastes would be more steady. Haste is the most important thing for the melee party next to being alive, and if whms can't handle 4 melee hastes we need to get them more support. This would also lend more support for melee to be able to /sam, as well as keeping the support needs for each party less (less melee to take care of that is)

Not to mention rdm could handle refreshes for whms for more MP... though i am not sure of the mp needs so far.

Also if we have 2-3 melee parties, we can split the mobs into 2-3 groups and work individually... to reduce lag and kill faster as has been mentioned.

[Ikonic]

My plan was to have 36 people with 4 total melee pts. I do agree that more RDMs could be helpful for backup cures (so WHMs can rest more), refresh ('tho all our WHMs were /SCH), and extra stuns (assuming a few of them come /DRK).

If we have more than 25 people I think we should have 2 assists so we can have more people actually hitting the mobs.

[Crumb]

I think the best situation would just be having 1 brd per melee party and not do brd rotation until the zerg on boss. That would allow the brds to give ballad somewhat to the whms and they could help focus on sleeping as well. I know when I was a brd swapping it was constant and nonstop, not allowing for other things. Our DDs should be ok with just 2 songs, to be honest you probably only had 4 songs for about 15-30seconds at a time last run.

[Raizo]

I'm liking the ideas so far. 2 assists sounds very ideal for Tier 1-2's right now. Our next step after implementing these general strategies is to assign most ppl a specific static job as a general start point.
This will help cut down pre-planning headaches and allow ppl to get better at playing specific roles in einherjar.

I think some of the gaps we see in performance is that not everyone is aware of how specific this event sometimes is for certain roles. i.e. BLU spamming DD spells is really not the best use for them. They are excellent crowd control and with the right spells/food/buffs can keep all hate off BLM after sleepga and supertank until fresh sleeps are laid down.

After everyone is better accustomed how to react to every mob set and their roles we'll see a huge increase in performance.