Blocking not visible from 1.8 with ProtocolSupport
arceuss opened this issue · 12 comments
@pabloalba16 That looks doable, it seems that plugin modifies some packets for certain clients so that 1.8 clients see people blocking. It should be possible to integrate that into OCM.
You can bring up 1.8 sword blocking on protocolsupport with this plugin: https://www.spigotmc.org/resources/protocolsupportstuff.44527/
@pabloalba16 That looks doable, it seems that plugin modifies some packets for certain clients so that 1.8 clients see people blocking. It should be possible to integrate that into OCM.
I am experiencing a similar issue, players on 1.8 clients cant see people drawing back their bows to shoot. This also occasionally causes the player to become invisible. Would it be possible to integrate a similar packet fix for bows as you are planning to do for sword blocking here? Thanks!
@NotAlexNoyle That doesn't sound like OCM is the cause of that problem, so it would not be possible to fix that from this plugin.
@NotAlexNoyle Are you using ProtocolSupport or ViaRewind to bring back 1.8 support?
@NotAlexNoyle Are you using ProtocolSupport or ViaRewind to bring back 1.8 support?
ViaRewind. Would I be correct in assuming that this issue is applicable for ViaRewindLegacySupport?
ViaRewindLegacySupport does not claim to fix it in their spigot description. If players become invisible, that's ViaRewind issue. It does not seem like they have implemented the draw back for bows. ProtocolSupport has it but it is discontinued and incompatible with some anticheats so it is not viable
This is actually not OCM's responsibility. All OCM does is give the player a shield. If ViaRewing/ViaBackwards etc. are able to show a 1.8 client who is sword-blocking as holding a shield, then they should also be able to show a 1.9+ client who is shield-blocking as sword-blocking. If that is not currently the case, that is a feature request for those plugins.
Sorry but I haven't a clue what sort of wacky stuff ProtocolSupport, ViaVersion, ViaBackwards etc. do to work. They often conflict with OCM because it was never intended to work with 1.8 clients. Maybe at some point in the future I will have the time to investigate this.
