SQUADRON

SQUADRON is a command used to form and control a Squadron, or a group of small
spacecrafts. Each capital class ship has three squadron slots. How many ships
in each slot is purely dependant on the type of capital ship. The squadrons are
labeled appropriately as 1, 2 and 3.

The first step is to create your squadron. To do this, simply place small
spacecrafts into one of your hangars on your capital class ship, and use the
following command while in the bay with the ships.

SYNTAX: Squadron add <Squadron #> <shipname>
Squadron remove <shipname>

Now that you have formed your squadrons, it is time to sort them into
positions: Outer, Midguard, and Center. Positions are used to organize your
squadron into protective layers. Only ships in the outermost layer can be hit
or targeted, so it may be important to keep your vital ships in the center and
surround yourself with your squadrons.

SYNTAX: Squadron position <squadron #> <Position #>

You have formed your squadron and set its positions! From the bridge, you'll be
able to launch, control, and recall your squadrons. Scrambling a squadron
automatically opens whatever hangar(s) they are in. To recall your squadrons,
you must have the bayspace and hangar(s) open, or else your ships cannot be
fully recalled! The recall flag is toggle-able, so that if you change your mind
you can turn it off and leave them in space.

SYNTAX: Squadron scramble <Squadron #>
Squadron recall <Squadron #/all> <on/off>

The squadron AI is more advanced than traditional autopilot AI. Launched
squadrons act like the old `scramble` system and act as semi-intelligent groups
of interceptors.

With the squadron command, you can also control your squadron to just about
anything you can do as if you were on the ship itself.

SYNTAX: squadron nav <Squadron #/all/shipname> <command>
(NOTE) A full list of commands can be found on HELP NAVCOMMANDS

Squadron target <Squadron #/all/shipname> <victim/none>

In addition to attacking ships, should you position the squadron over a planet,
it will be possible to bombard the planet using projectiles. Bombarding can
perm players, and may have serious repercussions if used flippantly. Use this
command with care.

SYNTAX: squadron bombard <planet>

See Also: NAVCOMMANDS BATTLEGROUP FLEETRADAR

Recent In-Game News

Arkania Space Holosimulator Complex Opens
After several years of development and speculation, the Arkania franchise of a chain of Space Holosimulators has announced its grand opening. A representative from the business mentioned that members of the public are welcome to tour the facility, located on the south side of Adascopolis, and experience the very latest in immersive space combat simulation technology. Features are reported to include four separate holosimulator pods and integrated leaderboard tracking, so repeat visitors and hotshot pilots can duke it out for the top standing in each scenario. Each pod comes with a monitoring system so onlookers can cheer on their friends or keep an eye on their rivals. The franchise owner was quick to point out that the company is not liable for any injury or death related to fights over leaderboard standings. At the time of opening, only one simulation scenario was reported to be functional, with representatives of the parent company indicating that more are planned for future development.

(8 years ago) Fight for Freedom halts Cybernetic Advancements
Despite the Trade Federation's victory over the &061O&093uter &061R&093im &061C&093oalition and Jedi Master Seela, the Twi'leks of Ryloth remained dissatisfied. They rose up and began a campaign of liberation shortly thereafter, including Tatooine and Naboo. A series of skirmishes began, which included several bombardments and full-scale assaults. However, once the dust settled and the &060T&103h&244e &060Ga&103l&102ac&244ti&250c &060Em&103p&102i&244r&250e decided not to bother with that quadrant of space, the residents began to pick up the pieces. As they cannot live on the surface, most of the damage to Ryloth's infrastructure was insignificant. However, an industry-leading enhancement laboratory was reduced to rubble by a 'lucky' rocket. Unfortunately, this has disrupted the cybernetic supply line, leaving the galaxy left only with what was already in circulation. In a stunning development, the Worlport General Hospital on Ord Mantell was able to collaborate with some of their industrial partners to reverse-engineer and reproduce some of the more application-specific cybernetics for sale.

Recent Changes

Various Space Updates
- You can now add or remove squadron ships for a landed ship, and you can remove ships from a squadron even if they're not currently on the ship. - In space combat, being in sustained action actually caused you to receive 0 experience from destroying the target, and that's been fixed. You'll receive experience based on the value of the target ship shown on "info". - All automated squadron ship actions now depend on autopilot being enabled, so when using them in a fight, you'll generally want to ensure autopilot is on. It is still enabled automatically when scrambling any squadron. - Autopilot logic now kicks in even when a ship has players onboard. - There's a new autopilot config: useion. Rather than using only lasers or only ions, you can now toggle each one separately using this. - Squadron ships will now honor these weapon settings when engaging targets. Be sure to update the settings on your existing squadron ships. - Squadron recall now takes precedence over engaging their target. - When you add a ship to your squadrons, it will automatically enable all three weapon types and turn on autorecharge. - Autopilot and squadron ships will now fire weapons at the same ranges players can. This mostly just means they'll be firing projectiles from farther away than they currently do. - Autopilot and squadron ships can now miss based on all the factors affecting whether players miss, such as relative ship size, target speed, and distance. Previously, they'd only miss due to ship dodging. - Autotrack will no longer cause you to re-course toward your target due to "evading collision" - When any ship in a battlegroup is attacked, all of the ships in the system from the same battlegroup are now marked as fighting, meaning they will stop regenerating fuel/projectiles. - Autopiloted ships with CLANPOST enabled will now attack any ship which they see bombarding that clan's worlds, regardless of the bombarding ship's affiliation. (As long as it's not owned by the same clan as the planet; your own orbitals will not attack you for bombing your own planets using your own fleet, but they will currently attack a ship piloted by a clan member but not owned by the clan.) - Orbitals will now switch to the closest invading pirate, no longer considering target ship size as a factor in prioritizing pirate targets.

Standardizing Mob Stats and Experience
We've introduced standardized mob "difficulty levels". This will allow us to ensure that easy/medium/hard/very hard mobs are set up consistently, controlling things like their hp, attacks, and attributes in one setting. This change will largely be transparent to players, with a few exceptions: Experience gain calculations have been revised for ground combat. Fighting the same mob repeatedly will no longer reduce experience gains from it, but the number of mobs you'll need to kill in order to level has been increased toward higher levels. Our combat gyms will soon feature mobs from the first half of the difficulty scale, with the higher-end ones being tougher than they historically have been. It'll still be pretty quick to level combat there up to the low-100s, but as you approach the top end of the level range you may find that our long-ignored combat class quests will help you level faster. And also: - Fixed output of score level to actually give you a gauge of progress from your current level to the next.

On The Forums

Vote For LOTJ!

Donate to Keep LotJ Online