Ships and Crews - FastTrek Docs

Star Trek® Fleet Command has a plethora of ships and officers to choose from, each with their own particular abilities. Not every crew can manage every task, so the FastTrek Bot allows you to quickly swap the ship and/or crew.

Ship and crew are saved with each Automation Profile, so you can be sure that each task is executed with the right ship and crew combination.

Swapping Ships

When setting up a Ship Automation, you can select the Ship to use. The list is automatically populated based on what is available at your ops level.

For example, at ops level 28 you will have theoretical access to a Saladin, but not to a Rotarran. The list will automatically grow as you progress.

Notes on selection:

Some ships cannot be uniquely identified by name, and the highest power available ship will always be chosen.

For example, if you own both a U.S.S. Enterprise (Epic 3*) and a U.S.S. Enterprise-D (Epic 5*), the Enterprise-D will always be chosen, because there is no unique way to identify the 3* by name.

However, if your Enterprise-D is currently assigned to another dock, it won’t be available in the ship selection. In that case the 3* Enterprise will be selected instead.

Swapping Crews

FastTrek uses Officer Presets for selecting crews.

When you first try to assign a crew, you will notice that the drop-down menu is empty.

Click the cog icon within the drop-down menu to open a small dialogue from which you can ask FastTrek to populate the list with your current named presets.

These will then become available for you to select from.

Officer Preset Naming

I strongly recommend using clearly legible unique names that vary in more than one character. Avoid numbers and ambiguous characters like 1,I,l,Q.

If you see incorrect crew swaps, try changing digits to written numbers, e.g.:

• Armada1 -> MADA ONE
• Armada2 -> MADA TWO
• Armada3 -> MADA THREE

Crew Un-Availability Policy

It is your responsibility to ensure that the selected crew is actually available to select at the time the automation runs, especially if used in conjunction with Scheduling.

The same policy applies if crews can’t be found, for example because you renamed them.

To safeguard against automations running with improper or incomplete crew, have a look at the new Settings > Ship Behaviour > When Crew Unavailable to influence behaviour.

By default, it is set to ‘Continue’.

Continue

When the policy is set to Continue, saved crews may be applied partially. It is the equivalent of confirming the “Unavailable Officers” message shown by the game. The automation will then continue as if the crew had been applied correctly.

The problem is that the game will show this popup both when crew are genuinely unavailable (they’re deployed or on Away Teams), but also when they’re on another docked ship.

Abort One

When the policy is set to Abort One, the crew swap is cancelled and the ship is stopped and a corresponding notification will be shown.

In addition:

• If the ship is an Armada Leader, its support ships will also be cancelled.
• If the ship is the target (lead) for a Cerritos automation, the Cerritos will also be cancelled.
• If the ship is the target (lead) for a Hunter Bait automation, Hunter Bait will also be cancelled.

But:

• If the ship is an Armada Support the Leader will continue without this ship.
• If the ship is a Cerritos, the targeted ship will continue without support.
• If the ship is a Hunter Bait, the targeted ship will continue without support.

Abort All

When the policy is set to Abort All, the crew swap is cancelled and the ship is stopped and a corresponding notification will be shown.

Just like with ‘Abort One’, leaders will cancel their supports.

But in addition, ‘Abort All’ will also cancel the entire group of ships:

• A Solo Armada Support will cancel the lead ship and all other supports.
• A Cerritos will cancel the targeted ship only if linked mode was also selected.
• A Hunter Bait will cancel the targeted ship.