Common mistakes

What happens if I make a mistake?

It depends on the patience level of the commander, and the severity of the mistake you made. Some commanders have the ethos 'If I boot them they'll learn that their mistake was wrong'. Some commanders have the ethos 'I'm pissed off and I'll boot anyone who doesn't do exactly what I say'. Some commanders have the ethos 'Whatever, it's just a game'.

Most of the time commanders fall into the third category. Generally you don't have to worry about getting booted unless you really stuff the team up, or really piss the commander off personally. Furthermore, new players with a rank of 4 or less are protected from booting by the Rules of Conduct.

If you are booted from a game you can join a different game, or log out of ASGS and log back in with a different callsign to rejoin the same game (sneak back in with a fake nose and a mustache, as it were).

Mistakes that will get you banned

Spamming Voice Chats

• Allegiance uses a system of short radio messages for teammates to communicate with each other. Using these constantly and ignoring requests to stop can lead to a ban.
• About 20% of all bans that are given out are given to players that are spamming.
• If you want to practice memorising which key combo relates to which VC, go to an empty server, or the Training Missions, or somewhere else where 50 people don't have to listen to you.

Mistakes that will annoy your teammates

Dropping probes in front of the red door

• The red door of the base is the exit door, by dropping probes in front of it you cause everyone exiting the base to bounce off it, which is infuriating.
• Doing this on purpose is against the RoC and will get you banned.

Using the VC 'Need better weapons'

• or 'Need better fighters' when the team already has advanced tech.
• Don't use these if you can't tell the difference between a Heavy Interceptor, a Basic Scout, and your elbow.

Broadcasting useless information to the entire team

• There is a minimap which displays all ship information for the entire map. An experienced player can read it far faster than you could ever type it in.
• Saying things such as 'There are two enemy scouts in Rigel', 'There is an enemy bomber in Aeroflex' is ... pointless.

Asking for ships that cost money

• Several ships in the game cost money every time you want to fly them. Since the commander controls the team's money you need to petition him for the money and he can choose to approve or deny your request.
• When you pilot one of these ships you are a walking team investment and it is critical that the money is not squandered.
• Avoid asking for these ships if you are unfamilar with how to use them - read how to use them in the F1 menu or on the Allegiance Academy, and then practice on the Newbie Server first.
• The exception is rescue probes for Scouts ($250 or $100 each) - commanders love pilots that drop rescue probes.

Continously spamming the commander with 'Buy Ship' requests will probably result in you getting booted from the game.

Jumping on turrets when not wanted

• Several ships have turrets which other pilots can board and use to defend the ship.
• However, sometimes pilots will not want turrets - they might be going on a stealth run, or would prefer you defend them with some other ship.
• Generally, if a player isn't using the 'I need turret gunners, NOW!' Voice Chat then they don't want gunners. They may also use the 'Get off my turrets, man' VC to tell you exactly what they want.
• Changing ships or stations will remove you from the turret spot, or if you're already in flight pressing ctrl-shift-d three times will eject you.

Mistakes that are detrimental to your team's success

Not shooting nans

• During an enemy attack nans will try and keep the main attacker (bomber, troop transport, constructor, etc.) alive. It is crucial that you attack the nans first because any damage you attempt to inflict on the main target will be instantly repaired.
• The commander will reinforce this by sending the VC 'Attack Scouts!' or 'Attack nanites!'

Not carrying a nan when possible

• Some commanders assume that any pilot flying a ship which can mount a nan is carrying a nan.
• During an emergency he may send ships (normally miners or constructors under attack) to the closest such pilot for repairs.
• If you don't have a nan and the ship dies because you were unable to repair it he is going to be annoyed, and may boot you.
• Note: Nearly all Belter ships can carry a nan.

Stopping a friendly constructor from building

• If you are too close to a friendly con it will think you're on a collision course, and try and avoid you. This can delay its building time allowing the enemy the precious seconds needed to destroy it.
• If you are defending a con stay about 400m away unless you have to get closer.

Not stopping an enemy constructor from building

• Constructors have to line up on an asteroid exactly before 'diving in' and building the base.
• By ramming it's nose or tail, you can swing it around forcing it to attempt again, buying your team precious seconds to destroy it.
  • You can do this from within a pod as well, but it will destroy your lifepod quickly (which can be a good thing sometimes).
• Note that they will not automatically avoid collision like friendly cons do.

Mounting sheilds and missiles on a stealth ship

• Both sheilds and missiles raise your radar signature, making it easier for the enemy to spot you - defeating the purpose of a stealth ship.
• You can place missiles and sheilds in cargo when you're not using them by pressing ctrl-5 and ctrl-7 respectively. You mount them again the same way.
  • This requires a spare slot in cargo.

Flying to another pilot that is trying to stay hidden while you are eyed by the enemy

• This is the same as above, except it is your teammate that is trying to stay hidden, not yourself. Examples include Heavy Troop Transports, Teleport Scouts, and Stealth Bombers.
• You can tell who is trying to stay hidden because they won't have sheilds mounted. Either stay away, or take off your own sheilds and missiles.

Ripcording to an Assault Ship

• An assault ship is an expensive capital class ship which uses stealth to infiltrate the enemy sectors, then acts as a teleporter for a bomber or htt or capship attack. By teleporting to it early you will almost definetely be spotted, and the enemy will trace you back to the assault ship, resulting in its destruction.
• Always be careful about which sector you are ripcording to. This is what the assault ship looks like on the minimap, avoid the sector that it is in.

Some commanders will boot pilots who give away the positions of ass ships, HTTs, TP scouts and/or sbs, with little to no warning.

Ripping to Rix SR scouts

• Rixian Unity has a unique ship, the Small Rip scout which other scouts and fighters can teleport to. However it only has enough energy for one such ship every 30 seconds or so. Because of this it is vital that the pilots that do teleport in are capable of helping the SR pilot with the task he is undertaking.
• Teleporting a basic scout to an SR which is trying to kill an enemy miner is not helpful. Teleporting a fighter is.
• If you don't know what you're doing, avoid teleporting anywhere when you fly for Rix; the exception being if you're sure you are teleporting to a teleport base (which have infinite energy).
• In fact, the most useful thing you can do if you are inexperienced is fly an SR scout yourself, and hope that an experienced player teleports to you when/if you get into trouble.

Pod killing

• Why do people tell me not to kill pods?

Not picking up friendly pods

• Picking up teammates who are in a lifepod transports them instantly back to base, where they can immediately launch to help defend, attack, or whatever again.
• By ignoring friendly pods you are handicapping your own team, because the players in the pods are unable to do anything useful.
• If you pickup people often, they are more likely to remember and pickup you when the situation is reversed.

Not Probing

• Probes are dropped by scouts to spot enemy movements when no one is in the sector.
• If no one probes then the enemy will always surprise you, always have the upper hand, and your team will lose. This is a fact.

Mistakes that will get you laughed at

Dropping probes directly in front of alephs

• When scouting you drop sensor probes to detect enemy movements later. But by placing it in such an obvious place as the "entrance" you make it easy for the enemy to spot and destroy.
• Place a probe (or two) around the sides or back of the aleph instead, anywhere from 500-1000m away.

Nanning piloted Phoenix ships

• Phoenix piloted ships cannot be repaired - nans have no effect on them.
• Attempting to nan them is a waste of time.

Following scouts through alephs

• Scouts often carry proximity mines which they attempt to drop in front of enemies, causing them to plow into them and explode.
• By dropping them on the "exit" side of an aleph they ensure that you can't avoid them. Following a scout full speed through an aleph is tantamount to suicide.
• Avoid dying by going through the aleph slowly, and/or wait till the mines expire before entering.

Using Gat and nan on GT scout

• Ga'Tarran Federation scouts are unique in that they can carry a gattling gun and a nan at the same time. Firing both at the same is pointless though, because you will be both damaging and repairing your target, with a net effect of nothing.
• Activate one or the other by pressing 1 or 2 on your keyboard. You can toggle firing all weapons again by pressing the same button again. This is covered in Training Mission 3.

Scouting with ints/figs

• At the beginning of the game the map is unexplored and you only have a few tasks to choose from.
  • Explore the map with a scout
  • Defend the miners or constructors with a nan, interceptor, or fighter.
• Exploring with an interceptor or fighter does not work because their scan range is very low.

Whining on the forums

• Sometimes a new player will come on to the FreeAllegiance Organization forums to rant and rave about some imagined slight, making outrageous demands and threatening to 'leave'. Or they make a topic about how great they are, a certified genius if you will, and how everyone should bow down to them.
  As in real life, whining and boasting irritate people, so don't expect anything different on our forums.

Trying to dogfight someone vastly superior

• Even though you have played a lot of FPS, you will be nothing more than cannon fodder for quite some time.
• Try to perform tasks which don't involve attacking the enemy, such as probing and nanning. To do this you'll be in a scout, and scouts are faster, more manuevarble, and stealthier than most other ships anyway, so you'll be able to survive longer (hopefully).
• If you do want to try and improve dogfighting try and only take on other newbs. Try and ensure that you have a ship built for dogfighting - either the Heavy Interceptor, or the Advanced Fighter. Avoid people with a squad tag attached to their name - exception being Cadets, who will have an @CDT tag.

Asking 'Can we start the game' when the game is already in progress

• When you join a server you will be put on NOAT (Not on a Team). Simply select a team and press join to start playing.

Asking to be commander during Prime Time

• As with the military, you need to be a good Private before you can become a good General
• Unless you have a solid reputation as a player who understands all of the roles in the game, no one will fly for you.
• Asking to command a team when you don't yet have the experience to even be a good pilot will annoy other players (apart from on the Newbie Server, obviously). Almost all new players don't understand the game well enough to make for good commanders.
• If you want to build experience commanding, ask other similarly-skilled players to join you in a private server for a 1-on-1 commander training game. Or, use R4's new "solo game" mode to explore the tech tree and learn how to manage your miners and constructors.

Getting started	Intro: Overview · Top 10 things you should know · Newbie games Installing: Quick install · Step by step guide · Troubleshooting Gameplay: Learning guide · Common mistakes · FAQ · Training index