[1.12] Missing methods when in Server outside of dev? (getBiomeName(),getBufferData())

[Kinniken]

Hi all,

 

I'm having at least two method calls that work fine in SP and MP when in development and in SP when running Minecraft, but fail when running a server:

 

java.lang.NoSuchMethodError: net.minecraft.world.biome.Biome.func_185359_l()Ljava/lang/String;
    at org.millenaire.common.WorldGenVillage.generateVillageAtPoint_findVillageType(WorldGenVillage.java:768)

 

(That's Biome.getBiomeName())

 

and

 

java.lang.NoSuchMethodError: net.minecraft.network.play.server.SPacketCustomPayload.func_180735_b()Lnet/minecraft/network/PacketBuffer;
    at net.minecraftforge.fml.common.network.internal.FMLProxyPacket.<init>(FMLProxyPacket.java:62)
    at org.millenaire.common.network.ServerSender.sendPacketToPlayer(ServerSender.java:378)

 

(That's CPacketCustomPayload.getBufferData())

 

I "fixed" the first one by using reflection to access biomeName directly. Not a real solution though.

 

Is this a known Forge problem? I saw references online to other people having the issue with getBiomeName, but no proper solution.

 

Thanks.

[Kinniken]

Great, a whole new constraint for developers... (well, new if you're coming from 1.7). I admit I hadn't thought something like getBiomeName() could be client-only (it obviously wasn't in 1.7).

 

And my packet system works fine, why do you want me to migrate 50+ packet types to a new system?

[Kinniken]

24 minutes ago, diesieben07 said:

This has existed since 1.3.

 

I honestly doubt it does. And yes, I would recommend that.

 

The principle exists since 1.3, but's clearly been extended. Anyway I checked, in 1.7 for biomeName there was no issue because the field was accessible.

 

And my packet system works fine in SP in 1.12 and I have a few million mod downloads for 1.7 of people who obviously managed to play with my packet system... assume all you want. Reworking it to use the new Forge system is a huge amount of work, and you have no way of knowing whether it's worth it or not.

[Kinniken]

Agreed on that last point. I had assumed it was something to do with Forge, but indeed that's on Mojang's side.

 

And well, I've found two of them so far Actually what's really annoying in fact is that in dev Forge doesn't enforce this. The rest lies with Mojang.