Tuesday, May 06, 2025

Proposal: Taking stock

In “The Break-In”, change

Post a blog entry announcing the end of the Break In, and naming all Burglars

to

Post a blog entry announcing the end of the Break In, specifying the Location of each Artifact, and naming all Burglars

If it is the Planning the Break-In phase and at least five EVCs contain the word “tonight”, then make these changes to both the dynastic and shadow ruleset, rather than just the shadow ruleset.

It feels like a bit of a let-down that when Artifacts get stolen, neither the Burglars nor the Guards discover who stole them. And it’s strange that a Guard can intercept a Burglar and prevent them getting away with an Artifact, but remain unaware that any of that happened (they discover that they caught a Burglar but not whether the Burglar had anything on them at the time). I think the game would be more fun if there were a little more context available for the two sides to celebrate or commiserate as appropriate.

The edited step comes before the step that sets up Artifacts for the next round, so it will report on the Artifacts at the end of the round that just completed.

Comments

JonathanDark: he/him

06-05-2025 23:54:01 UTC

for tonight

DoomedIdeas: he/him

07-05-2025 05:00:04 UTC

for tonight

Kevan: Concierge he/him

07-05-2025 07:35:30 UTC

imperial

Kevan: Concierge he/him

07-05-2025 11:11:38 UTC

I think the basic lack of reveal makes sense narratively: why would everyone always be able to tell exactly who had stolen what? If it can’t be worked out from public information and Infamy gains, it’s up to the Burglars whether they want to reveal what they did.

Guards being under orders not to search the Burglars isn’t implausible, they could be passing them on to another team. I think the only fundamentally odd logical gap is that a Burglar won’t always personally know for sure which thing they actually stole.

DoomedIdeas: he/him

07-05-2025 16:36:24 UTC

against CoV. Betrayal is funny, and should be encouraged.

JonathanDark: he/him

07-05-2025 17:08:23 UTC

Kevan has a good point. CoV against

ais523:

07-05-2025 19:41:15 UTC

@Kevan: I basically think that this sort of dynasty is less fun if you don’t know what happened in it.

It doesn’t do much to encourage betrayal, because it is very likely that someone who betrays will be found out – too many people will know what happened (including you). After the dynasty I will be asking people to post all the information they know about what happened, in order to update the historical record: people who didn’t betray will have no reason not to reveal the information, and so we will be able to determine who was betraying by seeing who is unwilling to post their information.

Note also that if there is a betrayal that somehow remains hidden, it gives Kevan an unfair advantage in future dynasties (because at least he will know who was betraying). It may be important for other players to vote to prevent Kevan keeping information secret in order to avoid him getting an advantage in future.

Kevan: Concierge he/him

07-05-2025 21:41:34 UTC

I think there’s definitely some puzzle-solving enjoyment (and social deduction gameplay) in players trying to work out what just happened based on partial information, rather than being given a more direct reveal.

I really doubt that I’m getting much insight into betrayals from here. I’m processing all of the actions, but with no context on any private agreements - I don’t know what individual players were expecting or not expecting to happen.

Darknight: he/him

07-05-2025 21:49:53 UTC

imperial

ais523:

07-05-2025 22:10:32 UTC

@Kevan: But I’ll post all that information (that I know) post-dynasty so you’ll find out about it from there, and expect that enough other players will do the same that it all becomes public.

DoomedIdeas: he/him

07-05-2025 23:56:24 UTC

Wasn’t there a previous Dynasty that Kevan ran where the players voted to ensure he could never reveal what happened, to ensure nobody would be punished in later Dynasties for their betrayals? If there’s a set precedent of “not all information needs to be revealed”, should we follow it?

ais523:

08-05-2025 01:07:48 UTC

IIRC that was Josh, not Kevan.

FWIW I think that the voting on such things should generally depend on whether you’re planning to betray people or not. If you aren’t, it’s in your interest to get the rules changed so that other people can’t either – such a rules change would benefit you by giving certainty, and by removing options that you aren’t planning to take advantage of but that other players might. (Note that this mostly only applies in dynasties where the intended conventional play involves players needing to trust each other – although I wasn’t there and don’t have the details fully memorised, I think the context for the “we’ll agree never to reveal” involved a player trying to take extreme steps to protect a pooling agreement in a dynasty where the conventional play didn’t involve pooling, so the proposal was intended to weaken pooling rather than strengthen betrayal. But in this dynasty, a betrayal is more likely to be intended to undermine the Burglar/Guard team you’re on than to intended to undermine a pooling agreement.)

In general, if you suspect other players are up to something, a very good strategy is to write a proposal that would prevent it, to see how the votes go (e.g. in Desertfrog I I suspect that there was a pooling agreement between other players that I didn’t know about, and submitted a proposal to ban pooling to see who would vote against it, because I wasn’t planning to pool myself). Anyone who votes AGAINST it should be considered as potentially being untrustworthy and not a good person to make deals with.

The standard counterstrategy to this is to vote AGAINST but to give an unrelated reason, but it’s generally fairly easy to see through. For example, in Desertfrog I my proposal lead to this thread in which Josh criticised my attempts to determine, via the proposal system, whether he was trying to pool or not (and argued in favour of allowing pooling in general in much the same way that Kevan is arguing in favour of allowing betrayal in general). But (as was revealed after the dynasty) Josh was in fact trying to pool at the time.

So I guess this is just a case of how you view the proposal system. Some players view it as “trying to make a good game, and then we play it without using proposals”, in which case you vote on whether you think proposals improve the game or not (although I think that the possibility of betrayal doesn’t improve the game much in this case – trying to cover everything as Guards, or to find gaps in the plans as Burglars, is interesting in its own right, but betrayals mostly make that part of the game irrelevant). Other players, however, prefer a more nomic-style view in which proposals are used to try to gain an advantage in a dynasty (e.g. although my proposals are generally intended to improve the game, usually by fixing loopholes, I fix loopholes selectively in order to leave in the ones that benefit me). In the latter case, it’s generally very powerful to use proposals to try to flush out subterfuge because players can’t vote against them without implying that they’re up to something.

(Kevan’s something of a special case here because, as far as I can tell, he seems to be fascinated in general by the prospect of betrayal, even though in practice it almost always seems to be a bad idea – it is too easy to determine that it’s happened and isn’t worth people never fully trusting you again. In at least one dynasty, he got surprised by the ending because he didn’t expect a couple of players to trust each other to the extent that they did. I suspect that this puts Kevan in a bad situation for trying to win dynasties in general, because it discourages people from trying to make agreements with him in dynasties where doing so is beneficial.)

You must be logged in as a player to post comments.