| Start date | End Date | title | Category | type | Places referenced | People Referenced | Description |
|---|
| February 1955 | February 1955 | First contact between the Vacus and the Droidic race. | | event | | | 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 | | | 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 | | | 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 | | | 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 | | | 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 1961 | March 1961 | Error: Connection node 9, 3, 4, 7, 5 block | | event | | | 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 | | | 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 1st, 1965 | July 10th, 1965 | Large structure cloaking technology perfected. | | event | | | The Vacus develop a new cloaking technology designed to make large structures invisible to Droidic sensors. This technology does not affect smaller ships. |
| April 1st, 1969 | April 22nd, 1969 | Empress Xylaris slain; Queen Kallara ascends. | | event | | | During an internal struggle, a rival queen, driven by a hunger for power, challenges and kills Empress Xylaris in a direct confrontation. Queen Kallara ascends to leadership, her ferocity making her a dominant ruler. |
| November 1st, 1975 | November 30th, 1975 | New energy shields deployed. | | event | | | Queen Kallara orders the development of a new type of energy shield for Vacus structures, bolstering their defense capabilities against potential threats and environmental hazards. |
| August 1st, 1980 | August 15th, 1980 | Rich mineral deposit discovered. | | event | | | Vacus scout drones discover a rich mineral deposit in a remote asteroid field. The resources are deemed vital for ongoing expansion and resource needs. |
| October 1st, 1985 | October 10th, 1985 | Advanced research facility established. | | event | | | Queen Kallara decrees the construction of a massive research and development facility for advanced materials and energy technologies, reflecting the hive's focus on technological superiority. |
| June 1st, 2005 | June 15th, 2005 | Resource recycling system deployed. | | event | | | The Vacus introduce a new resource recycling system to improve their efficiency in resource management and material recovery. |
| September 12th, 2031 | September 12th, 2031 | Work on hive ship 463 begins. | | event | | | A new Hive Ship is decreed by the ruling empress. It is to be the 463rd spreader and is to travel in 3 larvi-cycles. |
| May 7th, 2040 | July 15th, 2040 | Hive Ship 463 is launched. | | event | | | The vacus launch Hive Ship 463, a huge superstructure of a ship that is unable to defend itself but rather acts like a floating city. They launch hive ships through a complex sling shot system that sends their vessels on an uncontrolable journey through a system similar to the allied rift satellites, in so far as the hive ship is sling shotted into a rift and then appears on the other side, where ever that may be. The Vacus' sling shot system is not suffisticated however, and is designed only for the hive ship's massive frames. It sends Hive ship 463 spiraling away from its home space and out to the furthest point in Vacus history. The journey of the hive ships takes 27 larva-cycles, or 81 Earth years. |
| February 14th, 2115 | February 14th, 2115 | Vacus detect humanity or possibly dragon kind. | | event | | | Hive Ship 463, now on its 25th larva-cycle picks up on the signs of another civilisation in the direction it is traveling. fearing Droidic presents, it changes course to head north around them. |
| April 22nd, 2120 | April 22nd, 2120 | vakari spotted by Hive Ship 463. | | event | | | Hive Ship 463 identifies a planet in its path. After three firebursts (days) of scanning it changes course and begins to head towards it. |
| 2125 | 2126 | Vakari colonised by Vacus | | event | | | Vacus shielded pod ships are deployed down to Vakari in order to assess viability for becoming a new colony. They begin to establish small hives on the ground and construct areas for living out of the pod ships. hive ship 463 remains in orbit, deploying defensive ships and materials as needed. |
| 2126 | 2135 | continued colonisation of Vakari | | event | | | The hive ship continues to deploy heavier construction vessels down to Vakari as the planet is further colonised. Orbital forces begin to establish a small scanning station in order to begin to search for nearby threats. Shielding units are deployed to cloak the planet from droidic forces that are suspected to be in the area. |
| June 23rd, 2133 | November 19th, 2125 | Hive Ship 463 colonises Vakari | | event | | | Over a series of firebursts, Hive Ship 463 begins to deploy colony pods to Vakari. Colony pods are small, completely isolated pods in which Vacus live their lives for up to half a larva-cycle while a planet is assessed and, if necessary, changed to make it suitable to inhabit. While this takes place, Hive Ship 463 also begins to deploy scouts, with particular focus on building a chain towards the south to attempt to identify unknown lifeforms. |
| 2139 | 2139 | continued concerns from southern signals | | event | | | Sensor readings from far distant south continue to be detected causing concern among the Vacus settlers. It is decided that automated probes will be sent to try and identify the signals. |
| 2148 | 2155 | The Vacus emergency evacuation system for Hive ships is invented. | | event | | | On the Vacus home system a method to make short jumps using the hive ships as a base is discovered where they use a significant amount of power from the hive ship to propel an emergency escape force a short jump away in order to preserve the travelers, usually a hive queen and her workers. All new hive ships are fitted out with these, although Hive Ship 463 does not have this by default. It takes the Vacus on vakari a number of years to replicate the technology after information is transmitted over long range communications. |
| 2160 | 2175 | An exploration party is launched south | | event | | | With no response from the probe sent south, the Vacus decide to risk a scientific expedition. they gather a lower hive queen, several workers, a company of soldiers and a number of scientific Vacus who begin preparing to jump south on a scouting mission. The hive ship is deployed, ready to make the boosted jump and after one practice run that was aborted due to nearly causing a core overload, the exploration party is launched southward. |
| April 2176 | July 2176 | The expedition to the south goes wrong. | | event | | | the hive ship short range jump places the Vacus exploration team in the region of modern day sector 17, but not directly south of their original position instead it has sling shotted them off to the east, requiring them to make their way back in. After three months of floundering, the crew realise the problem and accept it. they settle briefly orbiting a small star while they carry out repairs and plan out their next actions. they take this time to communicate with the hive ship and update them on the situation. The hive Ship orders them to remain in position until the home worlds can decide on the next plan of action. |
| August 2176 | August 2176 | Death of the lower queen | | event | | | the lower queen aboard the exploration ship becomes ill with an unknown sickness. With no one to replace her, upon her death, the Vacus aboard the ship become more unstable. Without a queen to guide them, Vacus are not lost nore incapable but their decisions become eratic, they rely on the queen to tie them together. As such, when the hive ship transmits orders for the Vacus to return, it goes unheeded on the ship which had descended into chaos. |
| November 2176 | November 2176 | Exploration ship assumed lost | | event | | | The Hive ship is unable to raise a response from the exploratory party and it is assumed lost. The Vacus on Vakari hold a ceremony to honour the death of the lower queen. it is agreed another exploration party will not take place. |
| December 1st, 2185 | December 1st, 2185 | Invention of short hop stargate technology | | event | | | Back on the Vacus home world, the huge research lab set up back over 200 years ago turns out its biggest development yet, a small version of a Stargate which is able to create a stable corridor between two sections of space, boosting the ability to ferry goods and supplies between local colonies. It is theorised that this may allow supply corridors to not have to avoid the droidic race mining routes any more, speeding up colony development. Disappointingly, the distances it can travel are far shorter than the sling shot sends hive ships, though the data is sent across to all hive ships over time. |
| 2194 | 2194 | the Vacus on Vakari begin the construction of a stargate system. | | event | | | The Vacus on Vakari receive the information about the latest development from the home world and immediately are able to see the use case for it, finally finding out about those signals to the south that have fluctuated significantly over the last few years. the Vacus commence the building of two stargates, one for each end of the corridor. |
| 2204 | 2204 | Completion of Vakari stargates. | | event | | | The two stargates are completed in good time. The Vacus waste several months deciding who will go though after the disaster of the last exploration mission south. the debate that rages is whether to send one or two lower queens. typically, hives like those on Vakari each have a lower queen, so to send two would mean that two hives would lose their queens for the period of the exploration. Concerns were raised if the exploration mission goes wrong again. In the end only a single queen is sent. |
| August 2211 | October 2211 | The second southerly expedition begins | | event | | | the second southerly expedition begins with the first stargate set up and the second aboard the expedition ship, heading towards the unknown signals. the trip itself is fairly short, with the second stargate reaching its destination within several weeks. the Vacus set up in modern day sector 14, and paused briefly while the corridor stabilised and resupplies were sent through. It was decided to set up a guard at the entrance point to the stargate before continuing on south. |
| 2212 | 2225 | Slow mapping of expedition space by the Vacus | | event | | | Over the next 15 years, the Vacus carry out a slow search patern of mapping around their stargate, using a radial style pattern. They do not look to settle any planets and instead are looking for resource rich asteroids and other similar treasures. They set up a network of hubs that are responsible for harvesting, processing and extracting resources of various types while expeditions continue to search around, slowly gaining ground toward the southern signals. |
| 2235 | 2235 | Discovery of Vacus | | event | | | The Vacus race are discovered for the first time. |
| February 18th, 2237 | January 15th, 2239 | Commencement of Vacus War | | event | | | the very first Vacus war began. |
| 2260 | 2260 | Maraquden Military Forces Repel Four Vacus Invasions | | event | | | In four huge battles, Maraquda orbital defense repel four Vacus attacks in as many weeks. They name each battle: Bitva Zirkovogo Vidhodu, (Battle of the Stellar Dawn) , bitva za orbitu (The battle for the orbit), Bitva Nebesnogo Flota (Battle of the Celestial Fleet) and the final battle Polnaya porazhenie (utter defeat. While maraquda orbit does suffer some of the worst casualties ever to that point in history in space, the planet still comes out in tact and it is widely celebrated as some of the finest tactical work of the time. |
| August 1st, 2401 | August 1st, 2401 | Ryuchi Fleet Outflanks Vacus Attack | | event | | | On August 1st, 2401, Ryuchi fleet outflanks Vacus attack, leading to their total demolition. Ryuchi declare it a day of victory called Mcka. |
| September 3rd, 2401 | September 4th, 2401 | Defeat of Vacus | | event | | | three hive ships, those that were the main intruders into northern allied territory, destroyed in thundering victory by allied warships. |
| October 9th, 2405 | October 9th, 2405 | Peace Treaty with Vacus | | event | | | Unable to recover from defeat after defeat, not to mention the destruction of three hive ships, the Vacus race sign a treaty for peace that puts them under heavy restrictions in allied territories and near by sectors. The treaty placed heavy restrictions on the race's ability to be able to manifacture components for deep space travel and restricted all weapon technology. In exchange the allies promosed to help with medical and food baesd aid. |
| May 12th, 2426 | present | Vacus Breaks Treaty | | event | | | After sevearl warnings are issued by humanity to the Vacus race it is discovered that Vacus leaders in near allied territory have been using medical aid to instead facilitate the building of chemical based offensive weapons. The Vacus also are discovered to having salvaged, or bought from the Kaltz-baurgan, several long range communication modules and other similar technologies from the sector 2 stations when they were destroyed. In a haze of fury, rumours and conspiracies, the humans drag the allies into declaring war once again against the Vacus. |
| 2440 | 2440 | Temreth Discovered by Vacus | | event | | | Sensors set up by the Winthrope city seem to indicate Vacus exploration and scouting crafts are starting to show up. Temreth has been discovered as feared. |
| February 22nd, 2449 | December 18th, 2469 | Vacus occupation on Winthrope City | | event | | | In 2450, Vacus attack force sweeps into the atmosphere and, with very little difficulty, slams into Winthrope city. The defensive projects prove next to useless, and it takes them an hour to capture the leaders and suppress resistance. remember that this was a city of wealthy people, not rocket scientists. The Vacus occupation of the city is light for the most part up until 2463 when pressure in other areas of the Vacus lines requires them to crack down hard on Temreth. Vacus occupation is not ended until a second city is founded and an eventual uprising occurs. |
| January 29th, 2457 | March 6th, 2457 | Winthrope city, first uprising | | event | | | Winthrope city attempts to free itself from the Vacus, using a combination of garilla tactics and all out assaults, usually lead with primitives as cannon fodder. While at the start the uprising makes ground, it is not long until superior fire power and air superiority from the Vacus lays it out flat. |
| January 29th, 2457 | March 6th, 2457 | Winthrope city, first uprising | | event | | | Winthrope city, attempts to free itself from the Vacus, using a combination of garilla tactics and all out assaults, usually lead with primitives as cannon fodder. While at the start the uprising makes ground, it is not long until superior fire power and air superiority from the Vacus lays it out flat. |
| October 1st, 2465 | October 31st, 2465 | Cresting waves established | | event | | | Frustrated by their minimal gains, Cresting Waves settles down a large handful of miles away from Winthrope, and in a fashion earily similar to the first settlers, very quickly pulls apart the ship to establish their own city. enhanced by modern technology and experienced field workers the second modern city is far easier to defend and much less hostile to natives. |
| January 28th, 2485 | January 28th, 2485 | Vacus Warriors Takeover Attempt | | event | | | On January 28th, 2485, an attempted takeover of the station by Vacus Warriors is repelled by off-duty MI officers and some very aggressive, instrument-wielding performers. The battle is nicknamed the Battle of the Trumpet. |
| February 2494 | February 2494 | Vacus Attacks Star Command | | event | | | Vacus successfully attack Star Command and begin the black star war of terror. |
| June 2494 | July 2494 | Destruction of mission central | | event | | | |
| July 2494 | July 2494 | Vacus Full-scale Invasion | | event | | | Vacus launch a full-scale invasion of local sectors, bypassing the front lines and necessitating a destruction of the star gate system. Mission Central is bombed beyond repair, and Tera Base is launched to replace it. |
Image Description