Include option to bring back spectator shader bug

    • Type: New Feature
    • Resolution: Won't Fix
    • Priority: Minor
    • None
    • Affects Version/s: None
    • CraftBukkit version 3553-Spigot-14a2382-ef09464 / API version 1.19-R0.1-SNAPSHOT
    • Yes

      I am trying to use this bug (https://bugs.mojang.com/browse/MC-46503) in one of my projects. More specifically, I wanted to replace these types of shaders (using a resource pack) with ones with a scope texture for one of my minigames. If I kill the player then make them respawn back exactly where they were, they can use these "scopes" while being in survival mode. I thought I could do this, until I realized it was fixed (even in Bukkit). I would like there to be some way to bring back this bug (eg. in the configuration).

          [SPIGOT-7116] Include option to bring back spectator shader bug

          Phoenix616 added a comment -

          I see, well I doubt it was changed intentionally. Most likely it's just due to some events handling stuff changing that behaviour. I suggest just sending the packets manually that put the player into that state (and/or analysing the client code to find the cause for that bug and how to trigger it with packets) but how to do that goes a bit beyond this tracker as it's very unlikely that official API support for that would ever be added.

          Phoenix616 added a comment - I see, well I doubt it was changed intentionally. Most likely it's just due to some events handling stuff changing that behaviour. I suggest just sending the packets manually that put the player into that state (and/or analysing the client code to find the cause for that bug and how to trigger it with packets) but how to do that goes a bit beyond this tracker as it's very unlikely that official API support for that would ever be added.

          Anston Sorensen added a comment - - edited

          It isn't fixed in 1.19 by Mojang. So, it's definitely not the client. Spigot/Bukkit must've fixed it way back when. How could I achieve this by messing with the code?

          Anston Sorensen added a comment - - edited It isn't fixed in 1.19 by Mojang. So, it's definitely not the client. Spigot/Bukkit must've fixed it way back when. How could I achieve this by messing with the code?

          Phoenix616 added a comment -

          This is also most likely a change in the client itself, not in the server so there wouldn't be much for Spigot to be able to do here. I suggest taking a look at the client code which made this work and compare it to the code used in 1.19 and maybe you are even able to figure out a way to still achieve that effect by doing that.

          Phoenix616 added a comment - This is also most likely a change in the client itself, not in the server so there wouldn't be much for Spigot to be able to do here. I suggest taking a look at the client code which made this work and compare it to the code used in 1.19 and maybe you are even able to figure out a way to still achieve that effect by doing that.

          Black Hole added a comment -

          Spigot never introduced options to enable fixed bugs.

          Black Hole added a comment - Spigot never introduced options to enable fixed bugs.

            Assignee:
            Unassigned
            Reporter:
            Anston Sorensen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: