
Dear uaRO GM and Development Team,
First and foremost, we would like to thank the entire uaRO team for the time, dedication and hard work you continue to put into the server.
We recognise that maintaining and balancing a pre-renewal Ragnarok Online server is no small task. We also appreciate the willingness to improve expanded classes such as Ninja, which have historically received less attention than traditional classes.
The recent Ninja changes brought several welcome improvements, including Shadow Hiding, reduced Wind Blade after-cast delay, improvements to Throw Zeny, adjustments to Shadow Jump, and changes to Watery Evasion. These are positive developments, and we genuinely appreciate the effort behind them.
However, we would respectfully like to ask the team to reconsider one particular change introduced on 10 November 2026: the removal of Blaze Shield's movement-interruption effect.
We want to make it clear that we are not disputing the technical basis for the change.
Current rAthena implements Crimson Fire Formation (Blaze Shield) without its previous knockback or flinch effect. This behaviour was established through an upstream correction many years ago, and uaRO's recent update brought the skill into alignment with that implementation.
We recognise the importance of maintaining consistency with rAthena and addressing unintended mechanics.
There is also a documented history behind the skill. The original eAthena changelog records the addition of knockback to Crimson Fire Formation in October 2007. Later rAthena development removed that behaviour, with the change also discussed in Hercules development forums.
This demonstrates that the behaviour has a long history within Ragnarok Online emulators, rather than being something recently discovered or deliberately exploited by uaRO players.
We are not claiming that the previous behaviour was the official intended implementation. We are simply asking that its impact on actual gameplay also be considered.
A change can be technically correct while still having an unintended negative effect on class balance.
For many Magic Ninja players, Blaze Shield was not simply another damage-dealing skill.
Its movement-interruption effect provided a practical form of crowd control that allowed a relatively fragile class to survive encounters while casting its offensive skills.
Unlike traditional magic classes, Ninjas have particular limitations involving skill points, available elements, survivability and their dependence on cast speed.
Blaze Shield helped compensate for some of these limitations.
Most importantly, it allowed newer and moderately geared Magic Ninjas to progressively explore more challenging PvE content without immediately requiring extremely expensive equipment or near-instant casting.
Following the update, players have reported difficulties in areas involving:
Enemies that previously experienced movement interruption can now pass through the skill more quickly, often reaching the Ninja before another spell can be cast.
This affects much more than convenience. It changes how the class survives, how effectively it can mob, and which areas players can realistically attempt.
We acknowledge that Ninja received several valuable improvements in the same patch.
Wind Blade is now more practical, Shadow Hiding improves mobility and equipment flexibility, and Throw Zeny provides another potential build direction.
Watery Evasion also received a substantial movement-speed reduction improvement.
However, these additions do not necessarily replace Blaze Shield's former defensive functionality.
Several players have experimented with alternative builds, higher DEX, Watery Evasion, Shadow Jump and different offensive combinations.
Some have achieved encouraging results, and we absolutely recognise that Magic Ninja remains playable.
But the concern is not whether a highly geared player can adapt.
The concern is whether the class remains reasonably accessible and enjoyable throughout its progression, particularly for players who cannot afford near-instant-cast equipment.
Requiring substantially more DEX or specialised equipment to compensate for the loss of one defensive mechanic creates a greater barrier for newer players.
Similarly, Phantom Zeny is an interesting addition, but its 300-million-Zeny unlock cost and associated skill-point investment make it a specialised alternative rather than a direct replacement for a Magic Ninja's defensive toolkit.
We would therefore ask that the Blaze Shield change be assessed on its own gameplay merits rather than simply against the number of other improvements introduced.
One of the reasons we enjoy uaRO is that it preserves the classic Ragnarok experience while introducing thoughtful improvements where they benefit gameplay.
The server's own Class Changes documentation highlights adjustments across multiple classes that intentionally differ from original pre-renewal behaviour.
These changes reflect a sensible balancing philosophy: preserving the identity of classic Ragnarok while improving the experience for modern players.
We are not asking uaRO to abandon rAthena standards.
We are asking whether a carefully limited exception for Blaze Shield's PvE utility could be consistent with the same balancing philosophy already used elsewhere on the server.
In our view, maintaining a healthy and enjoyable class experience is just as important as maintaining technical consistency.
We understand that Blaze Shield's previous functionality may have raised balance concerns, particularly in Battlegrounds or PvP.
We do not know whether those concerns were the reason for the change, and we would welcome clarification.
Rather than requesting an unconditional reversal, we would like to suggest several possible compromises.
Our preferred solution would be to retain the current rAthena behaviour in PvP, Battlegrounds and WoE, while restoring the previous movement interruption against monsters in PvE.
This would preserve competitive balance without unnecessarily affecting players who primarily enjoy PvE content.
The effect could also be restricted against specific monsters or bosses if necessary.
Another approach used in custom Ragnarok balancing is to make specialised skill functionality available through equipment, requiring players to sacrifice another benefit in exchange.
For example, a custom Ninja card could:
This would give players a choice between additional damage, stats, survivability or Blaze Shield's former defensive utility.
It would not be a free enhancement, and it would provide another avenue for character customisation.
If restoring the previous functionality is not desirable, perhaps a weaker version could be considered.
For example, a reduced movement interruption, a limited knockback effect against eligible monsters, or a separate defensive adjustment to improve Magic Ninja survivability.
We are open to alternatives and would appreciate the opportunity to discuss what the development team considers practical and balanced.
We understand that gameplay observations alone do not establish precisely how much the change has affected overall balance.
If the team is willing, we would be happy to help test different solutions using both entry-level and highly geared Magic Ninjas.
This could include measuring survivability, mobbing effectiveness, SP consumption and practical performance against normal monsters and bosses.
A limited trial or test-server implementation would allow the community and developers to evaluate the results before making any permanent decision.
We are not asking for Ninja to become the strongest PvE class or for any build to trivialise difficult content.
We simply hope that its previous progression opportunities and distinctive gameplay style can be preserved where reasonably possible.
We appreciate that the GM team must make decisions for the health of the entire server, not just one class or group of players.
We also understand that not every community request can be accommodated.
Nevertheless, we hope the concerns surrounding Blaze Shield can be considered as legitimate gameplay feedback rather than simply resistance to a bug fix.
Players who relied on this mechanic were using functionality that had been available on uaRO for a long time. They developed their builds, equipment and playstyles around the version of the skill the server provided.
We believe there is an important distinction between exploiting an unintended mechanic and reasonably using an established gameplay feature.
Likewise, acknowledging that something has been fixed does not prevent us from discussing whether the resulting balance is appropriate.
We are not asking the team to choose between rAthena accuracy and player enjoyment. We are asking whether a balanced solution can respect both.
We respectfully request that the development team reconsider Blaze Shield's PvE functionality, clarify the balancing concerns behind the change, and explore whether a PvE-only adjustment or equipment-based compromise might be possible.
We genuinely value uaRO and want to continue supporting the server and the community that has grown around it.
Thank you again for your time, your hard work and your consideration.
We hope this letter can serve as the beginning of a constructive discussion.
With appreciation and respect,
Members of the uaRO Ninja Community