Presented by: Lumi, Arete, Wiml, katze, Taffy
Special Thanks for helping to name all the avatar submissions: My spouse <3
Extra Special Thanks for being the site's SysAdmin and creating the Vote History for this game: DJarJar
RULE NUMBER ONE of KRC: You MAY NOT discuss the role you submitted in any way, shape, or form, anywhere (not even factional chats) other than in direct discussion with the host! Although you are free to discuss the role you received without any restrictions! (Note the difference between the role you submitted vs the role you received!)
Revealing mechanics of the role you submitted will result in a modkill.
Revealing the name of the role you submitted will result in a modkill.
Softing mechanics, softing the name - modkill for both.
You know what role you submitted and may make decisions and actions accounting for that knowledge (e.g you do not have to intentionally perform sub-optimal actions in order to act uninformed), but aside from that you must act and post as if all the roles in this game were created by me and you have no knowledge on what roles are in the game.
Players attempting to hunt or deduce role submissions of living players anywhere other than in their own head/in communication with the host will also be in violation of this rule.
10 posts per day phase minimum. Anyone that fails to meet this will be modkilled and exit the game with a loss, regardless of reason. If there is an early hammer then it will be at my discretion if I think someone has posted enough to not get modkilled.
There will be no subs, Only Mod Kills.
This game is SEMI-ANONYMOUS. That means that the player list will be public, but everyone will receive an anonymous forum account.
Despite the public player list, you should treat this game like an anon game. Do not mention identities or meta reads on other players at any point. Any attempts to hunt other players mains, out your own main, soft your own main, or cleverly circumvent these rules is liable to being modkilled. You are free to think about these things, or muse about them with the hosts - but none of these thoughts should be evident in your actual posts. Additionally, particularly idiosyncratic players do not need to attempt to alter their playstyle in an attempt to remain anonymous, although the line between idiosyncrasy and softing your main is a fine line that players should be cognizant of and tread carefully. If you have questions on what is or isn't allowed, contacts the hosts.
Cryptography is forbidden. Breadcrumbing is okay.
Never post screenshots of anything. Do not screenshot the thread, do not screenshot private chats, do not screenshot mod communication, do not screenshot. If you wish to quote something, paraphrase it.
The only player communication you are allowed to copy paste is either from the thread to a private chat or to a factional chat. Or from a private chat to a factional chat.
Pasting your rolecard, night feedback, or day feedback in factional chats is okay. Copy + Pasting anywhere else or pasting any other forms of mod communication in factional chats is forbidden.
If you are unsure of what is allowed, ask first.
You may not modify your profile picture or signature at any point during the game.
I reserve the right to modify these rules if needed.
Last edited by Lumi; April 11th, 2023 at 03:48 PM.
Mechanics Accounts:
Anonymous accounts, an account will be provided for you
Phase Length:
48 hour days, 24 hour nights.
SoD/EoD Time:
7 PM US Central Time
Day Action Deadline (including day votes):
Exactly at posted EoD Time. X:59 = good, X:00 = too late
Night Action Deadline:
2 hours before SoD
Instantaneous Effect Actions Deadline:
Actions with instantaneous effect cannot be used during the 2 hour period before SoD nor in the 1 hour period before EoD
Early Hammers:
Night is always at least 20 hours long with SoD occurring at the soonest following 7 PM time.
Elimination Type:
Plurality Elimination on Day 1. Plurality with Majority Hammer on Days 2+
Votes to hammer is equal to 51% of the number of living players, rounded up.
Sleeping/Skipping:
Sleeping/Skipping is allowed.
Last Wills:
Last Wills are allowed
Death Notes:
Death Notes are allowed
Suicide:
Suicide is not allowed
Self-Votes:
Self-votes do not count, the bot doesn't even register them.
Factional Chats:
Factional chats will be on Discord. Factional chats will NOT be anonymous.
Private Chats:
Private Chats will be on Xoyondo.
In-Thread Attacks:
Yes. Refer to the In-Thread Attacks section for more details
Starting Day 2, all players may, once per day, shoot at another player.
Unless modified by a role ability, this shot is public, regardless of if it hits or not.
The player who is shot will have a percentage chance of immediately dying and flipping.
ITAs can only be used during pre-set time windows.
ITAs will be disabled when the total number of living players falls below a secret threshold.
The default percentage chance of hitting will be decided based on overall setup balance, but will likely be around 15%. This may be affected by role abilities.
In-Thread Attack Windows: Window 1: 18 hours after SoD from 1 PM to 2 PM US Central Time.
View in your local time zone: Link
Window 2: 25 hours after SoD from 8 PM to 9 PM US Central Time
View in your local time zone: Link
Can rolecards contain hidden information or false information?
It is possible.
Will players know their true alignment?
Yes, players will always know their own true alignment.
Will players know their true win condition?
Yes, players will always know their own true win condition.
Why wasn't my question answered?
I respond to all questions, even ones that I won't answer (e.g "No comment" or "¯\_(ツ)_/¯"). If it feels like I missed your question, then I probably missed your question and you are free to ask again. Getting 1 notification from a user vs multiple notifications from a user is effectively the same to me, so don't worry!
What is the difference between factional actions and role actions?
Factional actions are granted by a player's faction. Role actions are granted by their role. But other than that distinction they are all just treated as actions unless a role explicitly specifies otherwise (e.g a roleblock will stop a factional action just the same as a role action)
Can you rand your own role?
No. (The math behind the probability of someone randing their own role is fun: Derangements)
Was my role modified after I submitted it? Will I know if it was modified?
The balance team had two primary goals:
- To make a fun and balanced game for all roles and factions
- To alter as little about roles as we can in pursuit of this goal
We did our best to change as little as we can about submitted roles. But if your role was changed, you were not notified, and will not be notified.
Was the role I received altered?
I cannot comment on that, refer to the previous question.
When a player dies and their submitted role is revealed, is the version of the role they submitted shown? Or is the final, potentially-modified version that was actually randed shown?
The final version of the role that was potentially modified by the hosts will be shown.
When a player dies and their submitted role is revealed, is hidden information for the role shown?
Often, yes, but partial hidden information or none of the hidden information is also possible. It is a balance decision made by the hosts during the pre-game balancing.
When a player dies and their received role is revealed, is hidden information for the role shown?
Yes, when a player dies and the role they received is revealed, all hidden information for that role is revealed, UNLESS the flip was modified in some way, in which case whether or not hidden information is revealed depends on the nature of the modification.
What exactly is hidden information?
Hidden information refers to any sort of information on rolecards that is hidden in certain circumstances, examples of possible hidden information include, but are not limited to:
- Hidden from the recipient of the role
- Hidden from role-cops
- Hidden during the role-submitter's flip
Information that is hidden to role-cops or hidden during the role-submitter's flip may or may not be indicated as such on a player's role card.
Submitted roles must be alignment agnostic, do modifications to a role made during host balancing also have to be alignment agnostic? No, it is possible that a role was modified with a specific alignment in mind.
What is the OoO?
I refer to the OoO I use as "Paradox Avoidant Simultaneous Execution" meaning all actions happen simultaneously - unless a paradox would occur. If a paradox would occur then the paradox inducing roles are executed in a predetermined order instead.
In 99% of cases this functions exactly like a normal OoO, and you should probably stop reading here.
The major area where this differs from a traditional OoO is that roles that alter the execution of other roles do not have a strict hierarchy.
For example, imagine a setup with a Roleblocker and a Bus Driver. With a traditional OoO one of them has to go first, if the Roleblocker goes first then the Bus Driver can never protect other players from role blocks because the RB goes first in the OoO. If the Bus Driver goes first, then the Roleblocker can never stop the Bus Driver from swapping. But with simultaneous execution neither role acts as a trump card over the other role.
Spoiler : Examples :
Roleblocker blocks Player A
Bus Driver swaps Players A and B
Result: The Bus Driver redirects the block from Player A to Player B.
Roleblocker blocks Bus Driver
Bus Driver swaps Players A and B
Result: The swap is blocked
Spoiler : More Complicated Examples :
The way the simultaneous execution technically works is:
- Iterate over all possible action orderings (With n actions there are n! possible orderings)
- An action ordering is inconsistent if it results in a retrospective contradiction (e.g a role did their action but then later got roleblocked, therefore they shouldn't have been able to do that action)
- Ignore inconsistent orderings.
- For consistent orderings, add the outcome of that ordering to the set of valid outcomes.
- If there is exactly one valid outcome, use that outcome. If there are either 0 or 2+ valid outcomes, then a paradox occurred and the roles responsible for the paradox will be executed based on a predetermined hierarchy
Roleblocker blocks Player A
Bus Driver swaps themselves with Player A
Result: If the Bus Driver were to go first, then they would swap the roleblock onto themselves which is inconsistent because they already did their action. If the roleblocker goes first, then there is no inconsistency and Player A is roleblocked. So the effective OoO of Roleblocker -> Bus Driver is used
Roleblocker blocks Bus Driver
Bus Driver swaps themselves with Player A
Result: If the Roleblocker goes first, then the Bus Driver can't swap. This is a consistent outcome and is added to the set of valid outcomes. If the Bus Driver goes first, then the swap is redirected to Player A. This is also a valid outcome and is added to the set of valid outcomes. As the set of valid outcomes has two different solutions, a strict OoO is used instead and what happens depends on which role was given priority during set-up creation.
Spoiler : Abandon Hope All Ye Who Enter Here :
Bus Driver 1 swaps Bus Driver 2 with Player A
Bus Driver 2 swaps Bus Driver 1 with Player A
If Bus Driver 1 goes first, then:
1 -> 2
2 -> A
A -> 1
If Bus Driver 2 goes first, then:
1 -> A
2 -> 1
A -> 2
As there are two valid outcomes, a strict OoO is used and whichever bus driver was given priority during setup creation goes first. For the sake of example we can assume Bus Driver 1 has priority so the resulting outcome is:
1 -> 2
2 -> A
A -> 1
Same as the previous example, but add a roleblocker blocking Bus Driver 1.
Roleblocker blocks Bus Driver 1
Bus Driver 1 swaps Bus Driver 2 with Player A
Bus Driver 2 swaps Bus Driver 1 with Player A
There are 6 action execution orders:
1) R -> 1 -> 2 results in a paradox because Bus Driver 1 is blocked, but then later swapped, meaning retrospectively they shouldn't have been blocked. This is an inconsistent execution and is ruled out.
2) R -> 2 -> 1 has the same result as 1
3) 1 -> R -> 2 results in Bus Driver 1 getting to use their action, but then later being roleblocked, which is inconsistent, and this execution is ruled out.
4) 1 -> 2 -> R results in Bus Driver 2 getting roleblocked, but this is inconsistent because bus driver 2 already got to use their action, and this execution is ruled out.
5) 2 -> R -> 1 results in Player A getting roleblocked, and Bus Driver 2 going before Bus Driver 1. The execution is consistent and so the outcome is added to the set of valid outcomes.
6) 2 -> 1 -> R has the same result as #5
There is only one valid outcome in the set of valid outcomes, so the action ordering of either 5 or 6 is used to produce the result where:
1 -> A
2 -> 1
A -> 2
And Player A gets roleblocked.
Notice that the only thing we changed from the previous example is we added a roleblock action into the mix. The roleblocked blocked neither bus driver, and yet the execution of the bus drivers' actions flipped. The existence of the roleblocker pruned the set of valid solutions and coerced the OoO into a different outcome despite the roleblock itself not actually hitting either bus driver.
Spoiler : An OoO resolution that runs in O(n!) ?? :
While the theoretical upper bound for the run time of this style of OoO resolution is O(n!) the search space can be greatly pruned by only considering actions that can affect other actions. Build a digraph of manipulative actions and then search for cycles on the constructed digraph. Disconnected components do not affect each other and can be executed separately. Acyclic connected components form a tree and can be rooted and then topologically sorted in order to determine their execution order. Only cyclic components on the digraph require O(n!) consideration, since the occurrence of cyclic components is very rare, and the ones that do occur are usually of a low order, the actual computation of the OoO is not O(n!) in practice.
Will main identities be revealed post game?
Yes. Remaining anonymous post-game is not an option.
What's the deal with night 0?
All role actions and all factional actions cannot be used on night 0 unless they explicitly specify otherwise. Night 0 exists because at least one role exists that requires a night 0. If your role PM makes no mention of night 0 abilities, then you don't have to worry about doing anything during night 0.
Can I target myself?
Abilities may only self-target if they explicitly state that they are able to. If this explicit statement is absent, they may not self-target.
How do Death Notes Work?
Non-Town players may include a death note alongside any killing actions they submit. Town players may only include a death note if specifically permitted to through their role. If a player who dies during the night was targeted by a killing action with a death note, said death note will be included alongside the flip.
Last edited by Lumi; April 14th, 2023 at 12:41 AM.
Terminology The Thread - the public game thread Private Chats - private chats on Xoyondo where you do not know the alignment of the other members of the chat (e.g Neighborhoods, Architect Chats, etc) Factional Chats - private chats on Discord where the alignment of all members of the chat is mod confirmed to be the same and the main account identity of all faction members is known. In KRC members of a factional chat may have alternative win-cons, but it will always be guaranteed that all members of the chat may obtain a win through their shared win-con. (e.g Mafia factional chat, Masonries, etc) Host Chats - each slot's private group chat on Discord directly with the host team. If a slot is a hydra then all members of the hydra will be in the same host chat. Host chats are guaranteed to be private and will not be released after the game.
Alignment - the team someone is playing for. Members of the same non-town alignment will have access to a 24/7 factional chat with all members of that same alignment unless specified otherwise. Faction - another word for alignment. A faction may have any number of players, including just one. Factional Actions - non-town factions will gain access to some number (possibly zero, possibly one, possibly many) of shared factional actions that can be performed for free alongside their regular role actions. Each factional action must be assigned to a member of the faction unless specified otherwise. Roleblocks will block factional actions unless specified otherwise. Likewise, factional actions are subject to any other game effects as well (tracking, redirection, manipulation, etc.)
Role - the role that a player receives. Roles are alignment agnostic and any role can be assigned to any alignment. Role Actions - the actions granted to a player from their role, as opposed to factional actions.
Anti-Town Faction - a faction is anti-town if town cannot win as long as any anti-town faction members are alive. Although it may be possible for anti-town factions to win with town still alive.
The day ends at EXACTLY 7 PM CST.
Day action submission deadline is 6 PM CST (1 hour before EoD)
Night action submission deadline is 5 PM CST (2 hours before SoD)
X:59 = Good
X:00 = Bad
No exceptions will be made to any of these deadlines.
Where to Submit Actions?
We will be using Discord to process action submissions and to send night feedback. Please submit night actions on Discord and check Discord for any day/night feedback.
protip for everyone: go to Settings in the top right and then scroll down to General Settings on the left and go all the way down and hit "Check For New Replies When Posting" to turn that off