Ticket UUID: | 046737cd29cdce1da451e38d3dfdcf58b87f077e | |||
Title: | Multiple problems when an emote is overwritten with another one of the same name | |||
Status: | Open | Type: | Bug | |
Severity: | Minor | Priority: | Low | |
Subsystem: | Discord | Resolution: | Open | |
Last Modified: | 2018-09-24 20:19:06 | |||
Version Found In: | 0.3.4 | |||
tmad40blue — 2018-09-24 20:18:23Let's use an example emote :foo: If a server owner uploads another emote that is also named :foo:, Ripcord will show both the old and the new versions of the emote when the auto-complete UI appears. Trying to send the emote code will result in no emote being rendered, but instead the plain-text :foo: will be printed in the message. | ||||
tmad40blue — 2018-09-24 20:19:06Update... restarting Ripcord fixed this issue. Perhaps the old emote was being stored in some kind of cache? |