IE11 is no longer supported
We do not support Internet Explorer 11 and below. Please use a different web browser.
Roberts Space Industries ®

Azure / 24A

  • PMC
  • Regular
  • Role play
  • Exclusive
  • Freelancing
    Freelancing
  • Security
    Security

I’m sad to say this, but Azure will most likely be shutting down its SC branch of things. I cannot discuss reasons here, but I bid you all adieu.

So long, and thanks for all the fish.



History

Find us on Steam: http://steamcommunity.com/groups/24Azure

Join us in Discord: https://discord.gg/014KnajODvwBfVWAJ

——————————————————————————————————————————————————————

Declassified historical records:

——————————————————————————————————————————————————————

2947-09-13: So long, and thanks for all the fish.

And as mysteriously as the 24th Autonomous fleet came into being, it vanished back into the shadows. Liquidating all assets, and obfuscating the fate of all former members…

2947-01-01: UEE Militia Mobilisation.

As a part of the ongoing UEE Militia Mobilisation initiative, Azure added a number of Polaris corvettes to its fleet. The two most prominent additions being the newly commissioned IMSV Garanzieres and IMSV Vates who’s hulls sit in an RSI shipyard. The massive commission of new Polaris corvettes puts Azure in another period of waiting for a core pillar of the fleet.

Ongoing negotiations with RSI promise up to four total Polaris under the command of the entrepreneurial organization, certainly a fine way to ring in the new year. Alongside the new capitals two Caterpillars entered service with AZHI with one under the name CSV Svipul, to be assigned to the Salvage and repair dept.

——————————————————————————————————————————————————————

2946-10-02: Azurian Heavy Industries goes public.

The name “Azure Civil Concerns” Never had much flair for a corporation. And as time went on, the shell corp became more and more of a true functioning business. With that, the civil division was given a name proper: “Azurian Heavy Industries”. This newly named Division would cover as much of Azure’s supply need as possible, while turning a profit in and of itself via outside contracts.

Two Aegis Reclaimers are commissioned under the names Huginn and Munnin by the now named Azurian Heavy Industries. The sister ships would become the core of the Salvage and repair division of the civil fleet. Alongside these two titans of salvage and repair a number of logistical ships would enter Azure service as well.

——————————————————————————————————————————————————————

2946-09-24: The Raglem is launched.

A brand new Starfarer Gemini commissioned months ago as part of the Azure fleet expansion initiative was put into service. The Raglem was meant to serve as the backbone of the military logistics arm of Azure, bringing fuel and munitions to other ships through hostile territory.

——————————————————————————————————————————————————————

2946-09-23: Azure’s new flagship.

A mil-spec Idris M frigate was officially commissioned and paid for, while contracts and negotiations for the vessel had initially been part of the fleet upgrade done in the past year, acquiring a new fresh-off-the-line Idris-M was no easy feat. The soon to be flagship of Azure was acquired by the work of the mystery investor and Antinov’s military connections, this being in addition to the Idris P also contracted from Aegis dynamics previously.

Both ships still remain under construction, however in the spirit of choosing the new flagship, the Idris-M has been named as the Razgriz, serving under the Azure identification of IMSV (Imperial Military Space Vessel). Antinov intends to use the Razgriz as Azure’s mobile headquarters and the flagship of the military fleet.

——————————————————————————————————————————————————————

2946-09-01: Weekly training exercises begin.

With a tighter network, and recruitment up, Azure begins to fly weekly training missions and simulations to build teamwork between new and old members. As well as piloting skill, tactics and increased solidarity among all actively serving members civil and military alike.

——————————————————————————————————————————————————————

2946-08-01: A new division of Azure is founded.

Finding that being purely paramilitary left Azure spending most of its income on fuel, munitions and repairs, Azure restructured to include a civilian division. This new division would grant Azure even further Autonomy in producing supplies and conducting repairs internally. Additionally, this would give the organization further cover of their paramilitary nature.

In the vein of the new corporate face, Azure had a slight rebrand to incorporate both sides. Now known as the Azure group, and consisting of Azure Civil Concerns and Azure squadron (Otherwise known as the 24th Autonomous paramilitary fleet.) This new venture would make use of the downtime of Azure’s military assets for self security and increase available capital.

Zola Suwaro was named as the overseer of this new civil division, and part of Azure’s fleet was assigned over to civilian enterprises such as logistics, mining and industry. Many new ships also entered the organisation to make up for areas lacking in their Civil division. The Azurian Bellamya was ultimately transferred to the civil logistics branch among other ships.

The new civil face would also open up the world of contract security to Azure, a very lucrative field indeed. Ultimately ACC was primarily a shell corporation, designed to keep Azure’s opperatiosn under the table.

——————————————————————————————————————————————————————

2946-06-20: The Azurian Bellamya is launched.

A civilian MISC Starfarer acquired as part of the Azure fleet expansion program is put into service. The ship was purchased fully complete, but new from the MISC corporation. As opposed to being commissioned from scratch.

——————————————————————————————————————————————————————

2946-06-15: The Azure fleet grows, but manpower lags behind.

With time, and increased funding, the number of ships under Azure’s control grows. This proves problematic though, as Azure’s fleet grew faster than their personnel. Recruiting efforts were increased to try and fill Azure’s ranks and make use of their new pool of hardware. With so much hardware just sitting in hangars, Azure was stunted for growth overall.

However Antinov planned to use access to military grade hardware as a tool to recruit new soldiers to his cause. Not everyone interested in military service would wish for the restrictions of the UEEN, but not many mercenary outfits could offer a fleet quite like Azure’s.

——————————————————————————————————————————————————————

2946-06-13: A new internal network is adopted in Azure.

With the limitations of spectrum based communications, Azure found a new independent means of communicating directly and securely. Since then, org coordination and participation has greatly increased over the old methods of communication used.

——————————————————————————————————————————————————————

2946-04-06: Azure’s funding and assets expand dramatically.

An unnamed corporate backer assisted Azure in the acquisition of over 800 million UEC worth of new and used military equipment. Included in this was the commission of two new Idris class Frigates, numerous fighters, bombers and support vessels. Azure expanded from a small paramilitary corps to a small military fleet in the span of only a few months. New training efforts began within Azure to bring the increased number of new recruits up to military standards.

At the same time, the commissioning of new military assets filled the Commandant’s time with near unending bureaucracy. Holding the keys, and with no subordinates to delegate the tasks to, Antinov had to attend appointments with many manufacturers regarding the mass acquisition.

——————————————————————————————————————————————————————

2945-10-26: The Amerissa enters Azure service.

A surplus UEE military Aegis Retaliator, the Amerissa entered Azure’s possession and service late October after an end to end overhaul. All systems were re-certified, the hull inspected and refurbished and a fresh coat of paint brought the veteran ship back to a state worthy of when she first rolled off the assembly line. The Amerissa retained its military role as a torpedo bomber and formed the backbone of Azure’s early long range strike capabilities.

On occasion, the Amerissa has also been used to carry cargo and troops, thanks to the modular design. As one of the oldest ships in the Azure fleet, it’s seen deployment on almost every Azure operation as a bomber, or mobile command post. The Amerissa would replace the aged old model Retaliator previously serving Azure’s fleet, a significant upgrade, considering their former command post was falling apart.

——————————————————————————————————————————————————————

2945-08-01: A new name, and a new mantra.

After half a year of continuing to operate as the 24th Autonomous corps, an internal name eventually stuck. The corps was then known internally as Azure squadron. This name would become the new public face of Azure. And with this new name, came the 24th’s mantra phrase “Aeternum fido semper fortis” Ever faithful, always strong. A symbol of their solidarity.

——————————————————————————————————————————————————————

2945-05-26: The cost of war proves to outweigh the rewards.

Operating independent of the standard UEE military, the 24th found securing funding and supplies difficult. Thus was started other methods of supporting the organisation. UEE funding dried up only months after the organization was put into action. Continuing to independently support the UEE was an expensive endeavour without direct UEEN funding.

Azure began to take civilian security contracts, bounties, even missions to smuggle supplies, weapons and troops on behalf of the UEE and other clientele. With this new influx Azure was able to continue on for a while. But new problems would eventually arise for the new mercenary Azure.

——————————————————————————————————————————————————————

2945-04-01: An alliance is formed.

An economic and military cooperation pact was signed with another small organization, under the spectrum ID of [Geeks]

Intelligence sharing and cooperation efforts between the two organizations commenced and is ongoing.

——————————————————————————————————————————————————————

2945-02-26: 24 Autonomous corps founded under Commandant Antinov.

The 24th was established as a small covert operations task force to function within the UEE and surrounding space. In and of itself, the 24th is not directly linked to the UEE’s military, giving it greater autonomy and the UEE deniability should anything go wrong.

Commandant Antinov [Redacted] served as a black ops squad leader within the UEE before ending his tour of duty. From there he went straight into paramilitary operations as more transparency opened up within the UEE military, limiting the effectiveness of black operations within the Military.

Aside from the service record of the commandant, little else is known about him, and he seems to prefer it this way.

——————————————————————————————————————————————————————

Manifesto

Who and what we are:

The 24th is a UEE aligned autonomous paramilitary organization, and forms the backbone of Azure. While the 24th is highly factioned and structured, it still operates as a homogeneous military entity. Personnel, vehicles and equipment move freely around the paramilitary wing of Azure. The cooperation within Azure is the main focus, creating an org second to none in terms of teamwork.

Azure is more than just a paramilitary group, however. In order to achieve true autonomy, Azure brings its supply chain and much of its funding to internal means. To this end, the 24th had its sister branch, AZ.H.I., which provides much of the cash flow needed to keep a military fleet in operation.

In Azure’s overall operations, we act as a police and military force for the UEEN, operating in parallel, but outside the normal UEEN jurisdiction. With such autonomy, comes the ability to do things a regular military force could not. And with the power of autonomy, comes great responsibility to match.

Autonomy is not only limited to Azure as a whole, but given inside its ranks as well. Officers and pilots alike enjoy many freedoms not allowed by the UEEN, and likewise greater responsibility in tandem with their freedoms. Azure officers are held to the highest standards of leadership, strategic prowess, and moral compass.

Non officer members are similarly held for high standard of skill and ability to operate without their hands being held once fully trained for their roles. Piracy, acts of terrorism, economic attacks or other black area activities are strictly regulated and/or restricted. Black area activities are only performed in instances where it directly benefits the UEE and other allied entities.

Our Vision:

Azure is engineered from the ground up to be a strong paramilitary force working in parallel to the UEE. Azure is to be a force of well trained, skilled individuals who all work together in a tight knit and mostly homogeneous organization. We will strive for internal self sufficiency and autonomy in fuel, munitions, supplies and funding. To that end Azure has both a paramilitary and a civil-commercial branch in its integral structure.

Our end goal is a strong, tight knit “medium” sized organization. Azure will be large enough to field a sizeable fleet, but not so large that members become utterly insignificant and reduced to “just a number.” We aim to build a solid base of operations along the border of UEE and low security space to maximise our operational abilities and opportunities.

Our leadership will be strong, well connected, skilled and meet and coordinate regularly to ensure Azure functions as a smooth, homogeneous entity. Likewise members will be trained and brought into this entity. Together, we will all make a name for Azure, one that will be recognised from end to end of the known galaxy.

As Players:

As players we strive to be a close and dependable community that gives our members the freedom to pursue all aspects of the game, while receiving support from the organization, and an opportunity to pool resources to get farther than one could alone. Our main goal is to offer the support of a full organization without restricting people by overly harsh rules.

Our charter is simple but fair and intended as a guideline more than a hard set of rules for most cases, encouraging cooperative play from those who already seek it. As it stands we are not exclusive, and are fine with others being affiliates in other organizations, so long as it doesn’t harshly interfere with participation with our operations and goals.

We seek mature individuals without elitism and with a strong sense of community and camaraderie, who don’t need policing to behave and help out when they can. Any major org wide decisions will have all members allowed to weigh in and vote, and their inputs will always bee considered.

Star Citizen isn’t the only thing Azure as a group is interested in, we try to be a multi game group and welcome those who want to play outside SC. Our player-base has a broad interest, ranging from other space sims, to FPS games and even tabletop gaming. We also encourage socialising outside gaming in our group, all for the interest in maintaining a tight knit community of friends.

Charter

While operating within UEE space, members of the 24’th should behave as typical UEE citizens so as not to attract a negative light to Azure. Keep a professional attitude, and all internal affairs internal. To all outside entities, we should appear as though just a normal corporate entity. Internally Rank should be respected and your fellow Squadron mates treat with respect and dignity, they above all else are your comrades.

Core Rules.

Behavior:

  • Do not be a Dick.
  • Be constructive and contribute.
  • Treat your comrades with respect.
  • Treat other citizens with appropriate respect.
  • Listen to the chain of command.
  • If you have an issue with an officer sort it out with them or ask another officer to help.
  • Maturity is valued in our members, childish behaviour is frowned upon.
  • We are primarily PVE, so keep that in mind, however pirates are fair game.
  • Role-Play is encouraged, but not mandatory, if someone isn’t interested, don’t force them.
  • Do not be afraid to ask your comrades for help, and make sure when you can, you help others.
  • The 24’th is a military structured organization, but combat is not our only focus.
  • You are representing us all out there, please try to cast a good light with the image you project.
  • Do not be a coward, if a comrade needs help, don’t run away for your own benefit.
  • Conversely, do not try and force someone into suicide to help you, if it’s hopeless for you, but not your ally, don’t drag them down with you.

The Rankings and Chain of Command:

Respect your superiors and they shall respect you. If an officer asks you to do something within reason, try to do it, as an officer, they should only ask of you things you can accomplish and things that will help our group, if you feel a superior officer is taking advantage of you, please contact your division leader. Chain of command is important in a structured community.

Ranks are treat not just as guild standing, but are also taken into account for roles and have responsibilities. As an example, a Captain really is a captain and must be in charge of a crewed ship to hold this rank. Commissioned officers are in a command role. Do respect ranking officers, as they have worked hard to attain their position. Having a large ship doesn’t automatically entitle you to being a Captain, it is an earned position in which you will be managing a crew, likely of real people, and the position should be treat with respect and not abused.

Promotions will be handed out based upon merit of action and longevity of service, and you should not try to bug or guilt an officer into giving you one. If you feel you’ve been overlooked, sit down with your wing captain and discuss it. Ranks up to Commander can also be assigned by a ship captain if you work under them.

High ranking positions in the Organization will be by application, and decided by voting of the existing brass. High ranking positions can be revoked if you are found to not be upholding the position or abusing power. High ranks are not just for show, and come with responsibility, keep that in mind when asking for a higher rank.

The Ranks:

  1. Cadet: Cadets are new recruits yet to prove themselves and move up within Azure. This can indicate probationary status.
  2. Regular: Regulars are fully established or members who have passed through the basic ranks.
  3. Elite: Elites are those who have proven their merit, and begin to take on more duties and minor command roles in some cases.
  4. NCO: Non Commissioned officers are the lower ranking junior officers within Azure. taking on leadership roles aboard ships and small teams.
  5. Sr. NCO: Senior Non Commissioned Officers are proven officers within Azure, They will often be the second in command aboard ships, or in charge of larger groups. Sr. NCOs are allowed to vote along with other Org Brass.
  6. CO: Commissioned officers are part of the Azure top brass, and hold leadership positions within the org. These officers range from Captains of ships up to division leaders.
  7. Commanding Officer: Commanding officers are active Org administrators and leaders. Positions as a commanding officer are not to be taken lightly by either those who hold them, or subordinates.
You may refer to the entire range of internal ranks here: LINK
  • Recruitment Officers are officers who handle recruitment and any applications or interviews within Azure.
  • PR Officers handle org branding and other public relations specifically.

An officer is always permitted to request to be returned to normal status, if they believe they cannot continue in their role. Please do not try to bug superiors for a promotion, unless you really believe you are being overlooked, if so notify your wing captain and it will be looked into.

Economics and Assets.

Ships and other vehicles within Azure:

All members of Azure have the option to voluntarily submit their ships to the org fleet. Any personally owned ship submitted like this will be taken care of financially from crew to maintenance and even insurance costs. In return the ship will be put to use within Azure, including when its owner is not online. Ships submitted in this way can be withdrawn, though original components will be provided in place of upgrades applied at a cost to Azure.

All ships given to the org will remain the ultimate property of their purchaser. (referred to as the acquisitional agent/officer), though they will fly in Azure colours, and with an azure designation. Naming of larger ships is up to the acquisitional agent, though some names may be rejected if in bad taste. A ships name that reflects badly on the org is a violation of the cardinal rule of behaviour. Other vehicles and equipment can be likewise put into the org’s pool of assets as well.

Further information on the logistics of this is still forthcoming, so this will be subject to change as the game develops.

Profit Sharing and Missions:

We do not believe in taxation of our members. Any funds not obtained through Azure working as a group are strictly donated on a voluntary basis. These contributions to the org bank will be tracked and investors given some say in how their investment is used. Funds put into the org bank are for the benefit of the org as a whole, and will be used in ways that benefit the majority.

Most work within Azure will be handled via the in-game mission system CIG is putting in place. Jobs will be posted up for members to sign on for in terms of smaller routine operations. We hope to have the mission system able to fully take care of profit distributions and allocations of repair and maintenance funds. How it will play out remains to be seen as of this being written.

For larger missions the in game missions system may not be able to effectively handle, these will be handled more internally, with possible assistance from the mission system. This will evolve alongside the game.

Organization Hangar:

Ships entirely owned by Azure (with no acquisitional agent putting their personal funds into their purchase) will be assigned as needed and seen fit by command. Smaller craft such as fighters and gunships and mini-haulers will likely move around a lot, and have upgrades applied generally or per-mission. Larger ships may be assigned a captain and upgrades will be at the discretion of them and superior officers.

Smaller ships will be available as loaners for members currently lacking a ship for a mission or who have lost their ship and need a boost to get back on their feet. These loaners will be provided free to all members on org business.

Out of Game.

Real Funding:

Any cash funding provided for needed services such as web-hosting, VOIP servers or other game servers will be paid for by org founders. By no means will Azure ever ask for real money from members. Members who wish to voluntarily contribute to upkeep costs should contact Antinov in private.