Zell Wolf Wolfbot Testing Discussion

shortkut

idea man
Cuterator
10K Post Club
Moderator
Executive
GW Elder
Wolf Players
Messages
15,569
High School Water GIF by Bottoms Movie
 
Messages
5,163
@Zell 17
You've turned WolfBot into a time traveler. It just watched a posted of mine from VTS Mafia...
...from September... 2023.

Your bot is stalking me.

View attachment 26108

Ooh I can explain this one. So I noticed when Vash made his shot, that the bot marked his post as read and then it took like 45 seconds or so before it announced that the shot was successful. Most of that delay was because there is no way in the API that I can discern for the bot to edit the poll, so it has to physically fire up Chrome, log in, navigate to the thread, and click the buttons to make the edit and that takes some time.

So I decided to just move the section of code that marks the posts as "seen" to be the last thing the bot does. So you know for sure that if a post is seen, whatever actions it was supposed to take have already been considered.

The problem was that the variable I used to store the post IDs got overwritten in the meantime by the bot checking the PMs for actions. PMs have a separate "message ID" from the post IDs.

So these old posts marked as seen have the same ID as some current PMs flying around.
 

Jon

Diplomatic Immunity
T-Bone
10K Post Club
Moderator
Executive
GW Elder
Wolf Players
Messages
11,328
Ooh I can explain this one. So I noticed when Vash made his shot, that the bot marked his post as read and then it took like 45 seconds or so before it announced that the shot was successful. Most of that delay was because there is no way in the API that I can discern for the bot to edit the poll, so it has to physically fire up Chrome, log in, navigate to the thread, and click the buttons to make the edit and that takes some time.

So I decided to just move the section of code that marks the posts as "seen" to be the last thing the bot does. So you know for sure that if a post is seen, whatever actions it was supposed to take have already been considered.

The problem was that the variable I used to store the post IDs got overwritten in the meantime by the bot checking the PMs for actions. PMs have a separate "message ID" from the post IDs.

So these old posts marked as seen have the same ID as some current PMs flying around.
Imagine if you used your powers for good?
 

TD

ES COO Shitposting Dept. of GWF
10K Post Club
Executive
GW Elder
Messages
16,576
So Jawneh was lynched (you monsters), but it looks like WolfBot immediately removed him from the poll so you can't even look at who voted for him.

Is this by design or error? Seeing who voted to lynch someone is helpful.
 
So Jawneh was lynched (you monsters), but it looks like WolfBot immediately removed him from the poll so you can't even look at who voted for him.

Is this by design or error? Seeing who voted to lynch someone is helpful.
Both. You shouldn't be able to vote for dead people (splash victims, for example), but lynch victims should remain
 
  • Like
Reactions: TD
Messages
5,163
So Jawneh was lynched (you monsters), but it looks like WolfBot immediately removed him from the poll so you can't even look at who voted for him.

Is this by design or error? Seeing who voted to lynch someone is helpful.
Yeah I noticed this. The bot is programmed to take out anyone who is killed during the day from the poll. But, surprise! Jawneh met both requirements, but shouldn’t have been.
 
  • Cheers!
Reactions: TD

shortkut

idea man
Cuterator
10K Post Club
Moderator
Executive
GW Elder
Wolf Players
Messages
15,569
So Jawneh was lynched (you monsters), but it looks like WolfBot immediately removed him from the poll so you can't even look at who voted for him.

Is this by design or error? Seeing who voted to lynch someone is helpful.
I noticed it too, but wanted to see if I could skip after the day closed rather than point this out. It’s called prioritization
 
  • Haha
Reactions: TD
Back
Top Bottom