[X] Attack the ship
Many manufactories were build by Vita and I hope we can simply log in as an administrator and do shit.
I don't think we'll manage to build anything during the combat turn, building is for 5-year turns.Many manufactories were build by Vita and I hope we can simply log in as an administrator and do shit.
I think less building turn and more stompy robots starting to exit the factory instead of deck plating, boarding action from inside.I don't think we'll manage to build anything during the combat turn, building is for 5-year turns.
Question: can we, in any plan really, kill off Bongo before battle? It sucks to not milk it for all its worth, but given that its Chaos, it will probably try to mess with us, or magically send them (or through them) information on what we actually are, or whatever.
Question: can we, in any plan really, kill off Bongo before battle? It sucks to not milk it for all its worth, but given that its Chaos, it will probably try to mess with us, or magically send them (or through them) information on what we actually are, or whatever.
Not sure! There seems to be an idea going around right now that because Vita is bad at combat, that trying to do planning (or at least, as much planning as Hammer or Heart does) is a double-edged sword, which isn't what Neablis said at all:"Attack the ship" seems straightforward enough, but it provides zero tactical considerations or contingencies. Are people voting for this expecting a short update with just the outcome of this dice roll or that Neablis will take this simple directive and generate a full in-character analysis and approach?
It would be valid to pretty much just tack those thoughts into a plan. That pretty much means that Vita will have those thoughts and investigate using them.
The KISS rhetoric I've seen is either pointing out failure modes of Heart, or just... not specifying any specific failure modes at all.This. Depending on the write-in and what you're trying to do you'll succeed in different ways. A valuable question to ask yourself when considering a plan is "what are the failure modes?'
Because these are factories that Vita designed, and many of which she personally built, we actually get to try this time:I like this one, except IIRC our hacking does not happen at combat relevant speeds.
Neablis may or may not take thread discussion as a cue to have Vita try hacking during all of this - but the "Attack the ship" vote does not include it, so he's not obligated to have Vita come up with it if we don't put it in the vote.I'd let you try. It'd be a roll at least.You know it occurs to me that the manufactories feeding the shipyards were built using Vita's designs and codes so it's not inconceivable that she has backdoor access to those systems and can make them print out more combots so that she can take over them from the inside.
I explain my rationale for attempting a deception here: mouse-over commentary added after the fact."Shot through the Heart" provides more details, but I really don't get the point of this fake pretense of underestimating them. If you're going to do a deception, something like this feels like it has the lowest possibility of success. Also, manufacturing a reason to attack instead of just attacking without warning feels like a military tactic suited a for a drama instead of a fight to the death. I do like the boarding preparedness, the hacking attempts, and the coordination with W, though.
What Heart tries to do is change the main challenge into more of an intrigue problem, which Vita and Victan (and W!) are good at. Those three heads put together can absolutely sell a deception, and then accept the least tactical disadvantage needed to make sure the ship doesn't get away.
In fact, the plan doesn't say "accept tactical disadvantage" at all. I just personally would accept some if that's what it took to seal the deal. The secret squirrel alphabet gang will be figuring that part out for me, based on information we as players don't have.
So we can stay in character and amp up the possibility we get surrenders on the ground war and in the stations.
Besides letting us skip some fighting, I want live research subjects this time. We've got a chaos detection and treatment tech list to speed run, and I'm not passing up the opportunity to get more discounts for them.
We can treat apply treatment to them too some time later down the line too, but mostly I plan for them to go into comas or stasis when we're not poking them with a stick.
Really, the pretext is just me taking a shot at getting free stuff after the trouble of making sure the heavy cruiser doesn't run.
Thus, my preferred votes.[X] Plan: Hammer of an angry explorer
[X] Plan: Shot through the Heart
"Attack the ship" seems straightforward enough, but it provides zero tactical considerations or contingencies. Are people voting for this expecting a short update with just the outcome of this dice roll or that Neablis will take this simple directive and generate a full in-character analysis and approach?
Your post came pretty soon after mine, so maybe you missed it. But I make a pretty strong argument at the start of my post that you're going too far in the other direction.Because it is long past time that this thread start reeling it in on recursive contingency planning and be made to practice simple votes, in line with the quest philosophy and also practical limits on Neablis' time.
This is a widespread issue with quests, but it has been especially pronounced in this one, insisting on spending thousands of words expanding out literal one-line actions and burdening updates with the expectation of them.
This is such a plain thing. We have one ship. They have one (working) ship. We have to kill them. It does not and ought not to take a novel of planning and paranoid death spirals to resolve this subvote. It is also the option that Neablis offered to us directly.
Frankly, I hope after this we are no longer offered [] Write-In at all, or at least that some kind of strict limitation is put on it. This quest has actually, literally, gone and done this sort of thing in the middle of routine Construction actions to try and make it Just So. It's self-destructive to the quest on top of everything else, since Neablis does have to actually write the thing.
Because it is long past time that this thread start reeling it in on recursive contingency planning and be made to practice simple votes, in line with the quest philosophy and also practical limits on Neablis' time.
This is a widespread issue with quests, but it has been especially pronounced in this one, insisting on spending thousands of words expanding out literal one-line actions and burdening updates with the expectation of them.
This is such a plain thing. We have one ship. They have one (working) ship. We have to kill them. It does not and ought not to take a novel of planning and paranoid death spirals to resolve this subvote. It is also the option that Neablis offered to us directly.
Frankly, I hope after this we are no longer offered [] Write-In at all, or at least that some kind of strict limitation is put on it. This thread has actually, literally, gone and done this sort of thing in the middle of routine Construction actions to try and make it Just So. It's self-destructive to the quest on top of everything else, since Neablis does have to actually write the thing.
Minor correction with only calling space assets to war.
I agree with you that exhaustive micro-managing is terrible to read and interact with. Some quests I've read have gone off the deep end in that regard at times and it always proves to become a strain on the average reader's ability and willingness to engage with the decision-making process.Because it is long past time that this thread start reeling it in on recursive contingency planning and be made to practice simple votes, in line with the quest philosophy and also practical limits on Neablis' time.
This is a widespread issue with quests, but it has been especially pronounced in this one, insisting on spending thousands of words expanding out literal one-line actions and burdening updates with the expectation of them.
This is such a plain thing. We have one ship. They have one (working) ship. We have to kill them. It does not and ought not to take a novel of planning and paranoid death spirals to resolve this subvote. It is also the option that Neablis offered to us directly.
Frankly, I hope after this we are no longer offered [] Write-In at all, or at least that some kind of strict limitation is put on it. This thread has actually, literally, gone and done this sort of thing in the middle of routine Construction actions to try and make it Just So. It's self-destructive to the quest on top of everything else, since Neablis does have to actually write the thing.