Unlikely Company / UNLKLYCOMP

Unlikely Company started the way the best crews do—strangers becoming friends through shared chaos, close calls, and missions that probably shouldn’t have worked but somehow did.

We’re a group of experienced players across EU, SEA and AU timezones who wanted something simple: people to fly with who know the game, respect each other, and actually show up. No drama. No egos. Just good gameplay and good company.

We’re not trying to be the biggest org in the verse. We’re building a crew that feels like the bros we played with when we were younger—the kind of players who help you troubleshoot at 2am, laugh when everything goes wrong, and still want to run it back tomorrow.

If you’re looking for a place where experience matters, where people teach each other instead of gatekeep, and where we balance organized ops with genuine fun—you might be one of us.

We take the game seriously. We don’t take ourselves too seriously.

Welcome to Unlikely Company.

Organization Charter

Mission Statement

We are a community of experienced Star Citizen players focused on building a skilled, respectful, and organized team. Our primary goal is to create a stable gameplay environment where members can rely on each other’s technical knowledge, game expertise, and professionalism.

Target Membership

Geographic Focus

• Primary regions: South East Asia and Australia
• Timezone alignment: UTC+7 to UTC+11 (covering SEA and AEST)
• Exceptions may be granted for players who can consistently participate during these hours

Experience Requirements

• Minimum playtime: 6 months to 1 year of active gameplay
• Demonstrated understanding of core game mechanics
• Familiarity with current game bugs and workarounds
• Exceptions considered for players who show exceptional aptitude or have transferable skills

Technical Competency

Members are expected to maintain systems capable of stable gameplay:

• Ability to troubleshoot common PC issues (crashes, performance, connectivity)
• Clear audio setup for voice communications
• Stable internet connection suitable for group play
• Understanding of Star Citizen’s recommended specs and optimization

Organizational Hierarchy

Rank is determined primarily by tenure (time as an active player and org member), with recognition for demonstrated skill and contribution.

Rank Tenure Responsibilities

Founder/Master 10+ years Strategic direction, final decisions
Expert 2+ years Mentorship, conflict resolution, recruitment approval
Veteran 1-2 years Lead operations, train newer members
Experienced 6 months – 1 year Full participation, voice in org decisions
Recruit/Regular 0-6 months Probationary period, learning org culture

Tenure is measured by active participation and active time, not calendar time alone. Extended absences may affect rank progression.

Code of Conduct

Respect

• Treat all members with courtesy regardless of gender, background, or skill level
• Avoid language or behavior that makes others uncomfortable
• Disagreements should be handled calmly and privately when possible
• No harassment, discrimination, or targeted negativity

Communication Platforms (Discord, TeamSpeak, etc.)

• Noise Suppression preferred in group channels to reduce background noise
• Keep comms clear during high stakes operations—save casual chat for downtime
• Use appropriate channels for their intended purpose
• No excessive shouting, mic spam, or disruptive audio

Gameplay Conduct

• Honor commitments to group activities (of course IRL duties come first, this is a video game)
• Communicate if you need to leave unexpectedly
• Share knowledge about bugs, workarounds, and mechanics with the team (Documentation preferred)
• Report game-breaking exploits rather than abusing them
• Support newer members in learning the game

Technical Standards

• Maintain your system to minimize crashes during group play
• Test audio quality periodically
• Keep Star Citizen and drivers reasonably updated
• Notify leadership if ongoing technical issues prevent participation

Bug Knowledge & Game Mechanics

A core value of this organization is technical competency. Members are expected to:

• Know common bugs and their workarounds (character resets, inventory issues, ship claim bugs, etc.)
• Understand game mechanics deeply enough to teach others
• Troubleshoot issues before asking for help (check Issue Council, community resources)
• Share discoveries with the org when new bugs or solutions are found
• Document recurring problems to help the team adapt

Membership Policies

Joining

• Application reviewed by Elder or above
• Verification of experience and timezone compatibility
• Interview or trial period with existing members
• Probationary period as Recruit (typically 1-3 months)

Exceptions

Geographic location and experience requirements may be waived when:

• The applicant demonstrates exceptional skill or knowledge
• They can reliably participate during SEA/AU hours
• They are vouched for by a Veteran or higher

Exceptions should remain rare to preserve the org’s core identity.

Removal

Members may be removed for:

• Repeated violations of the Code of Conduct
• Extended inactivity without notice (6 months of no activity)
• Behavior that damages the org’s reputation
• Refusal to maintain technical standards for group play

Note: There is a difference between “refusal” and “inability” as economic systems around the world are volatile and people have different placements in their societies.

Inclusivity Statement

This organization welcomes players of all genders and backgrounds. Our focus on specific regions and experience levels is practical (timezone alignment, gameplay readiness), not exclusionary. We judge members by their conduct, contribution, and commitment to the team.

This charter may be amended by Founder approval with input from Elders.