VOTE: zug
Zugzwang (2): Ash, Atlas
ElizaThePsycho (1): Zugzwang
Not Voting (4): May, L.una, ElizaThePsycho, Bionic
VOTE: atlas
Zugzwang (2): Ash, Atlas
ElizaThePsycho (1): Zugzwang
Not Voting (4): May, L.una, ElizaThePsycho, Bionic
Zugzwang (2): Ash, Atlas
ElizaThePsycho (1): Zugzwang
Not Voting (4): May, L.una, ElizaThePsycho, Bionic
Zugzwang (2): Ash, Atlas
ElizaThePsycho (1): Zugzwang
Not Voting (4): May, L.una, ElizaThePsycho, Bionic
Zugzwang (2): Ash, Atlas
ElizaThePsycho (1): Zugzwang
Not Voting (4): May, L.una, ElizaThePsycho, Bionic
thanks
yeah it has that bug
if you vote after it reads the vote, but before it posts the votecount, it’ll overwrite your vote
problem is with that delay
it reads all the post and then delays itself
it doesnt delay itself then read the posts
this tends to be a problem with these bots (see: fam4 vc bot had the same issue)
I can fix it but its kinda annoying
so say if we’re doing a mash and its eod you might get upwards of 20s of old vcs youre going off of
probably wont matter in another situation but it theoretically could aswell
one way to fix:
post “Loading votecount”
grab votecount as of that post
edit votecount in
another way to fix is:
record postcount that VC is read at
post votecount
edit votecount as needed if new posts were made inbetween
(this is probably the better solution)
in FAM my vote did actually get erased at one eod, and it did change the EOD votecount (until hosts fixed it manually)
so like yeah its ~realistically a thing sometimes
it’s the third time i failed to modkill i will modcry
the bots off mate
well stop getting it online when im not >:(