[1.3.2][SOLVED] Questions beyond tutorials

[Xemrox]

hi there finally i decided to create a forge account and ask a few questions.

first off i am not new to modding games or programming at all, i am just new to minecraft/forge modding.

 

the last 3 days i followed nearly all tutorials from the wiki and the subforums on how to do certain things with the new forge,

but now i am at a point where i do not really understand how forge handles some things.

 

i tried to create a block with subblocks consisting of "block" and "itemblock" with metadata. (working)

after that i wanted to add the ability to rotate the textures on these blocks via a tool or as a start point my hand.

 

therefore i added tileentities (of course with all the register functions etc...) everything goes the right way except the sync part.

 

the first thing i noticed is that the tileentities get created on the client as well as on the server, so far no problem,

but they do not share their nbtflags.

 

so what happens:

[*]i connect to my local server and activate my rotate function

[*]no visual effect, but server recognized click and made his action, as well as client

[*]after a few seconds the block rotates at the client side

[*]reentering the server resets all rotated blocks to default

now to the question part... (sorry for the long text hopefully you can now understand my questions)

• is it necessary to sync all tileentities by hand?
  
• if so is that the ominous packethandler stuff?
  
• do i need to add this to all entity related actions?
  
• how do i send this custom packet to the right target? (creating the packets and registering the packetmanager is ok got that allready)
         
• far off but another question: is there a "new" way of how to add sounds to forge? (cant get it to work with old tut)
  

 

thx for all answered questions

[atrain99]

You do have to sync them.

[Xemrox]

thx for that info.

but could someone tell me the use for a tileentity now? (except nbtflags, wich dont seem to work...)

why shouldnt i reimplement the block with some extra network stuff?

[DarkGuardsman]

thx for that info.

but could someone tell me the use for a tileentity now? (except nbtflags, wich dont seem to work...)

why shouldnt i reimplement the block with some extra network stuff?

A block is simple the physical existence of the block with code to change how its is placed,removed,destroyed, walked, on etc. The block also shares the same vars with all blocks. Meaning a change in one block is a change in all blocks. Also a block is limited to storing so much data usually in metadata. It normally can't save any data past the metadata.

 

A TileEntity is the spirit of a single block. You can use it for storing data, doing per tick updates, and sending/receiving packet data. You can also use it for doing special renders,having something other than a block shape. Another is having 1000 blocks in one block by storing type info in the tileEntity.

 

[Xemrox]

You made my day thx for that explanation!

Now my basic questions are answered and i can go on with the network stuff without worrying that i do things straight against forge.