• The regular administrative staff are taking a vacation, and in the meantime, Biigoh is taking over. See here for more information.
  • A notice about Rule 3 regarding sites hosting pirated/unauthorized content has been made. Please see here for details.
  • Staff is working to deal with the problem of synonymous tags. See here for more information and to suggest tag mergers.
  • Due to issues with external spam filters, QQ is currently unable to send any mail to Microsoft E-mail addresses. This includes any account at live.com, hotmail.com or msn.com. Signing up to the forum with one of these addresses will result in your verification E-mail never arriving. For best results, please use a different E-mail provider for your QQ address.
  • For prospective new members, a word of warning: don't use common names like Dennis, Simon, or Kenny if you decide to create an account. Spammers have used them all before you and gotten those names flagged in the anti-spam databases. Your account registration will be rejected because of it.
  • Since it has happened MULTIPLE times now, I want to be very clear about this. You do not get to abandon an account and create a new one. You do not get to pass an account to someone else and create a new one. If you do so anyway, you will be banned for creating sockpuppets.
  • Due to the actions of particularly persistent spammers and trolls, we will be banning disposable email addresses from today onward.

Governor's Gambit - Star Wars SI into Imperial Governor

Idea for Omake: Nearby Moff decides to recruit Khaduss the Hutt (who was one of candidates for Las's new Secretary), but Khaduss's competence combined with Moff's own incompetence quickly cause latter's political opponents to joke that "it's only Sector where Hutt is a Moff... and nobody minds" behind his/her back
 
Omake: Project Watering Down New
Omake: Project Alloy Extend

Mytoan Mixed Reinforcement Battalion Order of Battle and Doctrine Review by General Frast Volga

MMRB Order of Battle

Type: Quick reaction unit

Sub-type: Low-cost anti-raid force

Troop numbers (excluding support personnel and droids):

  • ~800-900 Combat personnel
  • 2 Imperial Army Imperial Auxiliary Companies (298)
  • 1 Imperial Army Repuslorlift company (220)
  • 1 Imperial Army Line company (180)
  • 25-100 IGCPP mercenary specialists
  • 2 Flight groups of TIE/Mindas or other starfighters
Background

With the onset of the Syndicate War, a fresh wave of chaos and raiding struck the Myto Sector. This led to a hastening of the continuous adaptations and changes to the Order of Battle for the Imperial Military in the Myto Sector. There was little concern of actually losing a world or even a major settlement. Rather it was to avoid disrupting the economy on those worlds by enacting costly civilian mobilization and the raising of militias to deal with the threat.

Therefore one of the most pressing matters was to develop a low-cost anti-raiding formation developed under Project Alloy Extend. This formation could be sent to ensure order and a continuation of daily life on various worlds under threat from inter-Syndicate warfare and those that would take advantage of the confusion. Now when one thinks of lowering cost in the Myto Sector, one tends to think of the Imperial Auxiliary Battalions. Objections have continued to be noted and welcomed against further integration of the Auxiliaries. Nevertheless, this new wave of disorder brought about by Syndicate violence, the Auxiliaries' past performance against previous pirate raids, and the Grand Moff's continued focus of the Oversector's forces in the direction of the Mid Rim have convinced Sector Command of the potential benefits of attempting further embedding Auxiliaries into the standard Imperial structure.

The result of this attempt was the Myto Mixed Reinforcement Battalion. A mixed formation made up mostly from common units available in the Imperial Military Secondment Deployment Pool. This mixing of primarily Imperial Auxiliary companies and standard Imperial Army companies was seen as way to handle remote, small scale warfare on frontier worlds while keeping the manpower and equipment costs low.

MMRB Formation

An MMRB is typically made up of four companies like most Imperial battalions, plus some extra additions. These battalions would tend to be between 800 and 900 combat personnel. A notable increase in military trained and equipped sentients on worlds they were sent to.

The main command battalion is an Imperial Army Line company. This company would focus on providing leadership and coordination with the other elements of the battalion from a central location. They would also provide a last line of defense should the raiders break through the other companies.

Two Imperial Auxiliary companies make up the largest element of an MMRB. These forces would man the first defenses in the predicted path of the raid. Should the raiders hit their defenses, the Auxiliaries are to hold out for further reinforcements or until large enough friendly casualties are taken.

The final company would be an Imperial Army Repulsorlift company. This would be the main offensive element of the battalion. While the other companies would focus on defensive and delaying tactics, the Repulsorlift company was there to deliver the decisive blow to either end the battle early or finish a battle that had become bogged down. Containing little heavy armor in its company, they rely on speed, surprise, and flanking to deal with their often ill-disciplined enemy.

There were also two main additions to the MMRB to increase its capacity to fight independently of the need arises. The first is two flights of TIE/Mindas or hopefully equivalent starfighters. A full squadron was proposed at first, but due to cost concerns, a defensive and an offensive flight were deemed sufficient for the formation. These fighters are meant to secure the skies and keep raider fighters and dropships from attacking Imperial civilians and soldiers as well as provide close air support once the skies are clear.

These second addition to the MMRB are IGCPP mercenaries. These are typically recruited from the local system or brought in from a nearby system on a contract for the single conflict. They typically serve as specialists for the MMRB such as skirmishers, scouts, infiltrators, heavy infantry, and occasionally pilots for vehicles owned by the mercenary. While rarely do these mercenaries stand on the battle line with the companies, their capabilities for independent actions allow the MMRB utilize tactical options beyond what their companies would normally allow.

Typical MMRB independent deployment strategy

MMRBs are most frequently sent to frontier worlds within the Myto Sector for short periods. They can be sent to more populous worlds, however usually the Imperial garrison and the PDF are able to handle the type of threat the MMRB was made to combat. MMRBs are typically sent to defend against a known or rumored threat of a raid on the planet. They typically fight raiding parties made up of raiders numbering in the mid to high hundreds to a little over a thousand.

Upon arrival the MMRB will assess the situation and the state of the local Imperial Garrison. If a battalion level commander or above exists, the MMRB will subordinate themselves to them and follow their battle plan. However should the Imperial Garrison lack such a rank, the MMRB's major will assume command and begin using their standard battle plan. Although the local Imperial commander will be kept as a direct advisor to the major in matters of local affairs and terrain regardless of their rank.

The MMRB's standard battle plan is a two step catch and strike strategy. They wish to meet the raiders with their defensive positions, before sending their mobile force to hit their flank and break their raiding party. Afterwards a mobile force and the battalion's starfighters will be dispatched to pursue the routing force and either destroy them entirely, or at minimum drive them off the planet.

Standard placement and assignment of their companies and their other elements reflects this strategy. An MMRB wishes to set up in a defensible terrain feature that the raiding force will have to go through while on the ground such as a valley or a bridge for a raging river. This is so the raiding force cannot just bypass the MMRB and head towards their objective.

The additional elements of the MMRB are essential for forcing the enemy to go along with this strategy. The starfighters will be separated into a defensive flight and an offensive flight. The defensive flight will prevent the enemy from just using dropships or their main ship to land on top of their objectives. Meanwhile the offensive flight goal is to harry the raiding force and trying to funnel them towards the MMRB's position while stopping them from spreading out to ravage the countryside. This harassment is also where the majority of the IGCPP mercenaries will be utilized. Their independent and often more agile nature being used to hit patrols and small parties of raiders that are not heading towards the MMRB's main force.

The two Imperial Auxiliary companies will be placed in two positions at the front of the MMRB's main position. Their placement should try to force the raiding force to either engage them, or divert towards the Line company's position. The Line company should be further back and between the two Auxiliary companies to catch any raiders trying to bypass their positions. The Repulsorlift company is typically positioned in a reserve position close to the frontlines while also able to head towards the raider's objective should they somehow get a force past the battalion's position. Once the raiders are engaged with any of the three infantry companies, the commander will order an element or the entirety of the Repulsorlift company kept in reserve to hit the raiding force in the flank or rear. A sudden attack from a vulnerable angle is usually sufficient to cause a raiding force to begin to suffer from morale breakdown. Should the raiding force overcome the MMRB's formation or the force prove far larger than expected, the battalion will engage in an orderly retreat to the world's capital and begin requesting for further Imperial reinforcements while trying to keep the main population centers of the world from being raided.

After the raiding forces have been confirmed destroyed or routed, the MMRB will be picked up from the system. The battalion will then be sent to the next system under threat by raiders after being resupplied with equipment and fresh troops. It would be preferable that there be an MMRB deployed to every system under threat medium term to deter further attacks. Unfortunately the current rate of raiding and the Sector's lack of sufficient manpower necessitates the MMRBs be quick reaction forces only deployed shortly before and then shortly after the raid. This need for mobility also means any further requests for medium to heavy artillery or heavy vehicles for an MMRB are denied as they do not fall in line with its light, mobile focus.

While this strategy may not contain much tactical complexity, it has been deemed within the capability of freshly graduated commanders from local academies. Thus this author recommends that we continue the practice of giving priority to command postings for the MMRBs to young commanders so that they may gain experience leading a battalion sized formation in engagements of relatively small scale and consequence. The notable diversity of units and troops should also allow Sector Command to determine which commanders have more Imperial valued mindsets in order to reward them with a reassignment fitting for such steadfast and loyal adherence to the tenets of the New Order.

Glory to the Emperor, Glory to the Empire.


——

With a bit of time passing, the military is bound to change to adapt to its current environment. I see the Imperial Military in the Myto Sector in an odd place undergoing feast and famine simultaneously. On one hand they have great access to local resources due to them not being mired in corruption and cutting edge technology, but on the other hand they also lack the enough of the traditional pools of manpower for widespread use of "standard" Imperial formations and tactics. At the top they have some of the most well equipped and technologically advanced forces in the Empire. Yet they are stretched thin, are low priority for outside resupply, and also on the Moff's orders not working the Imperial soldiers to the point of collapse with constant deployments. So at the bottom they have to rely on mercenaries and non-human soldiers to defend the entire breadth of their territory.

The MMRB is essentially the Myto Imperial Military opting to "water down" its "proper" Imperial Army units with Imperial Auxiliaries and mercenaries. This might be done in order to make the "proper" Imperial troops they do have stretch farther while also relegating these new "experimental" formations to out of the way (and out of sight of the wider Empire) areas of operation to avoid scrutiny. With 200 systems to defend and rising with colonization, combined with less aid from the Oversector, sacrifices are probably going to be made to keep everything defended. At least the Auxiliaries are getting a bit more combat experience and a tiny bit of glory and credit.

The MMRB also serves to give a sense of the scale a lot of the Myto Sector is dealing with at this time. Frontier systems have around 3-7 hundred thousand sentients each and make up almost half of the 200 notable systems in the Myto Sector. If say up to 1% of the local population in a Frontier System is employed full time for local planetary defense during low or no mobilization that's still only 3-7 thousand people to work with, and with each additional percentage mobilized leading to exponentially more damage to the system's civilian economy. Also a lot of those troops are going to be in noncombat roles like logistics, maintenance, and bureaucracy, even if droids are available to lighten the load. With that scale in mind, suddenly 800+ "elite" combat troops (i.e. higher status than militia or PDF) and their support staff start looking a bit more impactful. Also a raiding party of a few hundred pirates attacking a planet become a much greater local threat.

Crossposted on SB and SV

Edit: changed the project name to something a little less blatant, but carrying the same connotation due to some feedback on another site.
 
Last edited:
Chp-119 New
Chp-119

Admiral Gerel Dionhar
Akahista Orbit
3.1 ABY


Admiral Dionhar stared at the vessel through the shuttle viewport. The Vigil of Starless Night hung before him, the second ever Arbiter-Class vessel.

A cowards ship, meant only to stay behind the vessels of true warriors. Fitting that the Moff had chosen it as their meeting place.

Oh, he was aware that calling a Moff a coward would be career suicide. At least, for most Admirals. Dionhar wasn't under the command of the local Moff, after all, and reported instead to the Grand Moff directly.

A prestigious position, if only it didn't also leave him in the ass end of nowhere without a chance at glory or prestige in combat.

Upon the shuttles docking, he disembarked into the hangar. It was vast, holding countless TIE's of various types, many of those being the newfangled Mytoan variants he'd seen in the Akahistan's governors forces.

Above him claws held individual fighters along a rail system, while on the ground sat larger vessels.

Before him stood an aide who nervously guided him towards the meeting room.

The halls of the vessel were lively with personnel rushing to and fro. At the same time, those hallways disgusted him.

On one wall, there was a poster for a Walker-Ball match in the hanger! If this had been his ship, he would've personally executed anyone who dared to suggest such a blatant waste of time and effort!

It was clear to him how the Moff liked to run things, and it felt distinctly anti-imperial. Still, Dionhar held his tongue. This would all be in a report to the Grand Moff anyways, and if Kaine had any sense Mola would be demoted.

Soon he found himself inside the meeting room, a utilitarian place with not a decoration in sight, simply two chairs and a table, sitting across from the Moff himself. A large, lizard-like creature wound itself around his shoulders, eyes seeming to bore into his soul.

"Glad to meet you, Admiral Dionhar." Said the Moff, reaching a hand out to shake. He accepted, if only to keep up the veneer of politeness.

"The pleasure is mine, Moff Mola. Now, what brings you to my post? Its rare for my position to get visitors."

The Moff before him straightened in his chair, eyes tightening. He removed from his pocket a small disk, a holo projector, placing it on the table.

Upon activation, it showcased a map of the galaxy. Markings showcased fleet movements, policing actions, and more.

"Can you see the pattern, Admiral Dionhar?"

He stared at the map for a little while longer, trying as he might to find it. "No, I'm afraid not, Moff Mola. What is the meaning of this?"

"The pattern, Admiral, is the Crimson Dawn. In every known sighting in the past months, the Dawn has gotten away. In fact, overall sightings of Dawn ships have dropped dramatically. Almost as if they knew where Imperial ships were going to be."

In a flash, Dionhar was at his feet, hands slamming into the table. "Are you accusing me of treason!? How dare you! I was personally chosen by the Grand Moff himself!"

Mola stayed infuriatingly calm, his posture unchanging even as his eyes scanned the Admiral. The lizard let out a low, almost threatening rumble. Dionhar avoided looking at it.

"Calm yourself. I'm not making any accusations here. If I suspected you to be a traitor, we wouldn't be having a conversation in the first place."

Dionhar huffed, dropping back down into his chair. "So, what? Am I to believe that somehow spies have infiltrated the Hub? It's one of the most tightly secured facilities in the galaxy, of that I've made sure."

"And yet, like all facilities, it's connected to the holonet."

The Admiral frowned. "At best a slicer could listen in on encrypted comms, and we change the encryption every other week, as well as the techs making the codes, and the five teams of people adding more complexity to the encryption. Safe to say, the Dawn would need to compromise nearly a hundred people."

"Thats not what I mean, though it is something that should be checked. No, what I mean is, last year, someone took down the holonet relays. In the panic, ships were pulled from Akahista."

Dionhar leaned forward. "You mean to tell me that somehow, Crimson Dawn caused the relay blackout to infiltrate the Hub?"

"It seems the only explanation" was Mola's response, gesturing towards the projector. "The data lines up. And the Dawn is specialized in infiltration. If anyone could do it, it would be them."

Dionhar felt a thin bead of sweat start to form despite the room's chill. This was…bad. Very bad. He didn't quite believe it, but that didn't matter. What mattered is that it was believable enough, and as such if this information was revealed to his superiors…

Well, Naval HIGHCOM had a habit of scapegoating whenever possible. He'd be lucky to be demoted.

Before he could continue to deny the accusations, the Moff spoke.

"I come to you with this so that we may coordinate. By investigating this issue with the help of the Governor-General and ISB, we may yet find the spies."

"You want to bring the ISB in on this?" Dionhar was in shock. To purposefully bring in the ISB, or any of their superiors, was a death sentence!

"Of course. They will eventually, inevitably, discover the same information I have. Better we report it ourselves and work with them to fix this."

"It'll see us both demoted at best!"

Here the Moff seemed to grow angry, his voice rising just a tad. "Admiral. We are servants of the Emperor. If demotion is the punishment for our failure, then so be it. I will be sending the message in 24 hours. Full cooperation will be expected."

Dionhar studied the Moffs face. A patriot? A real Imperial patriot? Damnation, why did he have to get stuck in a room with the rarest species in the galaxy!?

"...I understand. For the Empire, Moff Mola."

"For the Empire."

They saluted one another, and Dionhar left the room at a quicker pace than he'd entered with. He had no time to waste, after all. And that lizard scared him.

It was imperative he get to the Hub, and change the outgoing logs! His master override should work, and so if he could just change the logs, erase evidence he changed them, he could buy himself time.

After all, the ISB would arrive, see completely normal looking logs, and then leave to focus on the Moff wasting their time! It would give him the time he needed to track down these spies, if they existed.

And if they didn't, the logs would be perfectly fine, and he'd be perfectly fine. But the sweat upon his brown betrayed the truth.

If there was even the slightest chance the Moff was right, he had to check!



Akahista, Pyramid One
3.1 ABY


Three shadows crept down the side of the building, silent limbs using magnets to avoid the treacherous fall.

They had inserted themselves in the dead of the planet's night cycle, and now poised themselves before the gaps between the pyramids layers. A small maintenance shaft stood there, and quickly they entered, sleek black ID-10 making quick work of the electronic lock.

No noise was made as they swiftly passed through the hall, their armor covered head to toe in noise and signal dampening material.

Through the maintenance section they went, arriving swiftly into the main cooling bay of the pyramid. Here liquid was pumped in and out of the supercomputer above, then moved to sites further away in the city to cool off before being cycled back in.

From their hidden location, the shadows once again dispatched their droids, the red glow of their eyes removed to maintain their stealth. The metal creatures found their way to the cameras in the room, setting them to loop footage one by one until the room was blind to the security forces.

Then, they made their way to the engineering consoles. The shadows above fired small darts into some farther off machinery, small electrical discharges causing a commotion and bringing the engineers away from their consoles.

With unrestricted access, the droids hacked their way in, one droid accessing the panel and the other two plugging into the first droid in order to combine their processing power.

In seconds, pumps started to stutter. Liquid was sent out in short bursts rather than a continuous stream. A common enough glitch in coolant systems galaxy wide that the only eyebrows raised would be those of engineers wondering how such an advanced location would allow such failures.

Of course, such concerns would never be raised. After all, failures were things to be hidden in the Empire.

The shadows left their hiding space in short order, slipping into an open hatch in the coolant pipes. The stuttering pumps meant they weren't swimming in coolant, yet the pipes were far below a survivable temperature regardless.

Each of them activated simple heating packs stitched into their armor and checked their environmental seals before moving onwards. They held onto their droids, using the machine's propulsion to speed up through the waist high coolant.

Within a single harrowing minute, they were able to exit the cooling pipe and enter the colossal supercomputer, the Hub itself. Machinery lay all around them, piling high up above with crisscrossing wires and perilous gantries abound.

Not a single guardrail either, though workplace safety wasn't an Imperial concern.

Again, their droids went first, finding each and every camera along their path. The shadows climbed silently, grappling hooks pulling them upwards with ease.

Finally, they found themselves at the central access computer. The heart and soul of the compound.

Expert hands installed the device easily enough, hidden eyes scanning for threats where there were none. The second team across the facility had done well in drawing attention away from the computers center.

Soon, the second illegal modification to the computer was installed. They could've removed the first, it was right there. But its discovery was key. So, for now, they did as ordered.

Their path out was much the same, and within the hour three shadows slunk back into the darkness of the surrounding city.



Yo. For some reason writing just hasn't been coming to me as easily. Maybe i'm just not as excited to write this story, maybe i just don't like writing as much as I used to, who knows. I'll finish this story, as I promised, but it'll take more time. Its gotten almost out of control, this one, growing far beyond my intended premise. Did you know that in the beginning, I had intended the story to stop at Endor, with Las as a Governor? He was never supposed to become Moff, but I liked the idea so much I had to throw it in. Same with so many other aspects. And now I have a dozen characters I can barely remember and a rough draft of a plan for post-endor so rough it could be used as sandpaper.\

But, I said I'd finish the story, so I will. Planning will be refined and the chapters will be continuing. I expect that once this more stressful chapter of my life has passed this will come easier to me.

As for the cooking update, I actually did a few new things. Tried a new chocolate cake recipe, it was aight, honestly very moist even after a couple days but kinda bland. Great with ice cream tho. Also made some cucumber and zucchini bread, the former because I bought cucumbers by accident. Didn't like it, zucchini bread is better for sure.

Gonna go for braided danishes next, because normal danishes i buy from Costco piss me off. Too much of the cheese is left in the center in an island and you either toss it and waste food or eat it and get too much cheese taste which is gross.

-Freefaller
 
Nice! Well the political fallout is going to be massive, though the good news for Mola is that he isn't exactly in charge of the Hub's security and he did actually find the leak. That said, their best bet is to indeed find a scapegoat and luckily they might be able to brand a few Moffs working with the pirates and slavers as traitors, as those pirates and slavers might be using the stolen Hub data, even if it was purchased off the black market, rather than stolen directly.
 
Admiral Dionhar stared at the vessel through the shuttle viewport. The Vigil of Starless Night hung before him, the second ever Arbiter-Class vessel.

A cowards ship, meant only to stay behind the vessels of true warriors. Fitting that the Moff had chosen it as their meeting place.
If a political leader in charge of hundreds of systems is fighting on the front lines that mean something has gone very wrong.
On one wall, there was a poster for a Walker-Ball match in the hanger! If this had been his ship, he would've personally executed anyone who dared to suggest such a blatant waste of time and effort!
"Motivational posters are inefficient and users will flogged until motivation improves!"
It was imperative he get to the Hub, and change the outgoing logs! His master override should work, and so if he could just change the logs, erase evidence he changed them, he could buy himself time.
Oof, an admiral, one answering directly to the Grand Moff no less, getting caught doing this. That is going to put egg on Kaine's face and he is not going to be happy.

Wonder if it is enough to get Las' boss demoted for negligence? Probably not. Either way he is probably going to be relying on Las even more and give him yet more leeway to manage things in the "less important" parts of his Oversector.

Yo. For some reason writing just hasn't been coming to me as easily. Maybe i'm just not as excited to write this story, maybe i just don't like writing as much as I used to, who knows. I'll finish this story, as I promised, but it'll take more time. Its gotten almost out of control, this one, growing far beyond my intended premise. Did you know that in the beginning, I had intended the story to stop at Endor, with Las as a Governor? He was never supposed to become Moff, but I liked the idea so much I had to throw it in. Same with so many other aspects. And now I have a dozen characters I can barely remember and a rough draft of a plan for post-endor so rough it could be used as sandpaper.\

But, I said I'd finish the story, so I will. Planning will be refined and the chapters will be continuing. I expect that once this more stressful chapter of my life has passed this will come easier to me.
Feel free to take a break if you need it. Burnout is real and needs to be managed.
Gonna go for braided danishes next, because normal danishes i buy from Costco piss me off.
The sign of a true cook: getting angry at the store bought alternatives.
 
Last edited:
It's never a bad idea idea to take an extended break to plot out ideas, and develop an outline of major points to hit and go from there. It's best to start with a beginning and and ending point and start filling in from there. Having an open ended end goal makes it difficult to plot towards, because the end post keeps moving. Establish an end point you're comfortable with, and once you reach it you can leave a plot hook that gives you the possibility of continuing later, if you so choose.

As for characters, outside of major reoccurring characters that Las deals with regularly, just keep some brief notes on the more minor reoccurring characters, like Lop or some of the Governors, and if you need them again, pull up the notes and work from there. One shot characters that appear once for like a single instance glimpse of events unfolding can be listed and given a brief description who they are and where they appear and be done with. For major characters like Las's siblings, Veers, and others that Las interacts with frequently, the notes should be more detailed naturally because you've built them up more. That helps keep characters defined and allows you to quickly check active characters, their development, and where they could be brought in later if necessary. It may also be prudent to have a list of potential characters ready to introduce, depending on where the story goes, like having one governor who's a corrupt politician one that's a incompetent boot licker, that can be used depending on where the story goes. You had that with Las's mother, where she was a nebulous monolithic figure on the horizon, until we were actually introduced to her.

It could also be that you've reach a point where the story beat has reach a plateu, and you need something to make things active again. Currently, Las isn't doing much outside of delegation and working within upper levels of government that flows around him. However outside of these issues with the covert syndicates and pirates, there's not a lot going on, and thus the pacing is bogged down with smaller incremental additions that seem underwhelming compared to the more action packed fear driven build up of Las's Governorship. Now as a Moff, the responsibilities are larger, but the changes are more statistics and numbers, with little action and incremental adjustments. Meanwhile elsewhere you have both the Rebellion and the Empire and Vader running around on the complete opposite side of the galaxy, and no real contact with Las's sector besides the Rest, Repair, and Refit station.

It may be that without a driving force for his actions, like fear of his Mother, pushing Las to do more or press forward, you've reached a point where you need to actively add a new more direct driving point. Right now Las is going through the motions of being a Moff trying to deal with covert bullshit, Imperial politics, the issues with pirates and slavery, and not much else, instead of having a more direct pressing concern. The story started out as a "city" builder with external politics and internal issues with a governor trying to make things work just enough to keep his Mother from packing his shit off to a death sentence with medals. Now Las seems to actually be acting the part of a Moff rather than a guy forced into a governor role and trying to both learn on the fly and remain under the radar enough that he can get out of Dodge once he's clear of his Mother.

Perhaps focusing in one of the major side characters for a bit might help open up new channels for you to work with. Maybe a time skip towards something that brings action back into the mix that's more complex than a covert shenanigans that Las has no direct interaction with. You might also let the Syndicate issue fade into a side story where the Major side characters like Thorne are actively dealing with, and allow Las to focus on building up his sector, and experiencing the wonders of R&D with a loose budget again. All things to consider.
 
Last edited:
It really is the easiest thing to exploit from Imperials, hidden stuff.

Corruption is one thing, but treason is the hot button to avoid being pressed on. They always scramble to remove any culpability on their part or start throwing others under the bus. But when you tell them there's a timer, you can catch them in the act.

Now, whatever the admiral is rushing to hide that isn't related to the actual case, it's gonna be logged.


It's understandable that plans for a story to derail from what was originally planned, and what was once a simple list of characters to bloat into a booklet of names. But that is a sign of growth when your story expands beyond the borders of Myto.

Interesting enough, you actually did the rarest thing in isekai stories.

Not getting involved with the main story


I'm just waiting for MC to be labeled with Myto=Las to the Water=Lloyd by the people
 
Interesting enough, you actually did the rarest thing in isekai stories.

Not getting involved with the main story

Well, Las doesn't want to interact with main story, but main story wants to interact with him (see: Luke Skywalker's desire to come to Minda. In "worst case" he will get "great idea" to organize "new Jedi Order" there)
 

Users who are viewing this thread

Back
Top