Quote Originally Posted by Duelle View Post
The real question is: where can we put this feedback to ensure it is seen and at the very least considered by the developers?

We have our Temper threads here, the temper feedback in the test server forum got buried already. Don't know what else we can do other than post some more.

To recap, Spontaneity/Quick Magic recast should be taken down 5 or 3 minutes. Worst case scenario, delete something from category 1 or 2 merits and replace it with the option to merit Spontaneity/Quick Magic from 5 minutes down to 3 minutes.

10 minute cooldown is too much for an ability that seems to be something to be used whenever possible and is not an endurance/survival tool like Convert.
You respond by thinking like a developer / community manager not a player.

The developers do not play this game, at night they go home and relax with their family's. They also don't speak English as a first language, and most likely don't speak English at all. When you combine these two things you realize that the only way to get anything to a dev is through their PR team, in this case the community managers / organizers. Now CM/CO's aren't players either, their forum moderators who's assigned job is to be a go-between for the FFXI development team and the player base.

What you have to do is make a clean post explaining the situation and asking them to look into it. Don't use gamer jargon or slang, don't flame, yell, sigh, or use emoticons. Just be clean and polite. They'll notice, their paid to read the forums (but not every post of a 30+ page thread) and if there is enough positive feedback behind something they'll take the idea / concern to the developers. The devs will go over it during their daily / weekly meetings (or whatever schedule their PM has them on) and that will be that. Just look at the DRK forum, the idea's were so off base and the reaction so loud that the CM's brought it to the dev's who agreed to rethink some of their planned DRK update. Also Dev's don't have much time, their extremely busy, so keep things short and don't ask for complicated implementations.