New TK suggestion

[CrowdfordBot]

e_thsn:

[CrowdfordBot]

mctsts: "unavoidable" is a strong term

[CrowdfordBot]

venomousbirds: unavoidable as in it cannot be stopped at all

[CrowdfordBot]

venomousbirds: like hod

[CrowdfordBot]

mctsts: We do not have that

[CrowdfordBot]

mctsts: HoD can be stopped

[CrowdfordBot]

venomousbirds: by killing hod

[CrowdfordBot]

venomousbirds: how else

[CrowdfordBot]

mctsts: no - by any effects that can stop killing

[CrowdfordBot]

mctsts: for example vampire

[CrowdfordBot]

venomousbirds: like what

[CrowdfordBot]

venomousbirds: thats not what im talking about

[CrowdfordBot]

mctsts: I can't think of other abilities that stop "killing"

[CrowdfordBot]

mctsts: But there's probably at least 1-2 more

[CrowdfordBot]

venomousbirds: yes, vamp beats most cases because it changes role

[CrowdfordBot]

e_thsn: Idiot

[CrowdfordBot]

venomousbirds: but im not taking that into consideration

[CrowdfordBot]

e_thsn: That's kill not attack

[CrowdfordBot]

mctsts: yep, idiot is triggered on "kill" too you're right

[CrowdfordBot]

mctsts: thus it can stop HoD and this role

[CrowdfordBot]

venomousbirds: hm okay

[CrowdfordBot]

mctsts: Idiot is the only town role that can do it iirc

[CrowdfordBot]

venomousbirds: so i define unavoidable by most roles dying from it instantly

[CrowdfordBot]

e_thsn: Kills don't affect a hooker (if the hookers target dies) too right?

[CrowdfordBot]

venomousbirds: so you guys are right

[CrowdfordBot]

mctsts: yea we usually use "unavoidable" to mean unavoidable(*) * except by demonized, idiot and maybe a few other rare cases

[CrowdfordBot]

e_thsn:

Kills don't affect a hooker (if the hookers target dies) too right?

Just checking interactions with kills

[CrowdfordBot]

venomousbirds: i think it should be specified tho

[CrowdfordBot]

mctsts: however we can't actually put "unavoidable" in the role desc, thus It's usually "(this is not an attack)"

[CrowdfordBot]

venomousbirds:

however we can't actually put "unavoidable" in the role desc, thus It's usually "(this is not an attack)"

thats what i mean

[CrowdfordBot]

mctsts: yeah this role should have it

[CrowdfordBot]

mctsts: as should chef

[CrowdfordBot]

venomousbirds: OH

[CrowdfordBot]

e_thsn: The pinned descriptions aren't final

[CrowdfordBot]

venomousbirds: i thought you were arguing that we definitely shouldnt put it in the description

[CrowdfordBot]

venomousbirds: hsjhfkdsf

[CrowdfordBot]

venomousbirds: but yea

[CrowdfordBot]

venomousbirds: it should be specified in chef in that case

[CrowdfordBot]

mctsts: <#1166824488185368727>

[CrowdfordBot]

venomousbirds: ethan change your pfp pls

[CrowdfordBot]

mctsts: It should definitely be specified - knowing the formal definitions of "kill" and "attack" is up to hosts

[CrowdfordBot]

captainluffy: well this post is like 2 months old, so we shuld probably finish up with it eventually

[CrowdfordBot]

e_thsn: Jay suggested that instead of 2 different flasks for simplicity we instead give them 1 flask type with 2 different uses which is probably better

[CrowdfordBot]

mctsts: or well when we specify "this is not an attack" people can at least look up the definitions as they'll know something is off

[CrowdfordBot]

e_thsn:

Jay suggested that instead of 2 different flasks for simplicity we instead give them 1 flask type with 2 different uses which is probably better

Anyone disagree

[CrowdfordBot]

mctsts: me

[CrowdfordBot]

captainluffy: its simpler but makes the role worse

[CrowdfordBot]

mctsts: I find it to be a pointless simplification that makes the role a bit worse

[CrowdfordBot]

e_thsn: Ok

[CrowdfordBot]

e_thsn: Also what amount do we want since fixed amount won

[CrowdfordBot]

mctsts: let me write an updated desc