Jump to content

Erasmus_Crowley

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    I am new!

Erasmus_Crowley's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. I just had to use the new FIRST_PERSON_HOLDING instead of FIRST_PERSON_MAP and it worked fine. Problem solved. Thanks for all the help!
  2. Thanks for respond TGG, good questions. My block has absolutely nothing to do with any of the map classes. I'm not subclassing anything out of the ordinary, just BlockContainer, ModelBase, TileEntity and TileEntitySpecialRenderer. My item renderer implements IItemRenderer without extending anything at all and it's a really simple class. I checked to see if it looks like a map in all views and it does not. It only looks like a map in first-person view when it's being held in your hands. The view where you would normally read a map. It looks fine in third person, on the ground, in the inventory, etc. I saw this in the recent change log for forge: ml Added a RenderType that allows Map-style rendering w/o inheriting from ItemMap. Unfortunately, I just started working with forge a week ago and I don't know my way around the library (or even eclipse) enough to figure out with any speed if that is the cause of my current dilemma. I'll be trying your suggested method for a while. Let me know if you think of anything. Thanks again, I appreciate it.
  3. I installed the mod I'm working on in a client using forge build 9.10.1.865. The custom block I was working on is showing up as a map in the player's hands. It still renders perfectly in the world, and in a previous version of forge, it was working fine? Is this a bug or am I not doing something right? For the most part, I followed minalien's tutorial @ http://minalien.com/tutorial-advancedmodelloader/ when I set up the block, so aside from having a TileEntity attached, you can assume that the overrides are the same.
×
×
  • Create New...

Important Information

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