XenotropicDev
Should followup rolls remove themselves from the drop down list?
I'm not sure if this is something that should be done automatically or not. It might be possible to include some kind of handling for different scenarios in the select menu's value (first roll, reroll, delete after roll).
Other options include
- leaving the item for multiple values
- replacing the existing value to act as a reroll (this might want some kind of emoji or label change)
could handle rerolling individual fields by having a dropdown menu for that (probably hidden behind a "..." button). there's a maximum of 25 fields in an embed and 25 options in a select menu. ditto deleting fields.
otherwise, i'm strongly in favour of removing rolls that have reached maximum recommended rolls from the list for entities (or at least from the primary list - they could be accessible through other means), at least as far as oracles are concerned.
imo, recommended number of rolls per table is fairly important information (it's "top of the table, next to the title" stuff, not "footnote at the bottom" stuff)... so i reckon it's something that needs to be conveyed regardless. we could invent some other way to convey it (and force users to do the extra work of checking the limit and then counting existing results if they want to use the table as recommended), or we could convey it by removing it from the list of recommendations (e.g. the most obvious/readily available dropdown - implicitly a list of the recommended options) when it's no longer recommended.
on one of my branches i handle this by including the number of remaining rolls for a given oracle in the dropdown value string, decrementing it as part of the component interaction that makes the new roll, and removing it if it hits 0 (the same function can be used in building the embed/menu's initial output, too). -1 is used as a magic number to indicate "roll this as many times as you want", but there's probably other ways of handling that too.