Arelith

Description of Bug Experienced:
Project image cooldown not working as advertised.

Steps to reproduce the Bug:
Use -project_image [name] in the chat box to someone on another server.
Wait out the cooldown, after being told it's available again.
Send -project_image as a Tell to someone on the same server.

Expected Result:
The recipient receives the message.

Actual Result:
The recipient did not receive the message, and another cooldown was started despite the failure.

Screenshot(s)


_yes was the message sent. The system seemed to recognise a message was sent, but a Tell with the intended recipient confirmed they did NOT receive it.

Hi!

Thanks for reporting this bug. I wonder if this is a one time glitch related to the messenger mechanics and not the actual project image mechanics, but regardless, adding it to my list to investigate.

I may need some help with testing this if you guys are available.

Not one time, I've run into this myself and not gotten around to bug reporting.

Once you've dropped the code fixes let us know, I'll spend some time testing a few scenarios that I've noted odd behavior on, for the others testing, these are the various behaviours I've seen:
- Messaging after ESF: Clone (currently working)
- Sending 2nd Messaging timer refreshed (currently working)
- Sending 2nd Messaging after Server transition and timer refreshed (returns resting error)
- Sending 2nd Messaging after using a fixed Portal and timer refreshed (returns resting error)
- Sending 2nd Messaging after using -teleport command and timer refreshed (returns resting error)