Edge Cases

[CrowdfordBot]

mctsts: For some roles there's a significant section for edge cases, can we add an "Edge Cases" section for some roles?

[CrowdfordBot]

e_thsn: could you give an example <@242983689921888256>

[CrowdfordBot]

mctsts: I'm currently working on updating the Baker description:

**Baker** | Townsfolk Group
__Basics__
There is always more than one Baker. All the Bakers have a secret channel where they can communicate with the other Bakers securely.
__Details__
Bakers are a special type of townsfolk; they know all other players who gained the Baker role. They can fully trust and rely on each other. Bakers share a private channel, where they can communicate with each other. 
If a Baker loses their role, they will still keep access to the channel. This means that at some point, a Baker may betray the group. 
If a Baker is infected by the infecting wolf their role changes to bloody butcher, instead of wolf. If this happens, all other Bakers become butchers, and are notified of this change. 

I would update it to this:

**Baker** | Townsfolk Group
__Basics__
There is always more than one Baker. All the Bakers have a secret channel where they can communicate with the other Bakers securely.
Whenever the wolves eat a Baker, they will be able to use their powers twice.
__Details__
Bakers share a private channel, where they can communicate with each other. 
When the Wolfpack kills a Baker, each member of the pack will be able to use any of their role's powers another time during the next day/night. If a wolfish player kills a Baker, without using the pack's attack, only they will be able to use their power an additional time.
__Edge Cases__
If a Baker loses their role, they will still keep access to the channel. This means that at some point, a Baker may betray the group. 
If a Baker is infected by the infecting wolf their role changes to bloody butcher, instead of wolf. If this happens, all other Bakers become butchers, and are notified of this change. 

[CrowdfordBot]

mctsts: (note: all but the first lines of details are new)

[CrowdfordBot]

mctsts: huh

[CrowdfordBot]

e_thsn:

[CrowdfordBot]

mctsts:

I'm currently working on updating the Baker description:

**Baker** | Townsfolk Group
__Basics__
There is always more than one Baker. All the Bakers have a secret channel where they can communicate with the other Bakers securely.
__Details__
Bakers are a special type of townsfolk; they know all other players who gained the Baker role. They can fully trust and rely on each other. Bakers share a private channel, where they can communicate with each other. 
If a Baker loses their role, they will still keep access to the channel. This means that at some point, a Baker may betray the group. 
If a Baker is infected by the infecting wolf their role changes to bloody butcher, instead of wolf. If this happens, all other Bakers become butchers, and are notified of this change. 

I would update it to this:

**Baker** | Townsfolk Group
__Basics__
There is always more than one Baker. All the Bakers have a secret channel where they can communicate with the other Bakers securely.
Whenever the wolves eat a Baker, they will be able to use their powers twice.
__Details__
Bakers share a private channel, where they can communicate with each other. 
When the Wolfpack kills a Baker, each member of the pack will be able to use any of their role's powers another time during the next day/night. If a wolfish player kills a Baker, without using the pack's attack, only they will be able to use their power an additional time.
__Edge Cases__
If a Baker loses their role, they will still keep access to the channel. This means that at some point, a Baker may betray the group. 
If a Baker is infected by the infecting wolf their role changes to bloody butcher, instead of wolf. If this happens, all other Bakers become butchers, and are notified of this change. 

<@&1045732542399131769> <@&1128435183113220106> Opinions? Or maybe anyone have any alternative suggestion to improve the readability of roles

[CrowdfordBot]

e_thsn: Bring back the edge case document

I like it maybe have an extended role description with edgecases as well as just simplified and normal though

[CrowdfordBot]

mctsts: the edge case document was actually mainly not for edge cases

[CrowdfordBot]

mctsts: it mainly covered things such as aura teller/priest results and stuff like ice queen

[CrowdfordBot]

e_thsn: <:thonque:775345553600675850>

[CrowdfordBot]

mctsts: I feel like three different descriptions may be too much?

[CrowdfordBot]

mctsts: We could maybe replace the Simplified one with the Basics/Details one and the current Basics/Details becomes Basics/Details/Edge Cases

[CrowdfordBot]

shapechange: hmm

[CrowdfordBot]

shapechange: can't we just add the edge cases section to the basics/details info?

[CrowdfordBot]

e_thsn: how often does the simplified one get used?

[CrowdfordBot]

shapechange: that's what i was trying to think of

[CrowdfordBot]

e_thsn:

can't we just add the edge cases section to the basics/details info?

maybe it looks messy

[CrowdfordBot]

shapechange: it seems a shame to waste the effort put into those

[CrowdfordBot]

shapechange: i think either just adding it to the normal one or having a third command is best

[CrowdfordBot]

mctsts:

can't we just add the edge cases section to the basics/details info?

we can do that too

[CrowdfordBot]

e_thsn: what does it look like if you do that?

[CrowdfordBot]

shapechange: my only concern about that is the devil description - are there any devil edge cases?

[CrowdfordBot]

e_thsn: for bakers

[CrowdfordBot]

mctsts:

what does it look like if you do that?

thats what I sent above is it not?

[CrowdfordBot]

e_thsn:

my only concern about that is the devil description - are there any devil edge cases?

currently devil attacking macho and hags

[CrowdfordBot]

e_thsn:

thats what I sent above is it not?

oh I thought we were talking as part of Details not it's own description

[CrowdfordBot]

mctsts: Well thats what we have currently

[CrowdfordBot]

mctsts: so you can also see it in my message from the start <:pffffft:705639986384601110>

[CrowdfordBot]

e_thsn: Oh

[CrowdfordBot]

e_thsn: 🤦

[CrowdfordBot]

e_thsn: I am braindead

[CrowdfordBot]

shapechange: it's okay at least you're soulalive

[CrowdfordBot]

e_thsn: lmao

[CrowdfordBot]

shapechange: I'm going to have to do so many grammar checks aren't i

[CrowdfordBot]

e_thsn: I wish you luck but you're the best at grammar out of us

[CrowdfordBot]

mctsts: Well what are we doing?

[CrowdfordBot]

mctsts: Just changing $i so edge Cases are a separate section for some roles that you can skip if you want?

[CrowdfordBot]

e_thsn: yeah

[CrowdfordBot]

nottinghamshire: What’s the definition of an edge case

[CrowdfordBot]

e_thsn:

What’s the definition of an edge case

a case that occurs rarely

[CrowdfordBot]

e_thsn: for example

[CrowdfordBot]

e_thsn: baker becomes bloody butcher if turned by IW

[CrowdfordBot]

e_thsn: and all other bakers become butchers

[CrowdfordBot]

nottinghamshire: I understand

[CrowdfordBot]

nottinghamshire: I think it’s fine having edge cases as a desperate title underneath roles

[CrowdfordBot]

nottinghamshire: Seperate* not desperate

[CrowdfordBot]

e_thsn: <@242983689921888256> if we're sorting edgecases, if www kill rh through pack poll can they not use their ability to kill a pack member the next night?

[CrowdfordBot]

mctsts: uh

[CrowdfordBot]

mctsts: WWW can still attack. Could be reason for another issue if you think that seems unintentional

[CrowdfordBot]

venomousbirds: bring back edge case sheet