Hi everyone, Oliver here. Today’s blog is about the design – and the design challenges – of one crucial part of your Imperial intelligence network: the Imperial Inquisition.
The Inquisition are an elite group of highly-trained characters, able and licensed to arrest and prosecute the highest-ranking aristocrats in the Empire. They are your most precise and deadly weapon against treacherous underlings. But with great power comes great responsibility – responsibility even the Sun Emperor cannot override. The Inquisition, when they interrogate a suspect, will find the truth – even if that truth is not what you thought or hoped it would be. And, if the suspect is innocent, they will be free – and extremely angry.
The first design problem, building the Inquisition, is to make sure they don’t step on the corruption- and secret-hunting gameplay I described in my last post on the Intrigue system. They provide the payoff – they’re how you find out whether or not your reasoning (or guesswork) was correct – but you mustn’t simply be able to sic them on every character who looks at you funny. Thus, they always find the truth, but setting them on an innocent character will turn that character implacably against you. If that isn’t enough to stop Inquisitor-spam displacing interesting detective work, we might make you pay compensation to innocent victims of Inquisitorial investigation.
The second problem is how ‘human’ to make them. Can any character become an Inquisitor? If they’re simply ciphers who do your bidding, there’s not much point having them at all. The solution we’ve settled on for the first iteration is that any character can, with your permission and years of training, become an Inquisitor – and that their relationships with characters will affect how likely they are to catch them if assigned to interrogate them. An Inquisitor would never come up with false results in an interrogation, but the target might suddenly take a long holiday on a fast ship just before their friend the Inquisitor arrives. So your assignment of Inquisitors will depend on how much you trust them to get the job done.
One of the problems the Inquisitor system solves is the question of how to give you control over your information and intelligence flow. By assigning Inquisitors to monitor particular territories, you can receive more information than you otherwise would about that planet, system, or province – the smaller the territory, the better the information you’ll get on it. This also helps make the Inquisitor-assignment gameplay interesting: where will it be useful for this particular Inquisitor to be? Where do you need good information? Who do you want them to be near to, just in case? One thing we might do is increase Inquisitors’ flow of Secrets from characters they’ve got good relations with, making placing Inquisitors in their friends’ territories a double-edged sword – more likely to produce information, but less likely to catch wrongdoers if you ask them to.
Two options for Inquisitorial work is not quite enough to make the choice of assignment interesting, however. The final piece of the puzzle (at least in the design for the first full alpha) is military commissar duty. By assigning an Inquisitor as a military commissar, you can reduce that Force’s chance of rebelling – but at the price of slowly degrading it, as officers get Inquisited and troops desert to escape the suddenly hostile work environment. Can you afford that cost, for loyalty? Can you afford not to pay it? The commissar system adds another interesting aspect to your military decision-making.
The key thing to understand about all this, though, is that it’s provisional. This is what we’re going to implement for the first alpha – after we (and our testers) have tried it, and seen how well it works, we might well find it’s either too much, or not enough. Perhaps we’ll need to give Inquisitors another function; perhaps they ought to be able to investigate corruption on their own; or perhaps they’ll turn out to be a layer of mechanics we don’t need at all. I hope we’ve got it right first time round, but the proof of the pudding’s in the eating.
I hope this post has let you see a little bit of the sort of thought processes we go through as we’re designing Imperia. In the next post, Steve will be talking about UI design, and how we’re reworking it from the bottom up.