A Brief Introduction
The Archives have gone through quite a few revisions from its original form, and probably will go through several more as time goes by. The goal here is to let our AF Members know their history, and have it written down somewhere for future reference. Not everything is listed down, and it is told from an AF point of view, but it should offer a glimpse of some more Arcadian History that you may not have known previously.
5| Return of the Past (SVC & TC War)
SVC when arriving had every intention to hit out of sector like they normally did, however the ally they came with, TC, was an insecting alliance, and Rank #9. By their first day in Sector 1300 they had crushed DCD, being on the same planet, and hit an ARC·2 fleet. This led to fighting back from other ARC·2 members, and assistance from SVC.
|
SVC when attacking ARC·2 on 1303 mainly used blitz fleets which were hardly effective and where they were dying in almost every base. This led TC to start basing whom had several members who were, admittedly, extremely skilled snipers. Much of the base program that ARC·2 had implemented was in response to previous blitz attacks, and the bases handled poorly to snipers. Due to TC's high rank, and SVC now at Rank 24, ARC·2 had no way to fight in FvF, and were being crushed by TC base-wise. With the espionage event (Zeals, Sico Turrets) approaching, and TC & SVC not willing to have a ceasefire for the event, ARC·2 made the historic move of jumping out of 1300 temporarily. The move, although motivated by the event, was an after-effect of the merge of ARC·2 and ARC·3 whom were more comfortable jumping already.
6| The Pursuit for Sector Unity
Upon returning to 1300 after the event, many in ARC felt that they had been abandoned in 1300 by their sector, and their allies. DCD, which had been ARC's primary ally up until this point (ECHO often jumped from sector to sector) had been crushed by TC and still refused to fight back or help ARC at all. Upon arriving in 4300 when leaving Sector 1300, one of the first things ARC did was go to DCD's representative in the alliance with every intention of breaking off ties entirely. However, due to his reasoning otherwise, ties were mostly neutralized but remained partially intact due to the help of a few DCD members whom were violating DCD leadership orders against action.
|
As for Sector 1300 however, the idea of abandoning one of the core principles of ARC·2, being unified Sector 1300 defense, was out of the question for many of the officers and members despite the lack of help. Instead, ARC's leadership pursued a stronger path towards sector defense. Many of the large, and even developing, alliances were asked for a mutual defensive pact with the idea of "Defense of Sector 1300 against Foreign or Domestic Threats which mean to harm its inhabitants in any way." This model soon became the foundation for the Arcadia Federation.
The pursuit for a strong Sector Unity strengthened ARC's standing among other 1300 alliances, other than DCD whom was ignored and whose leader was becoming increasingly hostile towards ARC. It also managed to create hostilities with non-Sector 1300 alliances and alliances insector who didn't approve of ARC's 'carebear' ideology. The idea of Sector Unity although successful for those who participated, only served to isolate those who refused, as represented by alliances such as DCD. In the end this meant limited success other than with a set few alliances; the largest of whom were: ECHO, WWR, URTB, VA (EVOLV) and later ABYSS.
The pursuit for a strong Sector Unity strengthened ARC's standing among other 1300 alliances, other than DCD whom was ignored and whose leader was becoming increasingly hostile towards ARC. It also managed to create hostilities with non-Sector 1300 alliances and alliances insector who didn't approve of ARC's 'carebear' ideology. The idea of Sector Unity although successful for those who participated, only served to isolate those who refused, as represented by alliances such as DCD. In the end this meant limited success other than with a set few alliances; the largest of whom were: ECHO, WWR, URTB, VA (EVOLV) and later ABYSS.
7| The Creation of ARC·T
ARC·T was already in existence by the time ARC·2 & ARC·3 had merged. For the most part though because of the events leading up to the destruction of ARCAD, primarily that of a rogue leader, leadership was not handed to a person in specific. Leadership was held by an alt of Tony Mai and Hellrazor was kept as a de-facto leader. Many officers in ARC·2 also kept their alts in ARC·T to help out without directly moving their mains. This led to a situation where there was no dedicated support or assistance from ARC's leadership.
|
After several weeks of a highly ineffective ARC·T, and the merge of ARC·3 a new strategy was adapted. The new strategy involved Hellrazor moving back to ARC·2 (he had previously asked to return around a week earlier), and Kamina being placed in charge of ARC·T. Due to the fact that Kamina was the original leader of ARCAD, there wasn't a fear of him committing a coup against his own alliance and he was given nearly complete autonomy. Base testing became mandatory in order to move up to ARC·2, players had to have a minimum of 50 medals, and they needed to be level 30. The primary ARC alliances were prohibited from direct recruiting in order to prevent potential spies, which in the past had been compromising ARC group chats and intel.
ARC·T managed to serve its purpose and met the qualifications it was required to handle. However those same qualifications require an isolation of ARC·T from the rest of the alliance. Due to ARC·T's granted autonomy, it became almost its own branch of ARC with self-promoted officers which weren't represented in ARC's government at all; mainly because they were appointed through a different system. However, because ARC·T was performing as it was needed to, the major ARC government took no steps to end isolation stating it as a "necessary sacrifice." Throughout time this led to several incidents and a point of tension between ARC's leadership and the future ARC·T graduates, especially as they rose into positions of power.
ARC·T managed to serve its purpose and met the qualifications it was required to handle. However those same qualifications require an isolation of ARC·T from the rest of the alliance. Due to ARC·T's granted autonomy, it became almost its own branch of ARC with self-promoted officers which weren't represented in ARC's government at all; mainly because they were appointed through a different system. However, because ARC·T was performing as it was needed to, the major ARC government took no steps to end isolation stating it as a "necessary sacrifice." Throughout time this led to several incidents and a point of tension between ARC's leadership and the future ARC·T graduates, especially as they rose into positions of power.
8| Growing ARC Influence (2nd Se7en War)
ARC's pursuit for sector unity hit its highlight during the 2nd Se7en War. Se7en had been an ally to ARCAD initially but did not see them as an ally, and as such attacked them when arriving in 1400. During the conflict, many of the 1300 alliances which ARC had pursued relations with assisted, even several SIN members who were a Top25 alliance at the time. Combined, Se7en was held off at the portal in stark contrast to SVC just a few months prior. By the time Se7en left 1400, many in ARC considered it a victory and proof that the idea of a unified sector defense was possible, and could be effective against large alliances.
|