All of the information about this topic is not officially canon and should never be considered true within the RPG.
Non-canon information is usually left in for reference, extra reading, or the content was altered after being canon.

Battle of Sucan X

Siege of Sjutnarevo


Battle of Wglinian


BlyDonian-Suzun war


BlyDonian Space


Suzu Thrust


BlyDonian Space


July 23rd, 2012


Sucan X

Flag of Suzu Suzu

Seize Sucan X


BlyDonian Victory
Suzu Tactical Victory

Flag of the BlyDonian Civilization BlyDonian Civilization
Flag of Suzu Suzu
Flag of the BlyDonian Civilization
Commander Herst
Flag of the BlyDonian Civilization
Vice Admiral Yushidan
Flag of Suzu
General Tactal
Flag of the BlyDonian Civilization
Sucan X Defense Forces
  • BDN Defiant
  • BDN Supreme
  • BDN Conquest
Flag of the BlyDonian Civilization
Ground Snow Corps
Flag of Suzu
Various forces from its fleet
Flag of Suzu
Ground Snow Expeditionary Fleet
Flag of the BlyDonian Civilization
BDN Supreme
Flag of the BlyDonian Civilization
4,020 Snow Soldiers
Flag of the BlyDonian Civilization
1 Orbital Space Station
Flag of the BlyDonian Civilization
34 tanks and other ground artillery
Flag of Suzu
1,002 soldiers
Flag of Suzu
12 tanks and gunships
Civilian casualties


The Battle of Sucan X occurred on July 23rd, 2012. It was technically a BlyDonian Victory, as Sucan X remained in its hands, however Suzu was able to destroy one of the BlyDonian ships guarding the planet, as well as damaging one other. They also had ground superiority before BlyDonian reinforcements from the main capital city of Tian were able to route the invaders.


The Suzu Forces attacked first in the war, moving into BlyDonian Space and attacking the cold icy planet of Sucan X. Although BlyDonia instigated the war, Suzu decided they were going to make the most of it and try and seize planetary systems instead of going on the defensive. Emperor Orthmys ordered General Randal Tactal to attack the mineral rich planet to disrupt trade and commerce and also to seize the planet for itself.

Start of BattleEdit

BlyDonian sensors detected Suzun ships entering their space and plotted their trajectory as heading for Sucan X. The nearest fleet, the Fourth dispatched three vessels, led by the BDN Defiant, the second commanding vessel in the Fourth Fleet. The Suzun Forces arrived first, and opened fire on the orbiting space stations that immediately fired back. Fighters were dispatched and a dogfight ensued. A few frigates were sent out to keep the Suzu fleet at bay, and shortly after, the BDN Defiant, Supreme, and Conquest arrived. Before they could arrive, the Suzu dispatched a few landing parties to land outside of Talshia, a major city on the surface.

Battle of TalshiaEdit

The Suzu landing forces donned cold assault gear, and began to bombard the energy shield around Talshia that protected it from the cold weather. BlyDonian Cold Assault forces were forced to fight back the incoming invaders, causing heavy casualties before reinforcements from Tian arrived to decimate the Suzu landing party.

Conclusion of Space BattleEdit

Suzu forces were able to destroy the BDN Supreme, a Sunrise Class Capital Ship, before being routed away. A severely damaged Suzu ship exploded nearby a space station, but not before both were abandoned. BlyDonia captured 231 Suzu soldiers and sailors, while Suzu captured 329 BlyDonian forces. Commander Tactal then ordered a strategic retreat, and left the system feeling accomplished.


Although BlyDonia had claimed a victory by keeping their planet, it was in reality a Suzu strategical and tactical victory, since they were able to soften Sucan X's defenses, destroy a powerful vessel, and determine the strength of the BlyDonian Army. It was following this that central command realized that some forces were seriously under trained. As a result, more training was forced upon the men and they trained longer hours.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.