new ability definition case

[CrowdfordBot]

WWR Sync: <@578133411110060033>

[CrowdfordBot]

mctsts: In some cases we need to chain things together without it ever getting back to the player

For example:

Aura Teller does two checks (for attributes and category) and then does an evaluation step to define the feedback:

We can define this as the following

Aura Teller Immediate Night: • Process: (1) Attribute Investigate @Selection for Lycan (2) Category Investigate @Selection • Evaluate: ‣ @Result1 is Success: Threat ‣ @Result2 is Killing: Threat ‣ Otherwise: Not a Threat

In this case the action processes several abilities internally without getting back to the player in Process and then determines what to tell the player in Evaluate

[CrowdfordBot]

mctsts: does that seem reasonable?

[CrowdfordBot]

e_thsn: is there any other examples?

[CrowdfordBot]

mctsts: I had some earlier I think

[CrowdfordBot]

mctsts: But I forgot them 🙂

[CrowdfordBot]

mctsts: oh plague carrier for example

[CrowdfordBot]

e_thsn: is exorcist one

[CrowdfordBot]

mctsts: oh pc can be avoided probably

[CrowdfordBot]

mctsts: exorcist: maybe, idk

[CrowdfordBot]

mctsts: oh oracle too

[CrowdfordBot]

e_thsn: is that two alignment checks with info being a comparison?

[CrowdfordBot]

mctsts: Oracle Immediate Night: • Process: (1) Alignment Investigate @Selection (2) Alignment Investigate @SeconarySelection • Evaluate: ‣ @Result1 is @Result2: Same Alignment ‣ Otherwise: Different Alignment

[CrowdfordBot]

e_thsn: yeah this all seems fine to me

[CrowdfordBot]

mctsts: I'm open for changes to the formant and replacing the words process/evaluate

[CrowdfordBot]

e_thsn: maybe AT can be if Result (1) is Success or Result (2) is Killing: Threat

[CrowdfordBot]

relaxedmato: Could just make the Process & Eval steps into one liners, to fit the rest of the actions

[CrowdfordBot]

mctsts: that would get problematic once you get 3 lines

[CrowdfordBot]

e_thsn: ah yeah

[CrowdfordBot]

mctsts: Priest End Night: • Process: ‣ Attribute Investigate @Selection for Lycan ‣ Alignment Investigate @Selection • Evaluate ‣ @Result1 is Success: Attack @Selection ‣ @Result2 is Townsfolk: True Kill @Selection ‣ Otherwise: Failure

[CrowdfordBot]

e_thsn: what if they're both

[CrowdfordBot]

mctsts: both die

[CrowdfordBot]

mctsts: I think we discussed this when we added RW

[CrowdfordBot]

mctsts: as intentional

[CrowdfordBot]

e_thsn: ah so it's like an if within an if statement not an else if statement

[CrowdfordBot]

mctsts: yea

[CrowdfordBot]

relaxedmato:

ah so it's like an if within an if statement not an else if statement

Or like a singe use do while loop

[CrowdfordBot]

e_thsn: hmm

[CrowdfordBot]

relaxedmato: Do { If Statement If Statement } While (alive)

[CrowdfordBot]

mctsts: I now defined complex actions https://github.com/McTsts/Werewolves-Roles/blob/formalize-ability-types/Formalization%20Guide.md#complex-actions

[CrowdfordBot]

mctsts: problem

[CrowdfordBot]

mctsts: attribute investigation for AT cant be affected by disguises

[CrowdfordBot]

mctsts: so AT is even more compelx

[CrowdfordBot]

mctsts: oh and oracle is more complex than my proposed formalization due to its limitation

[CrowdfordBot]

mctsts: but hey, priest works

[CrowdfordBot]

mctsts: 1/3

[CrowdfordBot]

captainluffy: 1/3 is something

[CrowdfordBot]

venomousbirds: Seems like this needs further discussion or isnt needed at all

[CrowdfordBot]

mctsts: Its implemented, closing this