When players receive drops, collection logs, etc, we oftentimes send a number of messages in quick succession, and our backend reads each one individually with no context to the last one.
It would be ideal for us to have a way of knowing which "event" each drop a player sends came from. This would help us be able to more accurately track how many kc a player has tracked at specific bosses within the system.
Could use a simple integer on the client that signifies how many events have been processed, incrementing it each time a new one occurs.
This could also help us group messages together; for example if someone receives a drop that is also a collection log, we could send a message containing both sets of information instead of sending two; or note that its a collection log in the drop embed
It would be ideal for us to have a way of knowing which "event" each drop a player sends came from. This would help us be able to more accurately track how many kc a player has tracked at specific bosses within the system.
Could use a simple integer on the client that signifies how many events have been processed, incrementing it each time a new one occurs.
This could also help us group messages together; for example if someone receives a drop that is also a collection log, we could send a message containing both sets of information instead of sending two; or note that its a collection log in the drop embed