XCompWiz

Apologies for the necro. I make this post so anyone looking for the info isn't misled. It was brought to my attention and isn't a good thing to let lie, lest folks mess it up. No. 0.o That function is for data sending NOT rendering. You can already do this using a custom item renderer (IItemRenderer) to control how the entity form of the item is rendered or by using the RenderItemInFrameEvent.

Very simple. The line this.placeBlockLine(aint, aint2, (byte)HeroCraftMain.twoRiversLog.blockID); Is casting the blockID to a byte. Remove the cast and it'll work fine. The problem you are seeing is that that the blockID is greater than the maximum value of byte, and the value is being truncated. EDIT: I recommend turning on warnings on unnecessary casts to help prevent similar issues in the future. This can be done through the Eclipse settings for warnings and errors.

Sounds good. Thanks.

I assume Lex missed my synopsis of the problem in reading Keybounce's post. What do you think the best way to address this issue is, Lex? Should Forge make bed spawn tracking dimension aware?

The only actual issue (and what Keybounce is trying to explain very badly) for Mystcraft is that each player stores only one bed spawn-point, not a bed spawn-point per dimension. This means that if you set your bed spawn in one dimension it clears where you slept in other dimensions. This also means that the respawn code attempts to use this single bed spawn in all dimensions, checking for beds or force respawning at those coordinates in whatever dimension the player is respawning in. Thanks for pointing out that the issue tracker requires login to view. I'll try to address that problem. I'm not sure what causes that.