TimedAddItem and TimedChatDialogue are both implemented somewhat naively.

For one, nothing is done to make sure the threads interact in a safe manner.

Another is that there is no response mechanism - the triggering events, usually Quest related, simply schedule the timed event and update their status; if a player disconnects or the game crashes during one of these timed events, the quest status has already updated but the player did not receive their quest item or information.

There would have to be some way of ensuring the Quest couldn't continually trigger the timed event prior to receiving a response, but also allowing it to re-trigger if it doesn't receive a response.