12999th poster gets a cookie (cookie thread (Part 7)) (Part 8)

if i were to use this to code virtuous i would have to make a number of simplifications and bans (e.g. sibyl, judge, etc)

A very oversimplified explanation of Zugbot is that abilities are arbitrary functions, and the modbot will execute the functions without knowing what they do

This allows making roles do Anything, and it heavily decouples the main bot section of code from the roles.

The downside to this is that the roles become heavily coupled to eachother, so to fix that Iā€™ll be making a standard set of modifiers and subparts to roles, so that normal roles can be coupled only to the standard (and be much simpler to write), but if I want to make a very unusual role I can always do that

Is judge really that complicated to do

1 Like

oh i just realized that this would make roles like tos ret/necro way easier to do as well
you can just. take their input and then transform it into the actual action
tos ret/necro have a lot of weird shit that happens mostly because of flavor or beacuse the tos devs suck or smth
but i mean like. in virtuous we already have it so that Soulcatcher is literallly just using the actual ability, and the whole ā€œcorpseā€ thing just dictates what abilities that can use n shit

ehhhh

Besides the fact that you literally didnt implement voting uhhh

this is like EXACTLY how i designed mine too actually

2 Likes

oh yea no this program doesnā€™t have voting.
it takes a slate of actions and turns them into results
voting would have to happen outside of it

1 Like

nice

More specifically itā€™s copying the witch code but on a dead player

1 Like

my god

voting is just another interface like the base abilities id say

1 Like

judge wouldnā€™t be That complicated but i would definitely reserve it for much later

I am 90% sure this is why witch got result stealing when ret changed

1 Like

is the program aimed at being fully automated eventually? or is it just for the host to figure out action results faster

1 Like

ye it would just be an input thing. probably doesnā€™t even require any of this shit, would just need to be able to update peopleā€™s deaths n shit
but ui is, as mentioned, not my strong suit

if i magically knew that i would have the time to do it n shit
yeah, it would eventually turn into something that can be automated
but at the moment itā€™s just aimed at the host figuring our action results faster
thatā€™s not actually even that useful, though. even in virtuous the hardest part is recording actions anyways, a lot of the times you can just easily skip past protections that donā€™t do anything n shit
so really itā€™s honestly more like a proof of concept that you Can do it automated, but

1 Like

ā€¦and also I think it temporarily resurrects them? For the night? Since their passive abilities start working again (see: Necromancer in tos2 using Famine or Pest)

1 Like

yea tos devs are crazy its ok

1 Like

this is how i considered it on my revision. you can alter playerstate (alive ā†’ dead, targetting a ā†’ targetting b, defense), or observe the playerstate (i.e. investigatives). its 90% just getting and setting attributes that then go into a predefined gameplay loop i.e. the night/day cycle. vote modifiers are a role attribute, the main exception is chats. chats are weird and they stick out like a sore thumb as an attribute because it is so much more complex

2 Likes