Jump to content

[1.10.2] Getting a long from player's nbt and displaying in a gui?


dude22072
 Share

Recommended Posts

Currently using the following code:

        @Override
public void drawForeground(int mouseX, int mouseY) {
	long rupees = Minecraft.getMinecraft().thePlayer.getEntityData().getLong("rupeeCount");
	System.out.println(rupees);
	Minecraft.getMinecraft().fontRendererObj.drawString(Long.toString(rupees), 45, 92, 4210752);
}

 

It always displays as 0. I know I am using the correct key for the long because I have added a chat command that checks it and it is returning the proper value.

Legend of Zelda Mod[updated September 20th to 3.1.1]

Extra Achievements(Minecraft 1.8!)[updated April 3rd to 2.3.0]

Fancy Cheeses[updated May 8th to 0.5.0]

Link to comment
Share on other sites

The tag returned by

Entity#getEntityData

isn't automatically synced to the client, you need to do this yourself.

 

That said, you shouldn't be using

Entity#getEntityData

anyway. Use the Capability system to store data on players (among other things).

 

For examples, you can look at the capabilities provided by Forge (look for usages of

CapabilityManager#register

), the capability test mod or my own mod's capabilities (API, implementation).

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.