#of course there are exceptions like horus and whatnot

[linkedin-offficial]

where did the names for your sky ocs come from? like how did you think of 'em?

okay, but the real detailed answer is that when thinking of names for specifically sky characters, i often times like to just pick a word that i think represents each character well and then just translate it into tagalog (for example, "bata" means "child", "ilaw" means "light", ect ect).

though, when that doesnt work, i usually just shorten it or move some letters around to make it look and sound better on the tongue. (for example, "bituin" means "star" in tagalog; to me, its a bit of a mouthful. so id just use a variant of this word, like "bitu" or "itui")

i do this alot when it comes to names for characters of mine, not just sky ones. regular english names (even 'noun names') often times feel boring to me and usually dont fit the setting im putting the character in. so this is my go-to!

[msmc-796-official]

@faulty-heat-vents hiya. callsign Slipshod, MSMC-796-2, squadron mechanic and ex-HORUS member, at your service. buckle up, kiddo, you're getting the crash course on HORUS today. hope you're taking notes, there WILL be a test (I'm kidding, obviously)

HORUS is often considered a member of the big 4 (the other 3 being IPS-N, SSC, and HA, obviously - GMS doesn't count because they're the one the big 4 get all of their base parts from), but in truth it's not so much one big corpro conglomerate as it is a bunch of unaffiliated splinter groups scattered across the galaxy all operating and identifying with one unified group name. (kinda like how all the different merc squads at MSMC have their own squad names, but are all still part of Mirrorsmoke Mercenary Company, if that makes sense)

these splinter groups are called "cells", and usually consist of whatever technophiles, mechanics, hackers, NHPs, and assorted freaks (I use that term both affectionately and, well, not-so-affectionately here) feel like getting together and causing chaos that day / week / month / whenever. HORUS cells pop up fast and disappear just as quickly, all with different goals and personalities and agendas that make pinning down a consistent modus operandi for HORUS as a whole nigh impossible

HORUS mechs are all universally kinda fucked up, due to the fact that no two print codes are ever the same because they're always coming from different places, each with their own quirks and modifications and viruses and liturgicode and whatnot. the general frame naming scheme is that of mythological monsters from old Cradle - manticore, pegasus, goblin, hydra, minotaur, and so on. usually they specialize in systems-based abilities, seeing as the people who design 'em are talented in that regard themselves. (whole lot of paracausal tech and semi-sentient liturgicode get stuffed in there too, of course)

best example of what kinda weird shit HORUS mechs can do is the lich frame. those fuckers will pop into your hangar and replace your old mech seemingly outta nowhere, then when you go to check the records, you find that you've always piloted a lich - never had the old mech to begin with. basically, through some kinda paracausal nonsense that not even I fully understand, lich frames alter the timeline so that, effectively, you always have been a lich pilot. (that ain't necessarily a bad thing - liches are fragile, but stupidly powerful in the right hands. [REDACTED] over at @officialunionhr pilots a lich, if memory serves, and they were around to see SecCom firsthand. scary motherfucker, that one)

one more important thing: you can't buy a HORUS print code like you can from the other corpos. outside of DIYing a HORUS frame yourself, as it sounds like "Thermie" has reported your classmate doing with that prototype gorgon, the only way you can get your hands on the print codes for one is either a) find one buried somewhere deep in the backrooms of the Omninet, or b) randomly get sent one by a current HORUS op. sometimes a cell will do a code drop publicly, like the folks over near Free Sanjak did with the original kobold code for the use of the Ungratefuls, but that's an exception and not a rule. usually if you wanna get your hands on a HORUS mech, you gotta have connections (like me, for example) or get really, really lucky

that's the long and short of it - sorry for infodumping, but I was part of a HORUS cell for a good long time, so I out of anyone should know how it all works. if you have any further questions for me, the askbox is always open. take care, kid

-- Slipshod

//Pilot, you have one [1] unallocated License Point(s) available.

//WAIT SHIT SINCE WHEN??

//Your engineering monitor has temporarily allocated you one [1] license level for you next assignment.

//Well, that’s fun. Guess I should start thinking about what to kit you with then, huh?

//I advise consulting your newly-established Omninet social port. Perhaps the wider community has ideas?