FML, I based my parts of my small framework on a wrong assumption and now I have to rethink about 30% of it

What mind of assumptions?

@alexbrooklyn I've tried to think over it, but it's more complicated than I thought.

I'm trying to make handling discord interactions easier, but it's such a stupid concept to work with. Handling the initial interaction is not hard and if you just create a message reply it's pretty easy. If you however want to create a message with components (e.g. Buttons), you will get subsequent interactions from these components. You can think of them as events like "button pressed and such. So far the only common ID I've found between these component interactions I've found is the message id.

To put it simply, I've tried to create an object from that interaction and message, and then have the object update the message, but forgot that I don't have a message to update yet, so I want to find a proper abstraction to generate the initial message content, create it and then update the state with the message ID in order to properly route the following interactions to the right state.

It might sound easy like this, doing so would compromise a lot on the simplicity I had in mind, so I'm trying to figure out the proper protocol/sequence of events to keep the interface implementation to a minimum.

Writing this long text kinda helps visualizing it

@Awlex ah I kinda feel your pain, I wanted to make a midi bot but the whole voice chat stuff made me give up