Because a list only used to handle conflicts should reasonably only be used to resolve conflicts
I actually said ātol is a slightly modified narā myself
Then a friend of yours talked that idea out of me
But for real, canceling is really bad, it shouldnt happen
Just going per list is the basics what tol does
The golden rule is changing nothing but making it easier to use for human hosts and more complicated to understand
Canceling only happens between actions that would result in the āhigher on the orderā situation
I think that situation is poor from a balance standpoint (being lower on the list is actually punished by game mechanics)
1 Like
I really confused it with rarā¦
Ah heck
I like your solution
Thank you for writing it down
Also done right RAR can handle full feedback.
I know because Iāve programmed a mafia simulation that used RAR and would give detailed results for each player.
It was much simpler than ToL of course. But it included:
A Cop
A roleblocker
A Vigilante
A bus driver
A doctor
Some Mafia
An NK
Some Villagers
Each role also had a copy to test interacting with itself and the program could handle altering the list size and number of each role.
Regardless though the point is that I was successfully able to get consistent action results simply by counting feedback you get from an action as another result to be checked, thus using the result consistencies to produce the effect of action consistencies from the PoV of each player.
To ensure that it truly was a working RAR system part of the code randomizes the order of the action list. Thus in order for the code to work the program must be able to get the same results no matter what order each action is resolved in. This was successful.
Also Iām thinking about remaking this program but with the ToL classes. If I succeed Iāll upload it here somewhere.
Is there a place where we can find removed/altered classes from the standard FoL format?
