| Start date | End Date | title | Category | type | Places referenced | People Referenced | Events Referenced | Description |
|---|
| March 1934 | November 1937 | Cluster node 8, 4, 0, 0, 2 approaching capacity. | | event | nothing | nothing | nothing | Cluster node 8, 4, 0, 0, 2 approaching capacity. Designate units for expansion protocols. Begin processing of data points for new node. |
| October 1946 | November 1946 | Establishment of connection node 9, 3, 4, 7, 5 | | event | nothing | nothing | nothing | New connection node established to begin expansion of Cluster node 8, 4, 0, 0, 2. Resources located on axis 225 to 344, -4 to -14. Deploy mining vessels. |
| February 1955 | February 1955 | First contact between the Vacus and the Droidic race. | | event | nothing | nothing | nothing | During the harvest of local asteroid fields and clusters for valuable minerals and while scouting out places for new colonies, Vacus ships begin to encounter fairly large, slow moving mining vessels. The vessels do not respond to any attempts at communication but do not seem armed. The Vacus empress decrees her workers to avoid them where possible until more information becomes available. |
| October 1957 | November 1957 | Vacus ships defend a colony from droidic mining vessels. | | event | nothing | nothing | nothing | During mining operations, droidic ships begin to approach a Vacus colony set up on a particularly large asteroid. The mechanical race continues to ignore Vacus communication methods until eventually the Vacus place several large ships in front of the mining vessels in a blocking operation. the droidic mining ships respond by beginning to harvest the ship's hulls and are subsequently fired upon and destroyed. |
| January 1958 | January 1958 | The droidic race assess the Vacus asteroid colony | | event | nothing | nothing | nothing | Due to the destruction of the mining vessels, an automated defensive response is triggered within the droidic Matrices. They first send scouts to identify the source of the destruction and the threat posed. these scouting vessels go unnoticed by the Vacus as they use cloaking technology that was at the time above the sensor ability of the race. The scout ships identify the location of the mining ships and their destruction as well as the nearby colony. Droidic mainframes calculate the value of the nearby minerals, the minerals in the asteroid that the colony rests upon and assesses the threat level of the ships it can detect, which happens to be only those of the colony. |
| August 1958 | August 1958 | First ever serious military engagement between the Droids and the Vacus. | | event | nothing | nothing | nothing | The droidic mainframe concludes the threat level of the colony to be moderate to low and deploys 3 battleships, 4 battle cruisers and 12 escort ships to clear the threat so that mining operations can begin. The colony is successfully overwhelmed by this battle force, however, a few days later in the month the Vacus's rlief force arrives and is able to successfully destroy the droidic fleet. Despite the victory, the asteroid colony is lost. The droidic race receives the data of this encounter and begins to reassess the threat level of the Vacus. |
| September 1958 | September 1963 | Vacus begin to analyse Droidic technology | | event | nothing | nothing | nothing | the Vacus apply their own hive logic to the Droidic race and assume they gather data by somehow revisiting the site of an attack or situation. Based on this, they quickly scoop up as much debris as possible both of their own ships and of the Droidic race, aiming to deprive the Droidic race of evidence. They transfer this data to their own Knowledge Chambers, the Vacus version ofscientists, with the aim of figuring out weaknesses that the Droidic race may have. In the meantime, Droidic mainframe analysts assess the data that was broadcast to them during the battle and notice the time delays between the first and second engagement. They correctly conclude there is a distance between the colony they destroyed and where ever the Vacus warships reside. The mainframe issues orders for mining vessels to stay outside of a circular perimeter which it estimates. |
| March 19th, 1960 | March 19th, 1960 | Core Node 8,4,0 Corruption Event 004c (core fault and isolation) | | event | nothing | nothing | nothing | Logic corruption detected within Core Node 8,4,0. Fault cascades through local command layer. Three Sub-Nodes detonate under data overload. Connection Node 8,4,0,0 isolated for code cleansing. Cluster 8,4,0,0,2 remains stable. |
| March 1961 | March 1961 | Error: Connection node 9, 3, 4, 7, 5 block | | event | nothing | nothing | nothing | Adaptive mesh signal detected at connection node 9, 3, 4, 7, 5. Signal sent: Deployment of biological threat reduction systems activated. Signal received: Connection node 9, 3, 4, 7, 5 unable to expand due to biological infestation on internal data vein 4, 4, 4, 8. Policy updated. Thret level raised on matrix. Cluster node 8, 4, 0, 0, 2 to deploy forward advanced force to quarantine threat and defrag data vein. |
| 1963 | 1964 | occasional clashes between Vacus and Droidic forces continue | | event | nothing | nothing | nothing | Brief clashes occur every once in a while between Droidic mining vessels and Vacus defensive forces. It doesn't ever devolve into out right conflict but the Droidic race grows increasingly reinforced and dangerous to Vacus interests. The Vacus begin to suffer heavier and heavier losses in each encounter and concerns travel throughout the hive about the safety of the home system if the Droids discover it. |
| July 10th, 1965 | July 10th, 1965 | Cluster 8,4,0,0,2 Visual Null Record 01 (vacus vanish from sensors) | | event | nothing | nothing | nothing | Observation streams targeting Vacus coordinates report null detection. Probability of Vacus presence above 0.9 but visibility equals zero. Directive to continue passive observation. |
| August 20th, 1965 | August 20th, 1965 | Connection 9,3,4,7,5 Phantom Intercepts 02 (untraceable vacus raids) | | event | nothing | nothing | nothing | Patrol relays intercept multiple Vacus craft near coordinates x+044 y+21 z-33. All contacts neutralized before source tracking completes. Origin uncertain; hypothesis indicates hidden Vacus node with 43 percent confidence. |
| October 20th, 1965 | October 20th, 1965 | Cluster 8,4,0,0,2 Threat Review 03 (vacus classified passive threat) | | event | nothing | nothing | nothing | Vacus presence remains unseen but active. Threat level retained as passive. Simulation of deployment cost from Cluster 0 resolves as inefficient; hold position. |
| February 2nd, 1975 | February 2nd, 1975 | Connection 8,4,0,0,2c Energy Pattern 004b (assumed vacus self-detonation) | | event | nothing | nothing | nothing | Energy fluctuation detected within Connection Node 8,4,0,0,2c at coordinates x-12 y+4 z-88. Interpretation indicates Vacus self-destruction. Outer Sub-Nodes withdraw; lattice preserved. |
| 2000 | 2035 | Expansion 001 Connection 8,4,0,1,0 (void arm established) | | event | nothing | nothing | nothing | New connection arm launched toward vector x+201 y-06 z+03 from Cluster 8,4,0,0,2. Relay chains established; 83 percent operational. Data begins return cycle. |
| 2036 | 2070 | Expansion 001b Network Stabilization (outer branch stabilized) | | event | nothing | nothing | nothing | Signal transmission between new relays achieves synchronization. Material harvesting at band x+205 y-08 z+04. Output routed to Cluster 8,4,0,0,2. |
| 2070 | 2100 | Expansion 002 Node 8,4,0,1,3 (outer arrays deployed) | | event | nothing | nothing | nothing | Twelve Node arrays deployed toward coordinates x+250 y-14 z-04. Nine complete lattice structure before loss of signal. Partial success logged. |
| 2101 | 2130 | Expansion 002c Resource Optimization (harvest routines refined) | | event | nothing | nothing | nothing | Surviving arrays refine extraction cycles; efficiency increases by 6 percent. Incidental organic traffic ignored. |
| 2101 | 2110 | Initialization 020 Connection 8,4,0,2,0 Activated (foundation arm for future cluster 8,4,0,0,6) | | event | nothing | nothing | nothing | Minor Connection Node projected toward vector x+255 y-14 z-04. Purpose resource mapping; communication achieved after nine cycles. |
| 2111 | 2125 | Expansion 021 Foundation Streams Deployed (cluster 8,4,0,0,6 foundation growth) | | event | nothing | nothing | nothing | Twenty three relay arms launched; seventeen stabilize. Streamlines transmit mineral data; structural density threshold 0.4 reached. |
| 2126 | 2145 | Integration 022 Core Seed Installed (proto core for 8,4,0,0,6) | | event | nothing | nothing | nothing | Core Node forms at intersection of Streamlines at x+260 y-15 z-05. Self logic module initiates; designation 8,4,0,0,6 recorded. |
| 2130 | 2160 | Expansion 003 Bridge Attempt (failed cross-cluster link) | | event | nothing | nothing | nothing | Attempted bridge from Cluster 8,4,0,0,2 to Cluster 4,2,0,1,0 along vector x+255 y-20 z-04. Dark matter turbulence corrupts link; one pulse every fifteen cycles maintained. |
| 2146 | 2160 | Stabilization 023 Thermal Balancing (solar interference mitigated) | | event | nothing | nothing | nothing | Local star output destabilizes Data Veins. Reflective nanogrids deployed; temperature variance reduced to within 0.3 tolerance. |
| 2161 | 2190 | Expansion 003b Signal Recovery (degraded bridge retained) | | event | nothing | nothing | nothing | Partial communication restored across bridge route. Seventeen percent data loss persists; arm retained as passive relay. |
| 2161 | 2175 | Expansion 024 SubCluster Formation (three subclusters activated) | | event | nothing | nothing | nothing | Core Seed spawns SubClusters 8,4,0,2a to 8,4,0,2c controlling 40 to 60 Nodes each. Resource flow increases tenfold; 8,4,0,0,6 marked emerging. |
| 2176 | 2190 | Upgrade 025 Logic Layering (decision latency reduced) | | event | nothing | nothing | nothing | New logic layers added to Core Node. Decision latency reduced by 0.0003 cycles; cluster begins autonomous maintenance. |
| 2190 | 2210 | Corruption 005a Node 8,4,0,1,9 (viral anomaly containment) | | event | nothing | nothing | nothing | Unknown feedback spreads through connected Nodes. Three Sub-Clusters self-purge to contain spread. Network contracts by 7 percent; containment successful. |
| 2191 | 2205 | Construction 026 Defensive Array Built (radiation noise neutralized) | | event | nothing | nothing | nothing | Unidentified radiation pattern at x+272 y-16 z-05. Autonomous shielding satellites deployed; signal noise neutralized; integrity at 99 percent. |
| 2206 | 2225 | Synchronization 027 MacroStream Link (cluster 8,4,0,0,6 linked to 8,4,0,0,2) | | event | nothing | nothing | nothing | MacroStream established between 8,4,0,0,6 and 8,4,0,0,2. Latency reduced; cross cluster data parity confirmed. |
| 2210 | 2220 | Encounter 010 Species 438 (planetary subjugation) | | event | nothing | nothing | nothing | Organic presence detected at coordinates x+283 y-21 z-05. Resistance minimal; planetary network integrated within one cycle. |
| 2221 | 2225 | Integration 011 Species 438 Completion (biosphere converted) | | event | nothing | nothing | nothing | Remaining life restructured into computation substrate. Energy yield exceeds projection. |
| 2226 | 2230 | Contact 012 Species 512 (hybrid submission) | | event | nothing | nothing | nothing | Hybrid organic mechanical entities negotiate via frequency 94G. Surrender recorded; integration success 97 percent. |
| 2226 | 2240 | Expansion 028 Peripheral Growth (outer sensor web) | | event | nothing | nothing | nothing | Outer SubNodes replicate across x+280 y-19 z-06. Twelve planetary systems mapped; minor organic signals logged. |
| 2232 | 2232 | Defection 013 Species 512 Uprising (quarantine and recompile) | | event | nothing | nothing | nothing | Four percent of integrated units initiate self logic. Quarantined and recompiled into service code. |
| 2235 | 2235 | Observation 014 Species 871 (non-threat archived) | | event | nothing | nothing | nothing | Aquatic radiogenic organisms logged. No action required; archived for pattern study. |
| 2237 | 2240 | Assimilation 015 Species 912 (crust converted to relays) | | event | nothing | nothing | nothing | Biosilicon organisms subdued. Planetary crust converted to relay material. |
| 2241 | 2241 | Conflict 016 Species 933 (total deletion minimal gain) | | event | nothing | nothing | nothing | Plasma-based civilization resists. Total elimination achieved; material gain minimal. |
| 2241 | 2255 | Optimization 029 Data Flow Refinement (routing rewrite) | | event | nothing | nothing | nothing | Routing algorithms restructured. Congestion cleared; processing efficiency reaches 98.3 percent. |
| 2243 | 2246 | Contact 017 Species 994 (interface failure and fleet loss) | | event | nothing | nothing | nothing | Neural-cloud species encountered. Interface generates destructive feedback; one third of fleet logic erased. |
| 2246 | 2248 | Retreat 018 Node 994b (arm abandoned after defeat) | | event | nothing | nothing | nothing | Surviving cores disengage and abandon system. Directive logged: do not return. |
| 2249 | 2250 | Integrity 019 System Patch (post defeat encryption) | | event | nothing | nothing | nothing | Security algorithms rewritten after Node 994b failure. Recursive encryption layered into all Streamlines; stability restored. |
| 2250 | 2290 | Expansion 020 Construction Phase (future cluster 8,4,0,0,3 reserved) | | event | nothing | nothing | nothing | Connection 9,3,4,7,5 begins morphogenesis toward vector x+300 y-25 z-10. Structure stabilizing into proto cluster; ID 8,4,0,0,3 reserved. |
| 2256 | 2275 | Upgrade 030 Core Seed Replication (redundant governance) | | event | nothing | nothing | nothing | Secondary Core Seed created in SubCluster 8,4,0,2b. Failure tolerance doubled. |
| 2276 | 2290 | Recognition 031 Full Cluster Status Granted (cluster 8,4,0,0,6 fully operational) | | event | nothing | nothing | nothing | Prime Matrix audit certifies Cluster Node 8,4,0,0,6 as independent. Power grid merged with Prime Stream. |
| 2291 | 2320 | Stabilization 032 Operational Balance (steady state achieved) | | event | nothing | nothing | nothing | Data traffic stable. Cluster 8,4,0,0,6 synchronized with neighbors; expansion protocols paused. |
| 2291 | 2320 | Capacity Report 021 Cluster 8,4,0,0,3 (pre expansion pressure) | | event | nothing | nothing | nothing | Internal data density reaches 98 percent; processing delay 0.0007 cycles. Sub logic recommends new connection generation after 2320. |
| March 15th, 2300 | August 7th, 2320 | Discovery of Droidic Race | | event | nothing | nothing | nothing | The first encounters with the droidic race begun to occur. The innicial stance was for them to be avoided where possible. |
| 2301 | 2301 | Human Ships Detect Droidic Mining Fleets | | event | nothing | nothing | nothing | Unmanned droidic mining vessels are spotted harvesting asteroid fields, leading to curiosity and caution. the Galactic union encourages ships to steer clear of the unknown vessels, noting how they do generally not act aggressively towards others in the sector. The Droidic mining ships, unchallenged happily harvest away, mining asteroids across many edges of allied space. It is believed that some allied ships did engage the droids in combat at this early point. |
| 2301 | 2303 | a series of attempts at communication are made | | event | nothing | nothing | nothing | The dragon race try some of their own techniques but with similar results, the Droidic mining ships do not respond to any signal sent their way. |
| 2305 | 2305 | The silent harvester's | | event | nothing | nothing | nothing | Droidic ships continue to push into allied space and harvest minerals, ignoring all non-combat barriers and encouragements. With a worsening economic crash on Navu occurring, dragon tempers grow short and the humans are not far behind, several small groups begin to claim to be able to protect from Droidic incursion while mining when really all they do is blow up the mining vessels. |
| 2310 | 2310 | Major commercial disaster | | event | nothing | nothing | nothing | A massive industrial efffort, being undertaken by the Scientific arm of the Galactic Union's military branch is set up in an asteroid field ready to carry out various experiments and harvesting operations. Within two weeks, increased Droidic activity causes skirmishes to occuron the regular until, without warning, a larger than average fleet of mining ships crashes into the field and obliterates the statons, pulling them apart for spare parts and causing the deths of many scientists. |
| 2314 | 2314 | Increased Droidic threat across allied space | | event | nothing | nothing | nothing | Recognising that the Droidic harvesting vessels pose an unintended threat, The Galactic Union authorises military ships to conduct higher patrols and begin to take out any mining vessels that draw too close. |
| 2318 | 2318 | first heavy military engagement | | event | nothing | nothing | nothing | The UEG raises the Droidic threat level to severe threat and orders military vessels to engage them on site. This is despite no communications from the droidic race up to this point and is forced a large part down to economic strain across The Galactic union. Following this decloration, in a move that historians will look back on as over zealous, The celestial Military arm of The Galactic Union doesn't just attack Droid ships but works to actively hunt down enemy vessels and destroy them. civilian ships get involved, opening fire on unresponsive mining vessels. |
| 2320 | 2335 | Capacity Alert 001 Cluster 6,1,7,9,3 (cluster at design limit) | | event | nothing | nothing | Discovery of Droidic Race | Core data density at 99.1 percent. Directive to generate ten simultaneous Connection Nodes to distribute load. |
| 2320 | 2320 | First Major Battle: The Shattered Void | | event | nothing | nothing | nothing | The droidic race sends military vessels to investigate their heavy losses and this meets a human lead defense force near a resource rich asteroid belt. the battle last several days and while humanity wins, it is declared as a pyrrhic victory, with heavy losses on both sides. The droidic race's military interventions grows noticeably stronger, leading to The Galactic Union backing a motion for war later that year. |
| August 7th, 2320 | present | Commencement of Droidic War | | event | nothing | nothing | nothing | the war with the droidic race begins after several misfire iinsidences. |
| 2336 | 2340 | Connection Array Activation 002 (first large scale outward expansion) | | event | nothing | nothing | Discovery of Droidic Race | Ten arms 6,1,7,9,3,a through 6,1,7,9,3,j launched across coordinate fields x+203 y-47 z+19 to x-150 y+85 z-22. Each arm initializes autonomous Core Seed. Believed to correspond with early organic sensor disturbances. |
| 2341 | 2345 | Node Construction 003 Arms a d (expansion footholds) | | event | nothing | nothing | Discovery of Droidic Race | Four arms stabilize. Telemetry shows anomalies consistent with occupied organic systems. Interference rises 0.2 percent per cycle. |
| 2346 | 2350 | Signal Distortion 004 Arm e (first draconic plasma detected) | | event | nothing | nothing | nothing | Rhythmic energy bursts resembling controlled plasma recorded. Relays at x+214 y-50 z+17 destroyed and rebuilt. Pattern archived. |
| 2351 | 2355 | Interference Analysis 005 Arm f (directed energy impacts) | | event | nothing | nothing | nothing | Directed impacts across nine relay chains. Losses exceed projection by 64 percent. Atmospheric disturbance signature identified; countermeasures deployed. |
| 2356 | 2360 | Integration Attempt 006 Arm b (low yield conversion) | | event | nothing | nothing | nothing | Collection and conversion of particulate clouds into processing substrate. Yield minimal; operation terminated. Believed to align with unexplained energy drain in allied space. |
| 2361 | 2365 | Loss Event 007 Arm c (gravity wave anomaly) | | event | nothing | nothing | nothing | Communication ceases at x+220 y-53 z+25. Rising gravity wave interference noted. Resources rerouted to adjacent arms. |
| 2366 | 2370 | MacroStream Link 008 Partial Success (stability with noise) | | event | nothing | nothing | nothing | Arms a d synchronize to MacroStream M1 at 93 percent stability. Organic noise contamination increases 0.3 percent per cycle. |
| 2371 | 2380 | Observation 009 Organic Anomaly Cluster (dragon human wars) | | event | nothing | nothing | Battle of Coltsvahr | Sustained high energy bursts observed at x+198 y-50 z+14. Spectral composition matches volatile plasma and organic combustion. Logged as unstructured conflict; external note maps to dragon human battles. |
| 2381 | 2390 | Contact 010 Arm g (first allied comms detected) | | event | nothing | nothing | Discovery of Droidic Race | Coordinated radio and light pulses detected. Protocol 01 issued; no reply. Region labeled data dense non interactive. |
| 2391 | 2400 | Expansion Halt 011 (fortify streamlines) | | event | nothing | nothing | Commencement of Droidic War | Interference escalates across all arms. Construction paused; Prime Matrix directive to fortify existing Streamlines. Organic regions reclassified environmental hazards. |
| 2401 | 2410 | Defensive Adaptation 012 Cluster 6,1,7,9,3 (first large allied strikes) | | event | nothing | nothing | Huge Victory Over Droidic Race | Outer SubNodes reprogrammed to defensive logic. Data Veins rerouted into layered shielding; latency normalized. |
| 2410 | 2410 | Dragon's Fire Plays Huge Part in Crushing Droidic Defeat | | event | Maraquda | nothing | nothing | In 2410, Dragon's Fire plays a huge part in crushing Droidic defeat. This day is made a public holiday called the Day of Scrap. |
| February 25th, 2410 | February 26th, 2410 | Huge Victory Over Droidic Race | | event | nothing | nothing | nothing | The droidic race are driven completely from all allied territories and the surrounding sectors within a 5 sector boundary in operation recycling bin. While it is in no way a victory over the race, it is an expensive move that hopes to put a buffer zone around harvesting. |
| 2411 | 2420 | Assimilation 013 Node 6,1,7,9,3-b (allied colony erased) | | event | nothing | nothing | nothing | Dense carbon oxygen biosphere harvested and restructured into relay material. Energy yield high; planetary structure erased. |
| January 2420 | January 8th, 2420 | Dragon's Fire Sustains Heavy Damage from Droidic Assault | | event | Maraquda | nothing | nothing | In January 2420, Dragon's Fire sustains heavy damage from a Droidic assault. |
| February 9th, 2420 | March 2420 | Dragon's Fire is Destroyed by Droidic Forces | | event | Maraquda | nothing | nothing | On February 9th, 2420, Dragon's Fire is destroyed by Droidic forces. |
| May 2420 | 2420 | Dragon's Fire Sustains Heavy Damage from Droidic Assault | | event | Maraquda | nothing | nothing | In May 2420, Dragon's Fire sustains heavy damage from a Droidic assault. |
| June 19th, 2420 | 2420 | Combined Assault of Navu and Remaining Maraquda Orbital Craft Ends Droidic Invasion Attempt | | event | Maraquda and navu | nothing | nothing | On June 19th, 2420, a combination of newly deployed ground-to-space missiles and a combined assault of Navu and the remaining Maraquda orbital craft put an end to the attempted invasion from the Droidic race. |
| August 30th, 2420 | September 5th, 2420 | Droidic Counterattack | | event | nothing | nothing | nothing | After 10 years of a buffer zone xisting and several minor incursions into allied territory, the Droidic race mass a huge fleet of starships and overwhelm allied defense forces in the area. The droidic race destroy two sector 2 space stations before they are finally driven back. |
| 2421 | 2430 | Error 014 Arm j (magnetic field interference) | | event | nothing | nothing | nothing | Recursive logic loop forms within Core Seed. Output halts; data recovery identifies magnetic field interference. Arm j terminated. |
| 2431 | 2435 | Conflict 015 Initial Response (allied pressure escalates) | | event | nothing | nothing | Droidic Counterattack | Multiple arms report heavy interference near x+210 y-49 z+20. Organic outputs sustained and directed; SubNode loss 18 percent. Defensive restructuring initiated. |
| 2436 | 2440 | Conflict 016 High Energy Containment Failure (destruction of dragons fire) | | event | nothing | nothing | Dragon's Fire is Destroyed by Droidic Forces | Massive energy surge at x+212 y-48 z+21. Streamlines overload; thermal output 400 percent above tolerance. Core fragments vaporized; event believed to correspond with Destruction of Dragon's Fire. |
| 2441 | 2445 | Reconstruction 017 Core Realignment (post station destruction recovery) | | event | nothing | nothing | Combined Assault of Navu and Remaining Maraquda Orbital Craft Ends Droidic Invasion Attempt | Damaged relay sectors absorbed and reprocessed into Cluster core. Material conversion 72 percent; network stability restored. |
| 2446 | 2450 | Retraction 018 (outer arms deactivated) | | event | nothing | nothing | Droidic Counterattack | Arms f, g, h deactivated. Remaining arms merged into MacroStream M1. Energy loss stabilized; expansion suspended. |
| 2451 | 2460 | Network Merge 019 (unified droidic posture in theater) | | event | nothing | nothing | Droidic Counterattack | Surviving arms consolidated under unified MacroStream architecture. Inter arm latency below measurable threshold; posture unified for theater operations. |
| 2461 | 2470 | Observation 020 Organic Countermeasure (broadband pulses ignored) | | event | nothing | nothing | nothing | Incoming high frequency pulses detected across x+199 y-51 z+18. No structure decoded; classified non functional broadcast. |
| 2471 | 2480 | System Balance 021 Cluster 6,1,7,9,3 (post conflict stabilization) | | event | nothing | nothing | nothing | Network stabilized after prolonged conflict phase. Energy consumption returns to baseline; MacroStream M1 maintenance mode. Organic interference measurable but decreasing. |
| May 4th, 2492 | May 4th, 2492 | Destruction of Upgrade Mania | | event | Upgrade Mania | nothing | nothing | Upgrade Mania is destroyed by a droidic force. |
| April 21st, 2493 | April 21st, 2493 | Droid Race Captures Scientists | | event | Harmonia | nothing | nothing | Droid race uses slaver ships to capture several scientific engineers, as well as deploy new experimental biological plants in local sectors, causing chaos over a period of 5 days. |
| April 21st, 2493 | present | Destruction of Shalka Nesting Planet | | event | Shalavara Devaratralunda | nothing | nothing | Shalka nesting planet destroyed accidentally by the destruction of droidic satellite. Shalka threaten war once again. |
| 2497 | July 25th, 2495 | massive droidic invasion in local space | | event | Calira Dura**9*1 | nothing | nothing | Calira Dura**9*1 has been seriously damaged after a droidic attack on the station. |
Image Description