Skip to content

Migrating to MCP

Abstraction edited this page Jun 24, 2017 · 2 revisions

Preface

Relations use Stamina's own Minecraft API, thus it is not compatible with the MCP mappings. This page will explain how to migrate the system from the Minecraft API to a MCP environment.

Migrating

Migrating should be fairly trivial and straightforward. Just replace the Minecraft API class and member names, with the MCP deobfuscated class and member names, and fix the imports.

Minecraft API to MCP mappings

All class names should be correct, regardless of MCP and Minecraft version. Field and method name may differ a bit, but should be easy to resolve to the correct name. The mappings provided below are for Minecraft 1.8.

Classes are listed by their simple names, not their fully qualified class names.

Minecraft API MCP mappings
Entity Entity
Animal IAnimals
Monster IMob
Player EntityPlayer
Enderman EntityEnderman
Golem EntityGolem
Irongolem EntityIronGolem
Horse EntityHorse
Tamable EntityTameable
Wolf EntityWolf
Boat EntityBoat
Minecart EntityMinecart
ZombiePigman EntityPigZombie

Members are listed by their names, not including their signature. Methods are denoted as Class#method, and fields are denoted as Class.field.

Minecraft API MCP mappings
Enderman#isScreaming EntityEnderman#isScreaming
IronGolem#isPlayerCreate EntityIronGolem#isPlayerCreate
Entity#getRider Entity.riddenByEntity
Tamable#isTamed EntityTameable#isTamed
Tamable#getOwner IEntityOwnable#func_152113_b parsed to a UUID
Wolf#isAngry EntityWolf#isAngry
ZombiePigman#isAngry EntityPigZombie#func_175457_ck
Clone this wiki locally