You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And this is because, the method is defined in the interface net/minecraft/world/IEntityReader, but on changing this to IEntityReader, as it's suggesting (somewhat), we'll have some nice AP obf mapping:
HOWEVER, mixin application will fail in production, because the matching bytecode (remapped to srg named, but not decompiled and recompiled) looks like this:
Note the last invokevirtual net/minecraft/world/World.func_217358_a(DDDD)Z and it is not IEntityReader.func_217358_a(DDDD)Z, even though in theory this should be fine (relatively speaking, its an invokeinterface, but there's likely some proguard shenanigans at play here with relation to calling default implemented methods).
The text was updated successfully, but these errors were encountered:
gabizou
added a commit
to SpongePowered/Sponge
that referenced
this issue
Sep 5, 2020
I couldn't figure out why 9438945 didn't auto-close this and then I realised I put the hash in front of Fixed instead of in front of 438. I'm an idiot. This is fixed.
So, for the provided method from AbstractSpawner:
with the provided Mixin:
We get the following error from the AP:
Which of course provides the following refmap:
And this is because, the method is defined in the interface
net/minecraft/world/IEntityReader
, but on changing this toIEntityReader
, as it's suggesting (somewhat), we'll have some nice AP obf mapping:HOWEVER, mixin application will fail in production, because the matching bytecode (remapped to srg named, but not decompiled and recompiled) looks like this:
Note the last
invokevirtual net/minecraft/world/World.func_217358_a(DDDD)Z
and it is notIEntityReader.func_217358_a(DDDD)Z
, even though in theory this should be fine (relatively speaking, its an invokeinterface, but there's likely some proguard shenanigans at play here with relation to calling default implemented methods).The text was updated successfully, but these errors were encountered: