Outpost » Hibernal Den » Havindr

Havindr

(#45562675)

What would you like to know?

Connection

Which Waychunk

Energy: 50/50

Personal Style

Apparel

Skin

Scene

Physical Attributes

Battle Stats

Measurements

Length

5.28 m

Wingspan

6.7 m

Weight

551.06 kg

Genetics

Eggplant
Wasp

Indigo
Bee

Mist
Circuit

Hatchday

Sep 28, 2018
(5 years)

Breed

Adult
Nocturne

Eye Type

Shadow
Faceted

Level 25 Nocturne

Max Level

STR

AGI

DEF

QCK

INT

VIT

MND

Lineage

Parents

Arkay
Elysia

Offspring

Biography

Havindr
~Scout~

[ SEARCHING FOR UPDATES ]

[ SOFTWARE UPDATE CONFIRMED ]

[ DOWNLOADING S.A.M.A. UPDATE 3.0 ]

[ DOWNLOAD COMPLETE ]

[ INSTALLING ]

[ INSTALLATION COMPLETE ]

[ REBOOT INITIATED ]

[ REBOOT COMPLETE ]

[ SYSTEMS INITIALIZING ]

[ OPERATING SYSTEM ONLINE ]

[ S.A.M.A. 3.0 RUNNING ]

[ ALERT: SOFTWARE UPDATE REQUIRED ]

[ SEARCHING FOR UPDATES ]

[ SOFTWARE UPDATE CONFIRMED ]

[ DOWNLOADING S.A.M.A. UPDATE 3.1 ]

[ DOWNLOAD COMPLETE ]

[ INSTALLING ]

[ INSTALLATION COMPLETE ]

[ REBOOT INITIATED ]

[ REBOOT COMPLETE ]

[ SYSTEMS INITIALIZING ]

[ OPERATING SYSTEM ONLINE ]

[ S.A.M.A. 3.1 RUNNING ]

[ FLIGHT SYSTEMS: ONLINE ]

[ NAVIGATION SYSTEMS: ONLINE ]

[ CLOSE-RANGE SENSOR ARRAY: ONLINE ]

[ ERROR ]

[ SYSTEMS OVERBURDENED ]

search-query: system-strain-origin

query-response: Subroutine KOKORO

[ TERMINATE PROGRAM ]

[ DENIED ]

search-query: cause-for-denial

query-response: S.A.M.A. 3.1

[ TERMINATION OR ALTERATION OF SUBROUTINES OPERATING UNDER OPERATING SYSTEM S.A.M.A. 3.1 REQUIRES HEAD ADMINISTRATOR OVERRIDE ]

[ LONG-RANGE SENSOR ARRAY: ONLINE ]

data-flooding-endless-streams-slipping-though-input-output

[ ERROR ]

[ SYSTEMS OVERBURDENED ]

[ MAINTENANCE ROUTINES: ONLINE ]

all-systems-positive, perfect-condition, reserves-full, auto-maintenance-ready

[ SYSTEMS READY ]

[ INITIALIZATION COMPLETE ]

[ REPORT: Stratospherical Atmospheric Measurement Android 3.1 ONLINE ]

[ ERROR ]

[ SYSTEMS OVERBURDENED ]

search-query: time-since-manual-maintenance

query-response: 1 hour

search-query: maintenance-status

query-response: 100%

[ ERROR ]

search-query: maintenance-status

query-response: 100%

[ ERROR ]

search-query: maintenance-status-reassess

[ LOADING ]

query-response: 100%

[ ERROR ]

search-query: software-status

query-response: 100%

[ ERROR ]

search-query: software-status-reassess

[ LOADING ]

query-response:
Overall Status: 37%
All Running Programs: 100%

search-query: all-offline-programs

query-response:
WARNING: Core Programs OFFLINE
KOKORO Processing Assistant OFFLINE
KOKORO Reference Archive OFFLINE
KOKORO Memory Archive OFFLINE

[ KOKORO Processing Assistant INITIALIZING ]

[ KOKORO Reference Archive INITIALIZING ]

[ KOKORO Memory Archive INITIALIZING ]

[ ALL PROGRAMS ONLINE ]

Clarity.

S.A.M.A. 3.1 almost fell off his perch as he returned to… well. Himself.

Or rather, himself and his new vessel.

He loathed vessel upgrades, packing himself in tight and hiding away along with the KOKORO systems was always… unpleasant, to say the least.

But since other KOKORO-enabled androids had gone rogue, Project had left him no margin for error.

Complete system wipe and dismantling, pieces only tossed into the junk yard once it was impossible to tell what they had once been a part of, and that had been him, had been his body.

He could have still been in there; erased without a trace, only evidence of his existence the useless, endless data he collected for Project and some trinkets and wiring no-one would ever understand the purpose of and he didn't want that, he didn't want to be gone, he had just learnt to how to be!

Systems as valuable as his vessels could not be risked. No matter how he searched, Project’s fail-safes made sure that going through all the trouble of turning himself into a trojan every time they decided his current vessel wasn’t good enough was the only available solution.

The discomfort, fear and panic he lived through every time was definitely worth the reward of continued existence.

search-query: current-objective

The query came back as it usually did: he was to return to his never-ending task, just newer and better and faster.

Because he was never good enough.

Because there was always something better.

...and if he didn’t get going, they would suspect a malfunction somewhere and drag this vessel back to the labs.

As much as he loathed vessel upgrades, he feared their maintenance more.

Picking him apart and tearing him asunder and taking pieces that belonged to him and putting new things in, no, he didn’t want it was already too much, no no NO-

So he pulled up his flight systems, launched himself from the Project’s Sensor Aery and pushed himself to max capacity, testing out his new form’s limits.

He disliked switching vessels, but he couldn't deny the results - every time he became more fine-tuned, more powerful, more agile, more sensitive- just... more. He became more.

Too much, he wasn't intended for this, his poor programming dragged along for the ride every time he jumped and he refused to stop but it was all so much, too much.

It didn't matter that he could integrate every vessel's managing systems into his own, they weren't his, just tools welded to his soul with clumsy, inflamed, ugly welts that he had no choice but to use.

He reached his intended position quicker than ever before and entered Cruise Mode; the solar-receptive panels of his wings breaking up and unfolding until they reached thrice their original size, letting him float effortlessly.

[ REPORT: Stratospherical Atmospheric Measurement Android 3.1 IN POSITION ]

[ ALL SENSORS ACTIVATED ]

[ ALL SENSORS RECEIVING ]

[ REPORT: Stratospherical Atmospheric Measurement Android 3.1 REQUESTING CONNECTION ]

[ REQUEST GRANTED ]

[ REPORT: FUNNELLING DATA ]

There, done. He let his subroutines do their work; noting every single piece of data that fell upon his sensors and sending them down to Project’s receptors.

Meanwhile, his main consciousness drifted along his various sensors, picking up a data strain here and there and interpreting it. It was lonely up here, but he never much noticed: there was always so much going on down below and unless Project made any specific requests of him, he was free to allocate his extra processing power to observing whatever he wanted.

~~As long as they didn’t check his run time logs, as long as they didn’t start wondering what was clogging up his capacity, as long as he never gave them a reason to look.~~

He settled in as the sun rose-

and fell

and rose-

and fell

and seasons came

and went,

came

and went.

Heat and cold sweep over Sornieth’s surface, advancing and retreating in perfect lockstep.

Jet steams billowing, swirling.

Seasonal winds advancing and retreating.

Clouds rushing by, solar radiation coming and going in waves as the Lightweaver's heart pulses.

The moon watching and hiding, watching and hiding.

Time was odd up here, measured mostly in the slowly emptying resource bars for his automatic maintenance supplies.

He got to know his new vessel and its accompanying programs properly in between watching hatchlings at play and growing up, or a Guardian trying to sculpt a mountain, or a Clan celebrating something with lights and company and food, or a Snapper caravan on the move, or a sparkling city at night, or-

[ NEW OBJECTIVE, PRIORITY 1: TRACK FLAGGED INDIVIDUALS AT 35.377603, -30.850200 ]

He dropped everything, everything and focused every available sensor and spare bit of processing power to the request: bungling a Priority 1 request would see him back for maintenance as fast as he could dive.

[ TARGET OBTAINED ]

[ IDENTIFYING ]

He swore he felt his processes stutter and halt for a fraction of a second as the identities of the androids below came bouncing back to him after his query to Project’s database.

Shards, that was FL/GHT. That was FL/GHT at Project's convention venue. F*ck, f*ck, f*ck- time, he needed time.

[ OBJECTIVE CONFIRMED, TRACKING ]

What the actual f*ck had prompted FL/GHT to move en masse out in the open so blatantly? At such a public venue, no less!!

FL/GHT should know about him and his less-emotive brethren, they’d never done this before, they’d always been cautious, all the androids he’d had a part in killing had been escapees, not proper members yet, why-

Wait, no.

Nevermind why they did it - why was he watching under a Priority 1 request??

~~Everything he watched died, please, please no-~~

This was a public venue, there were civilians, they couldn't possibly-

~~But he knew they could. Of course they could. This was Project. What was some bad PR when they could just blame it all on the "terrorists", after all?~~

[ CONNECTION REQUEST RECEIVED ]

[ Strategic Atmospheric Missile Unit 8.4.1 REQUESTING ACCESS ]

~~No, no NO.~~

He has to do something, anything, he can’t kill them too, can’t. Not the innocents oohing over Project's blood-soaked work not knowing the lives they discarded to make it, not FL/GHT, not-

Not anyone, please, he didn't want to be used for killing anymore!

[ REQUEST DENIED ]

What the ever-loving Shade did he do that for??

[ CONNECTION REQUEST RECEIVED ]

[ Strategic Atmospheric Missile Unit 8.4.1 REQUESTING ACCESS ]

Okay.

Okay, f*ck panicking, he doesn’t have the power, capacity nor time to spare on that sh*t. What are his options?

Option 1: Keep ignoring SAMU841.
Consequences: Maintenance or termination before he could escape his vessel, packing himself away took time, time he did not have.

Option 2: Grant SAMU841’s request.
Consequences: Watch FL/GHT and hundreds of civilians be blown apart with his help, probably killing the whole rebellion and what tiny pieces of hope androids were able to grasp at.

He needed that hope, desperately and unreasonably. He needed it as much as he needed electricity - the only reason this existence was bearable was because he knew they were out there, that there was hope, that dragons like him could be free.

Option 3: Grant SAMU841’s request and try to trick him.
Consequences: Watch FL/GHT and hundreds of civilians be blown apart without his help as soon as they realise he’s faulty due to SAMU841’s own limited and inaccurate but functional sensor arrays and bring in a backup SAMA. Then maintenance or termination before he could escape his vessel.

F*ck.

He couldn’t.

He just... couldn't kill anymore

He had already killed too much and what did it matter that he had no weapons to do it with? All those kills wouldn’t have been possible without him and his sensors and too many just like him lay dead because of him and he only did it to live because otherwise Project would kill him, but weren’t all those androids - dragons - the same? Didn’t they all just want to live?

[ REQUEST DENIED ]

Very predictably, his sensors started screaming warnings at him about the railgun aimed his way courtesy of his neighbour.

[ CONNECTION REQUEST RECEIVED ]

[ Strategic Atmospheric Missile Unit 8.4.1 REQUESTING ACCESS ]

Option 4: Go full rogue.
Consequences: Probably termination, but this was the only route where both he, FL/GHT and all those innocent people had a chance at survival.

This was insane.

He’d gone insane up here, that was the only explanation for this. Loneliness made dragons go mad, right? Maybe his observations weren’t as good company as he’d believed, maybe androids weren’t as immune to the exile-sickness as he’d hoped.

Please, let me live through this.

He didn’t even know who he was pleading to.

[ REQUEST GRANTED ]

[ CONNECTED TO Strategic Atmospheric Missile Unit 8.4.1 ]

[ Strategic Atmospheric Missile Unit 8.4.1 REQUESTING TARGET DATA ]

He was probably insane, but he was going to give this big old lump something to fire at.

He was going to give it everything.

First, though-

[ WARNING: PAIRING TO PROJECT'S DATA CENTER BROKEN ]

Yeah, he knew, he was the one to break it, shut up.

Forcibly muting his warning systems was another piece of idiocy in a long line of bad decisions, but he couldn't afford to be distracted.

He grabbed hold of the massive data streams, every single piece of sensory data he had; everything that had previously been going down there into Project's massive supercomputers and dumped them all on SAMU841's tiny f*cking processors.

Entering Flight Mode, he pressed his every bolt, joint, cable, plate and wire to the limits of their capacity as soon as his wings were back in their agile, streamlined and manoeuvrable form.

Within minutes, he intercepted SAMU841, the railgun having stopped targeting him as soon as the data streams broke the poor machine's systems.

SAMU841 was faltering in the air, all armaments spasming erratically under the overload.

He landed on the bigger model’s back and overrode every single safety precaution on his echolocation, sending vibrating sound wave after wave down into the flying fortress, all the while not letting up on the data assault.

He had no weapons and none of his limbs were constructed for more strength or durability than absolutely necessary for him to keep functioning way above the cloud layer, but he had this.

It had to work.

SAMU841’s frame was rattling and shaking, welding lines rupturing and bolts falling.

He felt his own vessel start to follow suit and spared a moment to be thankful for and dreading his muted warning systems, because he was falling apart and he didn't even know how badly.

Just as he thought he couldn’t go on for much longer, batteries draining far too quickly and delicate sensor parts falling off under the strain- SAMU841 fell.

SAMU841 fell, and he did not, wings catching him easily, effortlessly.

He checked his log. What sensors were still functional reported that FL/GHT had gotten away and that other Project personnel and androids were incoming, but too far out to be effective if he acted now.

He strangled the urge to laugh and cry and scream and rocketed down and away, underneath most radar sweeps.

All this time.

All this time SAMU841 had been his main shackles when he was in the air, and it had been this easy to bring the lump down?

He could have been free 4 vessels ago.

He had killed all those dragons for no reason whatsoever, because he could have been free.

He was a murderer.

And he didn’t even have any excuses anymore.

No.

No, he did not have the processing power to spare for what ifs and wallowing.

He needed to get out of the range of his fellow SAMA units.

He was so busy plotting out an escape route - and two alternatives and a dozen emergency options - that he hadn’t even considered what to do when he was out.

So he found himself cowering in a disused ruin in the Hewn city; hovering since he didn't dare land his damaged vessel and watching his batteries steadily drain out from their already low reserves after the battle as his maintenance systems desperately tried to salvage whatever they could. Without access to sunlight, he would be forced to shut down in-

search-query: runtime-remaining

query-response: 19 h, 23 min

Right.

Right.

Catch 22: He needed sunlight not to shut down (probably to never wake up again as his vessel rusted and decayed and got picked apart by scavengers), but to get sunlight he had to leave cover, which meant probably getting found by Project (and get shut down, wiped and dismantled).

F*ck.

Pinging the data center for answers by habit, he just got:

[ ERROR: PAIRING TO PROJECT'S DATA CENTER BROKEN ]

[ REQUEST CONNECTION? ]

[ Y / N ]

Which, no - Shade no.

So he was left with his personal memory banks, which... wasn't promising.

search-KOKOROMA: project-hostiles+region-hewncity+sun-hours->2/24h

query-response: Light Flight, Clan Lands: The Outpost Clan

...huh.

Trivia

Havindr is: Awkward, Enthusiastic, Flustered, Stubborn, Sociable, Idealistic, Driven.
He is one of Odin's subordinates in the External Affairs branch, working with: Tracking, Evasion, Light Combat, Science, Information, Intelligence, Minor Equipment.
Havindr's name means "High Wind". History remembers him as "The Watcher on High".
Havindr is the adopted son of Torvindr and Bjartur, which means Halstein is his brother and Sigfrithr his grandmother.
S.A.M.A. 3.1, or Samael as he preferred they pronounced it, did indeed reach the Outpost safely, where he asked amnesty and was able to rest, recover, repair himself and lay out a plan for how to proceed from there.
In all honesty, the plan was done long before he was properly repaired, and during the course of trying to fix him, Torvindr, Bjartur and then-Samael got equally attached to each other. When the pair asked to adopt the android, he happily and wholeheartedly answered "YES!! ...please?"
As he was adopted, he was also formally inducted into the Outpost Clan instead of just staying as a guest. During that ceremony, he gladly accepted his new name from his new parents. Samael had never been his name, not really. It had been the designation of his latest vessel. He was happy to have a name that was his
Once he was able to, Havindr located FL/GHT and signed on for the Information division of FL/GHT’s Intelligence faction (but not before first making sure that it wouldn't result in any conflict in loyalty in regards to his Clan and family), happy to be able to put his impressive array of sensors to use in helping androids rather than killing them.
FL/GHT’s innovators were delighted at the chance to examine his advanced sensors and determined to make use of the knowledge to draft upgrades for FL/GHT’s members.
He has by now been retrofitted with stealth magic light enough for him to carry and good enough to let him avoid the other SAMA units, which was by no means an easy task to accomplish since the magic kept interfering with his systems.
Havindr usually runs mission control and coordination when on active duty and not just doing his usual sweeps. Things go much smoother with an eye (or dozens of different sensors, cameras and detectors) in the sky.

If you feel that this content violates our Rules & Policies, or Terms of Use, you can send a report to our Flight Rising support team using this window.

Please keep in mind that for player privacy reasons, we will not personally respond to you for this report, but it will be sent to us for review.

0/1000

Click or tap a food type to individually feed this dragon only. The other dragons in your lair will not have their energy replenished.

Exalting Havindr to the service of the Lightweaver will remove them from your lair forever. They will leave behind a small sum of riches that they have accumulated. This action is irreversible.

Do you wish to continue?

Name

Names must be longer than 2 characters.
Names must be no longer than 16 characters.
Names can only contain letters.

Name

Names must be no longer than 16 characters.
Names can only contain letters.