Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Smart Moving (backpack rendering) #59

Open
copygirl opened this issue Jun 19, 2013 · 2 comments
Open

Support Smart Moving (backpack rendering) #59

copygirl opened this issue Jun 19, 2013 · 2 comments

Comments

@copygirl
Copy link
Owner

No description provided.

@copygirl
Copy link
Owner Author

copygirl commented Jan 8, 2014

Moved back because I'm not sure if it's worth the effort of figuring out how the new render API works. Aaand ... for some reason I'm supposed to decompile it? What kind of API is that?

@mdfiot
Copy link

mdfiot commented Apr 2, 2014

Like this no?

This is all taken from their website [http://www.minecraftforum.net/topic/738498-172api-player-api/]. I thought maybe you may have miss interpreted it because it's mixed with MCP.

"How do I decompile this with Minecraft Forge?
Minecraft 1.6.4 and later:

By developing with Player API core instead of Player API forge you don't need to deobfuscate at all.
Put the PlayerAPI.jar in your development environment's mods folder.
Add /PlayerAPI.jar to the classpath of your mod project.
Done.
...
Outsource your mod specific code from EntityPlayerSP.java/EntityPlayerMP.java into a new mod specific class you create a single instance for each instance of the EntityPlayer class so that only the mod class field, some hook methods and some field accessors remain in EntityPlayerSP.java/EntityPlayerMP.java.

-Let your specific mod class extend the PlayerBase class
-Make sure your mod class is registered at the PlayerAPI class before the first player instance is created. (a ModLoader mod would be a good choice here)
-Adapt all your hook listeners in your mod class to overwrite their corresponding PlayerBase methods.
-Adapt all your field accessor references with references to PlayerAPI field accessors."

Sorry if I'm completly wrong about all this (I'm new). I hope to see this supported.

Thank you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants