mkmccarty / tokentimeboostbot Goto Github PK

From SpaceCowbot5150

•   If I can make a suggestion for something to be added to boost bout it would be a timer on active boosts. Would help show when to check in and add gusset.

  

Gusset Timer

•   For a timer: 10B / (7440 * 4 * 3 * artifact set * 1000 * boost beacons) will spit out the number of minutes to 10B chickens gained

The Chalice and monocle T4Es + 8 stones is x2.3
  

Those blue buttons are for the current booster. It makes sense to open them up to everyone to use. It was originally restricted to avoid an imagined abuse that probably isn't a thing.

The current /change commands can be confusing. Break this into individual commands that focus on a single task

Add a way for a farmer to indicate the number of boost tokens they want.

Options:

1. Through a slash command
   /tokencount 6

2. When user reacts to signup reaction list, send an interaction message to that user asking them to specify a count.

3. Allow for a number reaction to the boost list to specify the tokens needed

For some of the boost order modes they start as Fair/Random then after 20 minutes. Provide some indication of how someone is added. Maybe as a timestamp display.

Add a slash command to allow for the renaming of a contract

Perhaps:
/change coop-name: name
/change coop-id: name

Add /speedrun slash command to set parameters on an existing contract.

Option for Coordinator listed as first or last and everyone else fair ordering.

Option on where to direct tokens...

• During CRT: Who's getting tokens (aka Kicker)
• During Boost: Either to Boost List (normal) or to a token sink
• After Completion: Who's the token sink

Perhaps a couple new states for the bot. Signup -> CRT -> Boost List -> Post Boost

When a contract has boosted players, if one those players leaves via /prune or the Leave button then there is a crash when trying to find the next booster.

Added a guest booster to a contract using the "Last" option but they were added to position 7 out of 12 (presumably randomly)

Good to know who created the contract

A user attempted to press the last reaction and it didn't function.

This keeps the contract moving with less interactions for guest farmers

Through a boost list reaction, allow a reaction to increment or decrement if a token was sent to a farmer.

Update the boost list to give a tally of the received tokens on that farmer.

Perhaps something like this which would

1 - Farmer (x/5)

or if the farmer hasn't specified a number of tokens needed

1 - Farmer (x)

The Makefile doesn't build the correct target on RP4, it builds as 64-bit but the RP4 needs a 32-bit binary.

Allow for a guild to specific OpenAI or Google Gemini tokens to be stored and used within a server.

This should just be an edit instead of a new notification.

There is a request to identify a post boost token sink for a contract.

Add a command to change the coop creator

Sometimes these need to be evaluated or altered.

Provide a slash command to permit reordering of the contract in a single command.

Make the /calc-token-value command use an embed like the /token command

To avoid constant disruption after 20 minutes, anyone who joins will be added to the end of the list instead of inserted randomly.

For a large contract nobody wants to see a full 50 line list on every booster change.

Draw the list to show the previous booster (or two), the current booster and the next 7 boosters.

Those above and below the list can be displayed in a summary line.

opt-in DM when enough tokens to boost
opt-in DM when someone wants chickens

Add a new boost state for when boosting is complete and there are still open positions.
When in this boost state, add an additional reaction to allow the contract owner (maybe voters too) to mark this as done.

Avoid an accidental click

Add a /change single-booster: @mention:#
or something like that where a mention or booster/farmer name and some trailing number will move them to that spot

Make /join command response be ephemeral.

Give users an easy way to mark they need to go last

The bot would need to be told the start & end time of the contract to get the numbers close. When the sending/receiving of tokens happens then record the timestamps of sent & received tokens into arrays and do the math on those deltas.

Track more of the message id's used by the bot to help find the proper contract.

Add a slash command which would allow the @ROLE to be updated.

Perhaps:
/change role:@ROLE

Some /change commands don't ack the message back to the client and leave an empty response to the user

If someone uses the send to bottom reaction, do they always stay at the bottom, what if someone else wants to be the bottom?

Convert the Boost List to use an embedded message. Due to the many ways this message is displayed the work might be extensive.

https://cdn.discordapp.com/attachments/1189256007906492516/1227689912971821148/image.png?ex=66295254&is=6616dd54&hm=a9a209d86968a2c9088bc5138307388fd0f5dd16bd7e68ca24015d96aab73125&

Add a slash command /unboost to mark that user index as unboosted. Optional parameter for tag maybe.

There should only be a single tokentime status within the contract.