Major Update to Slays + other changes

[SGA-A]

Changelog is outdated, see the commits below to get an idea.

This PR is still a work in progress. I will update the changelog before the PR is ready for review.

[SGA-A]

A problem we are facing with tracking servant's levels has been encountered. We always use the on_app_command_completion to track misc user data such as commands ran. One of those also happens to include leveling up. A webhook event is then dispatched to notify the user in the invoker channel.

For this case, we need to know which servant leveled up, and (maybe) how they leveled up. This is almost impossible to do without attaching it to the end of the command callback, since that is the only place these details can be retrieved.

As a workaround, we're going to use a dictionary within the environment to store exactly what slave managed to level up, essentially which one reached the XP limit for the current level they're on. We then fetch it by the key which will be the user ID that we can fetch from the interaction parameter within the on_app_command_completion event using interaction.user.id. After, all that's left is to make the sql query and update the associated row field values.

[SGA-A]

Here is the to do list, just so that we don't miss out anything:

• [x] Wash your servant, and hence add support for dispatching servents on work.
  • When dispatching servants to work, reduce the energy bar once completed by X which scales upon the duration of the service.
  • Do not allow players to dispatch servants if they are tired or fatigued.
  • Find a way to increase the energy bar as well with time, if it's not full already.
• [x] Sending hugs or other interactions should actually increase the love bar and not just send a text response.
  • Add one more possible interaction, and insert it into the appropriate row.
• [x] Make it possible for servants to level up (mentioned this in the above comment).
• [ ] Send warnings to players when any of the bars is less than 30% (not including experience).
• [x] Noted issue: When someone else views your servant's, they cannot use the dropdown menu and pick any other selectable option. This is because of the interaction check we use that checks if the servants being viewed is owned by the invoker, if not do not allow them to interact with any of the menus, including the dropdown.
  • We will most likely alter the way this feature works, by disabling items that the user is not allowed to modify (if they don't own those servants), but keep the dropdown enabled within the timeout of 60s. This means we can remove the interaction check, and anyone can interact with the enabled dropdown, not the disabled buttons which are manageable by the owner. Though an obvious problem is that the owner themselves cannot use those buttons, it is disabled on their end too.
  • Another alternative is to have a single customize button on the menu, and we still display the select dropdown. Again, the interaction_check function is not overrided and there is only a single active button available for use, this will be named 'Manage'. If the interaction user is not the owner of the servants shown and this button is clicked, just return the interaction stating you do not own these servants. This single button will add the manage buttons back in, and respond by editing the original message with the new view. We will need a new button as well when the 'Manage' button is clicked, something like 'Go back'. This would be difficult to implement but it definitely would be a good solution if properly designed.
• [ ] Good to have: Interact with other player's servants, adding interesting features like stealing another member's servant (not indicative of what will happen). This will make it more interesting rather than using servants as a money/loot generator and have no meaning beyond that.

[SGA-A]

It is taking a while to cover all the bullet points, and any that are remaining are far too 'abstract' to develop entirely off of scratch. They need to be dealt with by decomposing the actual problem. There are a lot of factors to consider so we'll need to organize the ideas we have, perhaps into a mindmap that visualises all the things you can do with servants.

We want to push the changes ASAP but we also don't want to produce it rushed and as a result redesign it later on again in the future. Therefore, it is possible we will be postponing the release date, in the case it does occur, we will announce this on our status page for the project, which you can find here.

In the meantime, any other changes/bugfixes that are not relevant to the servant overhaul are also included, hence the title, to prevent merge conflicts to the base branch.

[SGA-A]

I suggest reading https://github.com/SGA-A/c2c/discussions/55#discussioncomment-8363343 for why this change is happening.

[SGA-A]

Seems like we're nearing the end of the changes we've wanted to make. We've made some changes along the way to how we want this to work out, so here are the details:

• Some parts of the system are somewhat buggy.
  • What we mean is that increasing the attribute of one item increases the attribute of another. This is not intentional but we're keeping it this way for the time being.
  • Many of the functionality we've wanted to add has not been added. These will be added at a later date, not now. It's more complicated than we thought it would be so we're implementing some functionality at a later date.
• You will not get a message if you're servant is tired, hungry, unhappy or anything else in terms of a negative context.
• Your servant will not abandon you if you do not care for them.

These changes may not be permanent if we reconsider things, but that's unlikely to happen so bare that in mind.

And now for the things we have planned to work on over the next few days/week:

• Dispatching servants to do chores/tasks/work:
  • You will be able to pick a servant you want to dispatch to work (one that hasn't already been dispatched)
  • You will be able to select the difficulty of the task but certain skill levels need to be attained for the individual servant you wish to dispatch.
  • The time spent will (try to) vary and scale based off how difficult the task itself is.
  • You should be able to see how many tasks your servant has completed.
  • You should be able to see your favourite tasks your servant has completed.
  • You cannot select more than 1 task for a single servant to complete.
  • Your servant must meet an energy requirement as well before being able to perform a task. For example, tasks that are of high difficulty will required at least >75% energy available, as this is the equivalent consumed upon task completion.
  • You will be able to interact with your servants while they are working, even though that does not sound right.
  • You will need to claim the rewards your servant gives you in some way as well. Not sure how this will be done.
  • Servants also cannot work if they are hungry or tired. (Possible)

We are planning on adding more features for this aspect of the economy, but that will be happening later down road. We'll open a new PR when the time comes.

[serephenna]

More commands are to come in this subsection of the bot, but for the time being, it remains as it is.