Thread: First in Force.
View Single Post
  #9  
Old 10-27-2015, 01:01 PM
maestrom maestrom is offline
Sarnak


Join Date: Oct 2010
Posts: 464
Default

Quote:
Originally Posted by Sadre Spinegnawer [You must be logged in to view images. Log in or Register.]
This would just turn into a diff version of FTE. As it stands FTE involves mobilizing and, as soon as you can get and keep a FTE, you launch the attack.

FiF has several serious problems:

1) defining what a force is, which would be very mob dependent and each guild would naturally lowball what they consider an adequate force for them.
I thought about this--tieing the definition of raid force to specific targets. It might be best to handle it by groups. Kunark and lower targets need 24. Velious-era mobs take something more. 48?

Quote:
2) can a force add to itself as more people log on? If not, yeah, that's gonna be popular. Who closes the window for "ok, this is your force, no more may join?"
There would be no "window" for when you can no longer bring people into a raid. The intent of this rule isn't to force guilds to take down targets with fewer people. The intent of the rule is to allow guilds to lock in ONE target at a time as theirs so they don't have to worry about trainfests and FTE sniping.

Quote:
3) would replacements be allowed as the guild waits? How would that work? Can you start out your force with a dozen rangers then gradually try to get other classes in?
I thought about this, but since people can't two-box I don't see a reason why we need to worry about who is actually sitting there. If the guild has claimed 1 target, then they can't claim another target. They can go FTE unclaimed targets or farm other loot/group content. But I imagine the players who get left socking would get grumpy and either get their guild to give up the sock or cycle people around. No reason to say that it has to stay this 24 people.

Quote:
4) if the force # drops below the required number, due to a ld, do they lose the right?
This has given me some trouble. It could either be handled with a "-5" rule. Or a timer. Once claimed, you have an allowance of 5 raiders. If you lose 5 raiders (such as going from 24-5= 19 raiders) then you lose the claim. Another solution is as follows. Guild A claims target. Guild B zones in. Guild A loses 5 people and drops below the raid force threshold. Guild B can inform Guild A that their timer has started and they have X minutes to get back up to 24 or they lose their claim.

I am sympathetic to a rule that says if your raid has some lag and drops below "raid force" that you lose your claim automatically, but that might be easiest to enforce. I don't expect it will happen that often though.

Quote:
5) socking the camp from when it's spawn window opens, which means that the "FTE" moment means who has a force at zone at the moment spawn window opens, which means guilds would actually sock to be able to sock
The rule does not discuss windows. I imagine claims won't go in on targets that aren't in window. But if a guild really really wants to claim Tormax even though he won't be in window for 3 more days, then i supposed they're free to sock Tormax all week. I imagine this won't happen, because...

Quote:
6) Can a guild camp multiple spawn windows as long as they have a sufficient force at each?
No. The rule says you get ONE claim per guild/alliance at a time. If guild A plants its raid force at and claims Tormax, it cannot put another raid force at Sontalak and claim him. One claim per guild/alliance.