FTE Shouts: Rethinking Their Mechanics and Issue

[falkun]

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

But if Guild B knew they could disengage and camp aggro after a FTE shout awarded the mob to Guild A, there is a decent chance Guild A will wipe and Guild B will get their shot. So raid encounters become a little bit more about mobilization, even if mobilization here just means "who can log in the fastest at the spawn".

This is granted via the incoming FTE shouts, you won't need FTC shouts for this functionality. I completely agree that Guild_B, once committed, pretty much has to stick on the raid mob currently, pre-FTE shout implementation. I anticipate many more disengages (and likely wipes) following the FTE shout implementation. FTC shouts bring in a bunch of new variables and rules to lawyer and hash out. For instance, guilds may disagree how many bodies represents an engaged force or how long it takes to pull a mob. FTE shouts, an extension/automation of the already existing FTE metric, minimizes additional creation of game mechanics/server rules to govern the player-base.