Avatar of HeySeuss

Status

Recent Statuses

7 yrs ago
Hot dogs are already cooked. Might as well just sear them to add flavor.
7 likes
7 yrs ago
I love it when I catch up on my posting.
2 likes
7 yrs ago
If you take college seriously, it opens doors. Harvard and Hopkins makes it easier, but you can do well anywhere.
3 likes
7 yrs ago
Prefer to brainstorm on Discord for that reason.
1 like
7 yrs ago
Windows 10 is very much like a German prison camp guard, "Ah, I see you are tryink to escape work fifteen minutes early, Herr Colonel Hogan, here ist an update zat vill stall you!"
4 likes

Bio

Most Recent Posts

"PLANCOM, this is Rat 1-6. Orders acknowledged. Over."

The radio orders were broadcast from the Captain's comm circuit to the rest of the lance and the other officers in the Task Force to keep them up to date on the new orders.

"Rat 1-6 here, we're redeploying the mechs from planned patrol to focus on sensor anomalies in the Pitt basin. Burns, von Wulfhart, Mattlov, use jets to obtain overwatch positions and maintain security. Rall, Bjornson, Eichberg and myself will push through along to grid 5-Bravo-9'er-Delta from here. Lieutenant Mazigh will oversee drone deployment and security to cover the flank approaches."

Captain Hart had the typical Davion 'school' accent; like the BBC of ancient Terra, Davion school-ships and broadcasts emphasized a common accent, and the Captain had it. He was some part of Draconis March gentry, but a career officer and NAIS cadre instructor, tasked with finishing off mechwarriors that were deemed ready to start their careers before they graduated and were placed in units. It was a shakedown for cadets that transitioned them from the rigid structure of the academy to active duty and, presumably, command in the future.

The man was in an Enforcer, a very standard type of Davion mech, though his was fitted, as all the mechs here were, with advanced technology. Steelton was near the periphery, had lots of environmental factors to deal with and so it was an ideal place to train new mechwarriors and test new equipment. They ran exercises against the Star Guards, an elite unit, and learned things the hard way alongside and against some of the best Mechwarriors in the Inner Sphere. The Captain was well-respected with these men and women, coming from McKinnon's Raiders, in the 7th Crucis Lancers. He'd fought the Dragoons and lived to tell the tale. He'd fought in the Fourth Succession War and the War of 3039 and had a good professional reputation among fellow mechwarriors; even Crab Carraza, the Star Guards' commander. The rest of them, however, just fresh from the academy, were firmly made aware of their position on the pecking order by the Star Guards personnel they ran into -- they were greenies.

Mattlov had a very similar accent was the product of good schooling and NAIS, though he was not an aristocrat, more of a man-at-arms from a family, on the maternal side, of Mechwarriors who weren't title-holders. The distinction didn't matter that much; a mechwarrior was a mechwarrior, at least in the Federated Suns, and they all fancied themselves knights defending their realm. His Shadow Hawk happened to be painted a dusty desert pattern to match the terrain, and it didn't shine, but that didn't dull the romanticism of being a mechwarrior for Mattlov. He bought the Hanse Davion cult, the image of the great savior of their civilization, a man and a cause to fight for. His Caph upbringing was supposed to make him cynical of the mass media manipulation, even in a constitutional state like the Federated Suns, but he followed his mother's path, a warrior's path.

PLANCOM's regional sensor net had gone down about a day ago, which meant that geographic data was not being updated realtime and commos depended on onboard systems alone. Mechs were fine, but a lot of vehicles weren't. As a result, the Star Guard sent out one of their engineer detachments along with the task force in the area to check on the backup sensors system and stand by to activate them to keep the navigation networks going. It was an ideal time to send out a lance, preferably a green one, to pick up some good training in the field doing maneuvers with their mechs while providing an escort (and a tie-in to the planet's commo net) for the engineering, infantry and other elements in the area. Steelton was a hub of anti-piracy operations near the Periphery in Lyran Space, but it was unlikely that a raider element would hit a planet with an elite garrison. All the same, standard operating procedure in the Star Guards, and Mattlov approved, was to take it all seriously.

After all, Caph didn't expect to get hit in 3039, but he was there for it when the Ryuken regiments landed. They were beaten bloody by the ready reserve for the Federated Suns push into the Combine, but it taught Mattlov a valuable lesson; don't assume. He vaguely monitored the lance's internal commo net, but maintained relative silence. They had a lance leader and commo discipline could be hard to maintain at times on boring 'milk run' operations, but Mattlov learned the hard way through NAIS discipline to keep it professional in the cockpit. He had a mouth, so the lessons were reinforced with a lot of company punishment before he finally got it.

As the lance started underway, he stowed the mental chatter and focused on visuals; his Shadow Hawk had good sensors and comfortable life support, but he wasn't relying just on the sensors. Sensors could lie, after all and the eyes were needed. Once upon a time, Star League Mechwarriors were rumored to fight inside a sealed cockpit with sensors only. Mattlov couldn't see it, even though his neurohelmet was an old Star League model, provided by his parents as an early graduation gift; his mother knew how to pick the most utilitarian equipment and his father had connections through the family import/export company to get their son that, even if they could not afford a Mech.

The interface was wholly different; the SLDF model neurohelmets had a different system architecture and OS than the newer-made stuff. This one was vintage, SLDF-issue rather than a remake with familiar Davion-style screen layouts on his HUD using the old Star League tech; lostech, they once called it.

It was also a different color than the usual gold that he was used to, with different shapes and indicators for features to get his attention. He used the settings in live-training in the mech and in the simulators, but noticed a subtle difference in how the mech handled with this neurohelmet's interface.

The mech had a smoother than usual gait, and he owed it to the interface of the neurohelmet. Always a deft, delicate 'twitch' hand with the controls of a mech, which included a control stick that was set between the legs (not always the case, depending on the mech type) he marveled at the slightly elevated performance the helmet afforded. He'd gone out in a spare neurohelmet, a regular one, just because Senior Technician Reginald, his mech's crew chief, wanted to know if it was the mech or the helmet. They ran the data, crunched out a comparative report and made the SLDF neurohelmet's performance another piece of all the reports they were generating on this test equipment.

The Shadow Hawk had a restricted field of vision in some ways, which was a criticism of the design; the autocannon was overhanging the left shoulder, and there was a Streak-SRM-2 on the right side of the head, which was, quite simply, a reality of the design. Other mechs had far more expansive views, but he always liked the feel of a Shadow Hawk. The hum of the engine and power systems, the slight whine of the actuators and myomers, different in every mech, was to his liking in this particular type of Mech. He felt like he had the extra touch in one of these, and it had nothing to do with the new neurohelmet, though that helped.

There wasn't much of a view. Steelton was a dusty wasteland with mineral riches. It had jutting rock formations with a very specific hexagonal sort of characteristic that spoke of ancient geological activity of some sort, but it was mostly sand. Some extra heat, but nothing the sinks on his mech couldn't cope with. It was shades of sand, clay and slate out there, but at least the skies were clear and the horizon extended a ways. It was a desert vista that sung to his mother's heritage, and totally unlike Caph or New Avalon.

Weapons were not hot, but they could be very quickly. That was another operational rule of the Star Guards. They'd loaded with live ammo, not training stuff, just in case.

As their orders were given, he shifted his Shadow Hawk into a faster run as a prelude to a jump; with the rumble and roar of the jets beneath him, he used the neurohelmet to balance the Mech as it came down, to position the legs just so on the high ground he and the two others were told to ascend. There was a crunch of landing, as the myomers in the legs absorbed the landing shock and the arms splayed out to help the mech maintain balance just as a human would, with assistance from the neurohelmet interface.

Meanwhile, further below, the non-jumpers were making their way forward, sensors out...
First post incoming.
@HeySeuss So out of curiosity when can we expect the IC?


I hope to have it written in the next two days. Friday should be slower in the afternoon as business dies for that week.

Finally posted my app in the characters tab. Let me know if that's fine!


Approved, though I would change the artillery pieces over to Thors or Thumpers, and maybe put the Arrow VI on Padillas. As this is a testbed unit, these star league era vehicles may have been produced on a special run to spec for this unit to evaluate for general deployment with the AFFC.

Also, as house rules, I think we are going to be deploying drone units as well as that makes a lot of sense.

Sheets up to here are approved. I have a specific planet that they are going to be on, and I sort of envision their current AO as an arid sort of place.
Name: Harper Rall


Going forward, folks, please just post the sheets in the sheets tab. This one's approved.
Hello, OOC is here.

Note that we have a short but sweet character sheet.

Name: Peter Mattlov
Rank: Cadet Sergeant at NAIS, Subaltern in the field (brevet rank)
Allegiance: Federated Suns (House Davion)
Planetary Origin: Caph
MOS: Mechwarrior
Synopsis of Role: The son of a Caph businessman with ancestral ties to pre-Succession War Caph aristocracy and a Davion veteran mechwarrior of the 3rd Crucis Lancers, Mattlov is current enrolled in NAIS. Has not risen past cadet sergeant because, while capable, he sometimes racks up demerits. He is noted for his affinity with medium mechs and a taste for hit and run tactics.
Battlemech: SHD-2Hb, but retrofitted with an AC/5 and ER Large Laser while retaining the Streak SRM-2's. The intent behind this mech is to function as a testbed for special munitions to augment standard autocannons and the Star League era vehicle with the Ferro-Fibrous armor and Endosteel was a viable upgrade that didn't involve the side-torso vulnerability of XL engines.

T;DR Summary:
  • Using the provided template, please create a character sheet.
  • Character sheets are short and sweet - the character can be summarized in a couple sentences. This is to get to a first post quickly, rather then spend a week writing character sheets.
  • You can create multiple characters (but only one mechwarrior.) Please keep their character stubs all on one post here.
  • See below.


Character Stubs

The whole point of this system is to quickly introduce a character's name, planet of origin, rank and military occupational speciality (MOS) and a quick summary of who they are in order to get them into the fight quickly. We're doing away with large sheets as an experiment. You can even write this stuff -after- you make the first post.

Name:
Rank:
Allegiance: FedSuns or Lyran Commonwealth, but they're all in the Armed Forces of the Federated Commonwealth (AFFC)
Planetary Origin:
MOS: (eg. Mechwarrior, Tech, Recon VTOL pilot, etc.)
Synopsis of Role: (One or two sentences, keep it moving. Ex. '4th year NAIS student mechwarrior from an aristocratic heritage' or a 'veteran tech officer that's salvaged and repaired mechs in two wars over the course of her service.')
Battlemech: (The most important item of equipment is separate; please list the type (such as TDR-9SE). Inner Sphere mechs that exist in 3050 only. Information on modifications is also appreciated. We will go into greater detail on the applications of helmet-mounted modules, networking capabilities and drones, etc, etc as well. (I have to update that from the old BT stuff. See the above list for ideas on which mechs to take.)


Unit Structure/Battlemechs


Bravo Lance, 1st Armed Forces of the Federated Commonwealth (AFFC) Cadre Company
  • Command: ( Recommend a fast moving medium such as the Phoenix Hawk, upgraded variant like the PHX-1b which is the old Star League version and might well be field tested because of the re-discovered tech but it's ultimately up to you.)
  • Fire Support: Recommend medium mech.
  • Recon 1: (Locust, Raven,Jenner, Cicada, Hermes, Hermes II, Mercury , Mongoose, Wolfhound(as a heavy scout), Sentinel(also as a heavy scout) and Firefly are really good examples, but there are other mechs as well in the light to medium category. You are allowed to play around and have custom configurations -- because it's a unit that field tests prototypes.)
  • Recon 2: (As above)
  • Other unit elements added as necessary.


Yes, I supported the kickstarter. I love BT.

T;DR Summary:
- The year 3050 in the Battletech Universe
- The primary weapon of war is the Battlemech, a class of heavily armored robots piloted by a human's nervous system.
- Characters are Mechwarriors in the lance (four to six -- I am willing to augment the lance) or support personnel (there's about a platoon of those, including infantry/security and aerial reconnaissance for the mechs.) However, three characters is all I need to start this.
- The characters top military academy students from the Federated Commonwealth, in their final year of training at the New Avalon Institute of Science (NAIS) College of Military Science or The Nagelring, and are doing field work in experimental battlemechs in conjunction with the College of Engineering at NAIS, who are trying out various new technologies.
- The unit and their support staff find themselves out in Steelton in the Lyran Commonwealth side of the FC, doing field tests of sensor and targeting systems in dense sandstorm conditions and other inclement weather specifically.
- Inner Sphere tech only; it's 3050, right before certain things happen. (Not spoiling)
- Characters should be members of the AFFC -- Lyran or FedSuns side.
- Discord Link - Feel free to ask questions.

In Character Info:

3050; humanity has gone to the stars. But human nature hasn't changed much. In the last three hundred years, since the Star League Defense Forces jumped out of the Inner Sphere and into the beyond, the Inner Sphere has been wracked with a series of destructive wars to determine the succession of one of the Great Houses to the First Lordship of the Star League, a seat vacant since the Amaris Coup three hundred years ago. The only thing that's been accomplished is the near-destruction of space travel technology.

Right now, however, the Inner Sphere is in a good place. Thanks to Grayson Carlyle's recovery of the Helm Memory Core in 3028, technology is improving rapidly, a reversal from the fall of the Star League and the destruction of the Succession Wars when so much technology was lost that some planets were brought back to a 21st century standard of technology. With the marriage of Hanse Davion and Melissa Steiner, it seems inevitable that the unified Federated Commonwealth will eventually be able to bring the other three great houses to the negotiating table to revive the Star League, possibly without having a destructive war in the process. It feels like humanity turned a corner.

Graduation is a heady time for any student, but particularly for senior students at NAIS and the Nagelring, the best of whom are on a detached duty in the far reaches of the Lyran Commonwealth, finishing up a joint maneuver with regional militia and the 12th Star Guards, a mercenary unit, and testing new and different systems for the Armed Forces of the Federated Commonwealth. It's a cool assignment where the young mechwarriors get to use unusual and new pieces of technology and battlemechs in a variety of interesting field conditions as test pilots near the Periphery. Though there is little action to be had besides dealing with potential pirate attacks, they get to run exercises with an elite mercenary unit and, in general, be free of the day to day discipline of academy life. It's almost like a working vacation, a reprieve for all the hard work of four years of the Academy and the hard years before that, preparing to enter the Academy.

They don't expect what's coming for them from the Periphery. No one does.

Out of Character Info:

I can answer any and all battletech universe questions, but here's the essentials; your characters are Mechwarriors, and are most likely from a feudal class or wealthy background. While the militaries are becoming more egalitarian with the rediscovery of Lostech from the Helm Memory Core in 3028 the average mechwarrior is still the product of a feudal family and their retainers that have been piloting mechs, sometimes the same mech inherited from family, for generations.

They are on soft duty, so they think, but there is about to be a huge disruption to the Inner Sphere's status quo and it's going to come at them from the Periphery. They will not be prepared for it but they will have to deal with it.

I designed the unit, a small unit of mechwarriors working with technology types, so that the characters would have a good reason to be very inexperienced characters with very advanced equipment -- realistically, anything in the Inner Sphere could show up on these scientific studies -- including mechs that belong typically to other factions. I wanted to keep it flexible.

I realize that the amount of lore in this RP can be daunting, but I've been in on the lore stuff for this setting since childhood and I can cut through the confusion. If you are confused or not familiar with the setting, you can throw me a concept and I can work out a sheet for you that handles the history portion -- and I am willing to do this. I can assign titles, planets, and a degree of background sufficient to set up your character as credible in their position and then let you fill out the rest.

Samewise, I have a list of acceptable battlemechs to start with that make it easy; since the starting battlemech is just that and characters will be switching in the process of the RP, it's not hugely important to get the most perfect, bestest, awesomest mech from the outset, because your character won't be in it long (unless you love it). I am recommending light and medium mechs because this is still a training unit and because the maneuverability is important. It's not like you'll stay in them unless your character is just a big fan of the chassis.
Hello folks,

I'll get a structure up for character sheets. I can answer lots of questions in the Discord channel I'll set up for the purpose.

I am looking at a medium lance here, which means mechs up to 65 or so tons, and the lower end should be in the 30 ton range. General combatant unit capable of heavy reconnaissance, raiding, fire support and light line of battle work. Anything under 65 tons on this list should be a safe bet and a good starting point. The heavier mechs in this unit should at least do 50kph walking speed, but a Catapult is acceptable because it has jump jets.

© 2007-2024
BBCode Cheatsheet