Beastmaster Rankings Delayed in FFXIV








Sq. Enix has postponed the Season 1 rating interval for Crucible of the Unbroken in Closing Fantasy XIV, citing ongoing stability work on the Beastmaster restricted job, in accordance with an announcement on the official Lodestone.
The subscription MMORPG's growth staff says it has acquired appreciable suggestions on Beastmaster's fight stability together with experiences of points tied to sure gameplay mechanics. A future publish will verify the precise begin date as soon as these changes land, however no specifics on what's altering have been shared but.
Beastmaster launched as FFXIV's second restricted job in patch 7.56, and Crucible of the Unbroken was constructed as its aggressive solo endgame – a roguelike gauntlet the place gamers who end within the prime 300 on their server every season earn an unique mount. That reward threshold has already drawn criticism from gamers who contemplate it unreasonable for a restricted, level-50-capped job, and the delay has solely sharpened calls locally to scrap seasonal rankings fully in favor of a flat clear-based reward.
This is not the primary post-launch repair Beastmaster has wanted; Sq. Enix additionally needed to handle a separate Beastmaster bug shortly after the job went dwell, underscoring how a lot tuning a pet-collection job with roguelike scoring apparently nonetheless requires.
Gamers with out the remodeling automobile mount from the Closing Fantasy XV crossover occasion get a comfort prize within the meantime: that occasion returns September twenty fourth for anybody who missed it the primary time, although it affords nothing new for individuals who already cleared it.
With no new rating date set, the true check is whether or not Sq. Enix's stability adjustments handle the exploit complaints substantial sufficient to make top-300 competitors really feel honest, or whether or not the format will get rethought earlier than Season 1 ever begins.
Additional studying: MassivelyOP



Associated:
$publish = $orig_post;
wp_reset_query();
?>







Source link