Subscribe to download
O.S.A. Drone Carrier 'Peachy'

”Heading for the group that had gathered near the Charmer, they passed the Peachy and the Dazzler, the Convoy’s newly modified drone-carrying ships. Box-shaped and simple in design, they had rows of exterior attachment points.”
-From The Fleet Beyond Neptune

The Peachy was one of two cargo runners that were hastily converted into drone carriers before one of the first engagements between Alliance forces and an Earther battlegroup. She can carry four drones into battle and then remote control them from her on-board control stations, or by using Rdav’s Fleet Command MKII script. She is currently carrying four Ruffian light combat drones, but any drone design of the same size will do.

The Peachy’s interior is cramped but has all the necessary life support that her crew needs for long deep-space missions. Her hybrid thruster configuration enables her to enter and fly in an atmosphere, and then launch back into space. In case her crew must make repairs without having available components, she also carries a refinery and assembler.

Drone Launch Procedure:
1. Go to Toolbar 3.
2. Press [3], [4] and [5]. This activates the batteries, turrets, script and antennas.
3. Check bottom-left corner of interface LCD-screen. If the leftmost number is not 4, or is flickering, recompile the programmable block named “CENTRAL_COMMAND”.
4. Press [6] and then [1] to launch the drones. Alternatively, select the ship on the interface screen by pressing [Q], and then click on the icon in the lower right corner by pressing [E].
5. When the drones have launched, press [1] again to make them form up around the ship.

Drone Recovery Procedure:
1. Go to Toolbar 3.
2. Press [6] to use the interface screen.
3. Select the drones by pressing [Q] on them, and then hover the cursor over the ship icon until it becomes a purple icon. Press [E] to order the drone to dock.
4. Remain stationary and wait for the drones to dock (you may have to roll and pitch to help them).
5. When all drones are attached, press [F] to return to Toolbar 3. Then press [5], [4] and [3] to deactivate the drones and script.

General characteristics:
▪ Crew: 1 pilot + 3 drone controllers
▪ Length: 59 m
▪ Width: 35 m
▪ Height: 25 m
▪ Mass (standard equipped): 887 780 kg
▪ Block count (without drones): 656
▪ Block count (with drones): 898
▪ PCU count (without drones): 7 506
▪ PCU count (with drones): 12 388

Armament:
▪ 4x 25mm Gatling Turrets

Features:
▪ Drones controllable through the interface screen in front of the pilot’s seat.
▪ Pilot’s seat with information screens and toolbars.
▪ Controller seats with access to the drones’ remote controls, for flying without using the script.
▪ Can land on planets and launch back into space.
▪ Has on-board production equipment to refine ore and assemble components.
▪ Jump Drive with a range of 2000 km.
▪ No mods or DLCs.
▪ Contains fuel and components – tested in survival.

Known issues:
▪ Since I have chosen to have Rdav’s script deactivated until you need it, you may have to recompile the programmable block named “CENTRAL_COMMAND” after pressing [5] on Toolbar 3.

Acknowledgements:
▪ The radar panel uses Whip’s Turret Based Radar script by Whiplash141.
▪ The information screens use MMaster's LCD 2 script.
▪ The screen showing the planet's horizon and the ship's heading is using Whip's Artificial Horizon Redux script by Whiplash141.
▪ The interface and drone control are using the Rdav’s Fleet Command MKII script.
▪ The doors and airlock are operated by Whip's Auto Door and Airlock Script by Whiplash 141.

For those who like the setting and lore surrounding the Alliance: consider reading The Fleet Beyond Neptune[www.amazon.com], my book about the conflict between the Alliance and the Fleet.