Open ghost opened 5 months ago
No, we need control over the listener priorities and to have our own encoder/decoder, you will get conflicts with other plugins otherwise
No, we need control over the listener priorities and to have our own encoder/decoder, you will get conflicts with other plugins otherwise
I don't understand, you shade packet events directly from the github repo, all you do is relocate it?
Shading packetevents gives Grim its own encoder/decoder, this also means we don't have any plugins interfering in packet listener priorities, and any plugins that mess with packets using packetevents (such as spawning entities) will go through Grim.
Shading packetevents gives Grim its own encoder/decoder, this also means we don't have any plugins interfering in packet listener priorities, and any plugins that mess with packets using packetevents (such as spawning entities) will go through Grim.
Seems like a non issue, why would plugin be messing with spawning entity packets? Grim doesnt modify any packets right? just reading? For packets we are receiving grim should listen at lowest priority, for packets being sent listen at highest, simple no?
No, I suggest you look at all the different priorities Grim is using. I have packet-level NPC plugins, if Grim was not shaded then my packets might not be read by Grim, and other plugins may listen at different packet priorities and modify packets.
@IssueDescription Retrooper is fine with people shading packetevents & he isn't getting ad revenue anyways.
Modrinth does offer a little ad-revenue. At the end of the day, not shading benefits the users so it has little to do with me.
Feature description
Pros of unshaded packetevents:
Cons: