#(cerusabi) `glow` not resetting for self

20 messages · Page 1 of 1 (latest)

lost quartz
#
  • Glow reset works succesfully server-side, other players will not see you as glowing anymore (as long as you correctly set the for: property
  • Something about setting someone's gamemode to spectator is enough for the client to do an update and fix whether you are glowing or not, so is there a workaround for this command that I can do?

steps to reproduce

  • glow <player> for:<player>
  • press F5, you should be glowing now
  • glow <player> reset for:<player>
    • you still look like you are glowing, but you are not. If you set your gamemode to spectator, you won't be glowing anymore.
    • you can contrast this to skipping this reset command, and then setting your gamemode to spectator.
    • if you include other players in the for: selector, they will not see you glow when you use this command
stiff lindenBOT
#

(cerusabi) Visual bug with 'glow <[entity]> reset for:<player>'

#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

lost quartz
#

still looking for a clean workaround for this

lost quartz
#

(cerusabi) Workaround for the visual bug with 'glow <[entity]> reset for:<player>'

#

bump ^

trim crownBOT
#
Changed to Bug

Thread is now a Bug thread. This indicates a core code bug that a developer must resolved, not an error message or other support topic. Please do not misuse the Bug label. Use </helpthread:1028674284870180883> to switch the thread back to a normal help thread if you are not 100% confident it is a code bug.

lapis glacier
#

Can replicate, and I believe I found the cause

#

(cerusabi) glow not resetting for self

lapis glacier
#

Should be fixed ref #commit-log message

trim crownBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@lost quartz

lost quartz
#

thanks so much!!