FSE

Furry search engine

formerly SoFurry search engine

CONFIDENTIAL - Top Secret

Authorized Personnel Only

File No. 32810

Date: 1/17/437 After Human Extinction (AHE)

Author: [REDACTED]

Contents

1. Introduction

2. Dragonoid Drones

3. NanoFluid

4. Drone Classes

5. Drone Models

6. Docking Procedure

7. Drawbacks

8. Extended Transfer Time

9. Transfer Shock

10. Docking Positions

11. Squadron Formations

12. Harem Formation

13. Reverse Harem Formation

14. Binary Formation

15. Adaptive Formation

16. Other

17. Common References and Unofficial Terminology Index

18. FAQs

Section 1: Introduction

The Dragonoid Project represents a revolutionary development in autonomous drone technology. While first conceived as a general response to increasing military aggression from the adversary, following the enemy's successful replication of this technology during Operation Dragonslayer, the project's aim has now shifted to combat enemy Dragonoid units. This file will provide a comprehensive introduction to the Dragonoid Project's objectives, function, and technological advancements.

1.1: Dragonoid Drones

The autonomous drones developed through the Dragonoid Project (henceforth referred to as "dones", "mechs", or "units") can be separated into five classes, each with unique physical characteristics and abilities. However, generally, these drones are based on the appearance of the quadrupedal western dragons of ancient human myth, with reptilian features; including a long muzzle, two eyes, horns, long talons, slender tails, membranous wings, and plantigrade feet. Dimensions range from 3 meters tall and 9 meters in length to 12 meters tall and 36 meters in length.

1.2: NanoFluid

All Dragonoid units use a concentrated nanite solution composed of highly adaptable nanomachines, known as NanoFluid (colloquially referred to as "NF"). NanoFluid is white and slightly more viscous than water. It's primary purpose is to transfer energy or intelligence between two units[1].

More recent advancements in enemy nanotechnology have enabled the development of combative NanoFluid, designed to fight against our Dragonoid units instead of transferring power or data. Ally engineers have noted that units which are overpowered by enemy units can also have power or data extracted via the forceful extraction of NanoFluid. Due to its detrimental effects on a unit's overall function[2], this method is strictly prohibited among allied mechs.

Combative NanoFluid Types:

1. Destroyer NanoFluid - Capable of dismantling and destroying enemy mechs by deleting critical operational files and overloading mechanical components.

2. Shutdown NanoFluid - Capable of shutting down an enemy mech's systems without damage, allowing the mech and its data to be preserved.

3. Hacking NanoFluid - Capable of infiltrating a mech's systems and assigning alternative orders.

1.3: Dragonoid Classes

Combatant

• Purpose: Aerial and Ground Assault Operations

• Dimensions

◦ Height: 12 m

◦ Length: 36 m

◦ Size Classification: Large

• Overview: The most basic and abundant class, but also the most powerful, combatants are designed and constructed purely for battle. With a reinforced titanium alloy chassis, self-sharpening nano talons, tri-stream plasma-ignited flame breath, kevlar-webbed wings, and a bite strength of several tons, the combatant can stand up to the toughest of opponents and obstacles.

• Identifying Color Scheme: Red, Black Markings

• NanoFluid: Enemy Combatant Class mechs can produce Destroyer NanoFluid

Stalker

• Purpose: Covert Operations

• Dimensions

◦ Height: 3 m

◦ Length: 9 m

◦ Size Classification: Small

• Overview: Designed for stealth and silence, stalkers use Chameleon Scale (TM) hide to become invisible to the naked eye, internal coolant systems to avoid thermal detection, and are programmed with a range of stealth attacks and tactics. Liquid metal joints and vibration-absorbent padding in the feet allow them to move soundlessly, living up to their name by stalking enemy mechs and analyzing their defensive capability to exploit weaknesses. While they don’t breathe fire like combatants, their retractable fangs carry a high tech nano-venom, a purple nanite fluid which shuts down hardware it’s injected into.

• Identifying Color Scheme: Black, Purple Markings

• NanoFluid: Enemy Stalker Class mechs can produce either Destroyer or Shutdown NanoFluid

Hacker

• Purpose: Enemy Computer System Infiltration

• Dimensions

◦ Height: 3 m

◦ Length: 9 m

◦ Size Classification: Small

• Overview: Designed to remotely take control of other Dragonoids, hackers employ their adaptive cortex to invade an enemy mech's neural network and force them to accept alternative orders or even switch factions altogether, as well as executing cyber attacks on other systems. This class is not designed to be used alone and should have others in its squadron to provide support in combat situations. Hackers cannot sustain nearly as much damage as the combatant class, but can still withstand more than the stalker class.

• Identifying Color Scheme: White, Pink Markings

• NanoFluid: Enemy Hackers can produce Hacking NanoFluid

Charger

• Purpose: Energy Storage and Transfer

• Dimensions

◦ Height: 12 m

◦ Length: 36 m

◦ Size Classification: Large

• Overview: The charger class is primarily designed to accompany squadrons on longer trips where Dragonoids may not have easily accessible power sources. Chargers are capable of delivering full charge to four other Dragonoid units at once and still remaining functional. The charger is not designed for combat, but if needed can execute various electricity-based attacks to short out or disable enemy units and is capable of withstanding a moderate amount of damage. Chargers are typically much larger than other mechs, even Combatants.

• Identifying Color Scheme: White, Blue Markings

• NanoFluid: Both enemy and ally Chargers use basic NanoFluid to transfer energy, but can produce large quantities of it

Medics

• Purpose: Ally Dragonoid Maintenance

• Dimensions

◦ Height: 10.5 m

◦ Length: 22.5 m

◦ Size Classification: Large

• Overview: Medic class Dragonoids are built to repair damaged units after or during battle. A more focused and intense but less powerful variant of the flame breath used by combatants help medics to weld damaged armor plating, and their internal compartments carry a variety of spare parts to replace damaged components. Medics can't sustain much damage on their own and must be defended by other mechs. Although not designed or programmed for combat, a medic's knowledge of the mech classes' critical systems could potentially allow them to make precision strikes and damage an enemy mech's weak points.

• Identifying Color Scheme: White, Red Markings

• NanoFluid: Medics can produce Repair NanoFluid, which can be transferred through another unit's ports to repair internal systems, or ejected over external damage

1.4: Drone Models

In addition to the distinct classes, drones can be separated into unique models based on the arrangement of docking ports, general appearance, and vocal processors.

Male: Male models possess unique external male docking ports, with ridged shafts, a tapered point, and a thick bulb at the end meant to secure NanoFluid inside a receiving docking port. Male mechs also possess a rear port, which serves only to receive NanoFluid, although both they and female mechs are also capable of receiving NanoFluid via the oral port (note, however, that this will likely disrupt their vocal processor and impede speech ability). Male vocal processors are typically deeper in register.

Female: Female models possess a female docking port, made from highly flexible synthetic flesh with a high number of tactile sensors. Although typically used to receive, female mechs can transfer data as well through the default docking procedure, since their NanoFluid can be absorbed by an inserted male port. Same as male models, they also possess a smaller rear port, built only for receiving NanoFluid. The primary female port can apply automatic self-lubrication, unlike the rear port, and is generally not as restrictive. Female mechs generally tend to have higher-pitched vocal processors.

Intersex, Non-Binary, and Other Models: At times, a mech's model may not be visibly or audibly clear, or they may possess features not commonly included in their originally designated model. Some may possess one port and prefer to be referred to as another model, some may even possess both male and female docking ports. Others may not possess a model designation at all. Fortunately, such features can be easily determined via the ocular display interface provided by standard issue eye implants. If this is not available, open discussion with a mech is permitted, provided they are not on-duty or engaged in active combat.

Section 2: Docking Procedure

The docking procedure is a complicated mechanical method of transferring NanoFluid between two or more units, often to transfer power or data. The procedure involves the docking port of the sending mech and that of the receiving mech being stimulated in close proximity, until enough NanoFluid is produced to ensure the transfer. Field operatives and mechanical engineers have noted that this process is visually very similar to two organic life-forms engaged in sexual intercourse, but this is to be dismissed as the common tendency of the mind to attribute organic qualities to non-organic things, in the same way a car's headlights and grill can appear to form a face.

2.1: Drawbacks

Due to the complex nature of docking, the procedure possesses two notable disadvantages:

1. Extended Transfer Time: The process is often lengthy and requires minutes to hours in order to achieve full transfer.

2. Transfer Shock: The process tends to overload the systems of the mechs involved and can require even longer periods for the mechs to fully reboot, a phenomenon referred to by systems engineers as transfer shock (though field operatives tend to refer to it as the "refractory period" due to its similarity to the organic phenomenon). This can be gradually shortened with experience, as the mech's artificial intelligence systems learn to parse data quicker and reroute power more effectively.

Section 3: Squadron Formations

Units are assigned to squadrons based on a series of factors, such as class, model, the purpose of the squadron or current assignment, and even the individual unit's OS version number.

3.1: Harem Formation

The harem formation indicates a squadron consisting of a single male unit and multiple female units. These formations are most typically used when the male unit is a Charger class, capable of sustaining the female units over long distances regardless of their class or the squadron's overall purpose. This formation has other uses, however, such as when a male unit is transporting intelligence which cannot be transmitted wirelessly and can be transferred to female units via docking, allowing said intelligence to be encrypted, dispersed, and compartmentalized. Alternatively, the sole male may be a Medic class unit, with other units being Combatant class, which may require frequent repair due to their typical use in direct combat.

3.2: Reverse Harem Formation

As the name would indicate, a reverse harem formation indicates a squadron which consists of a single female model unit and multiple males. Such formations find common use in black operations requiring stealth, in which the male units are Stalker or Hacker class units with the goal of obtaining enemy intelligence or performing reconnaissance, allowing all of their obtained intelligence to be transferred to the female unit, typically a Combatant class unit, chosen for their high likelihood of survival in the event the operation is compromised. In other cases, the female unit may be the designated squadron leader, whose survival is prioritized, capable of taking multiple transfers of power or intelligence at once.

Footnotes

Many have noted that the process of two units docking and transferring NanoFluid tends to appear extremely similar to what organic dragons might look like if engaged in sexual intercourse. (See Section 2: Docking Procedure)

Beyond potential physical damage, units may also display operational errors in programming, such as refusal to obey orders. Given our still limited understanding of their artificial intelligence, it seems wise to avoid psychological trauma, or whatever the AI equivalent of this is.

~~~

4.1 Common References and Unofficial Terminology Index

FAQ

Q: Why use NanoFluid to transfer power or information when the transfer process is so inefficient? Why not just use a power cable or wirelessly transfer encrypted data?

A: NanoFluid transfer is a lengthy process, but this was intentionally designed, partially to enable time for a receiving unit to prepare to accept data or power, but also to make the forced transfer of NanoFluid more difficult for enemy mechs, giving a targeted mech more time to escape an aggressor. It has been determined that power transfer via external cable is actually more likely to overload a mech and cause extended transfer shock. Meanwhile, wireless transfer of sensitive data, even encrypted, can always be intercepted or jammed by enemy hardware.

Q: Why is NanoFluid only used in Dragonoid mechs and not other equipment or power plants?

A: NanoFluid is proprietary technology, and its use is restricted to military equipment to prevent it from being reverse-engineered and misused. Further, NanoFluid production requires specialized nano-forges which are too large to be used in smaller equipment, suitable only for use in Dragonoid mechs. And lastly, production of NanoFluid is a complex process which only the advanced artificial intelligence of Dragonoid units is capable of handling successfully.

Q: Why not just mass produce NanoFluid in external nano-forges to inject mechs with?

A: NanoFluid is a highly adaptable material which must be produced directly inside of a mech based on its designated purpose. For example, a mech may decide to initiate docking in order to transfer data, but in order to do this, the mech would need to pull this data from their own database, encrypt it, and transfer it into their NanoFluid. Keeping this process internal protects against security breaches.