cherdt / wumpus-twitter Goto Github PK

I mean, we have to have a little oddness, don't we? Random events are harmless and do not affect the game, but merely add color. E.g. "You walked right into a spider web. Yuck."

According to the API docs at https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/get-sent-message

There are limits to the number of Tweets which can be accessed through the API. If the limit of Tweets has occured [sic] since the since_id, the since_id will be forced to the oldest ID available.

That just doesn't make sense. Well, Twitter is deprecating that endpoint soon anyway and replacing it with one that makes even less sense.

Currently get_dms_since limits the number of returned DMs to 1. Obviously that would not work if multiple players were playing simultaneously. Can be up to 200 with this version (now deprecated) of the Twitter API

• wumpus should not move every time it is disturbed
• wumpus should not move onto the hunter

It's fun to have multiple tweet bubbles in the DMs, but each one is a chance for the twitter API to decided we've exceeded some arbitrary limit. Better to pack all the messages into one DM and use newlines judiciously.

if we're processing multiple DMs from different users, we don't want to exit the program until all are processed.

Since users can't DM wumpus_bot until wumpus_bot follows them, wumpus_bot should automatically follow any user that follows it.

Instead of "Think you can shoot through rock walls?" maybe "You refrain from such foolishness."