Leaderboard

It isn't possible because when the game is loaded, the data is the only thing that makes the TE exist there after a reload of the world. So you need to at least have the default read and write anything else doesnt have to go there.

Actually, since you're starting this now and 1.13 is getting close I would suggest taking the same approach and making it fully "flat" -- separate block for every variant. The way 1.13 seems to be going is that properties like facing orientation will still be applied to blocks but all the different types of wood will be their own block. I am not sure the entire motivation but I'd bet it is because the combination of variants with other states simply runs out of room with the 4-bit per block position "metadata". So instead of doing a half-assed approach like having two log blocks each with multiple variants just go all the way and make every variant its own thing. For more on the 1.13 approach see: https://minecraft.gamepedia.com/1.13/Flattening It will make your transition to 1.13 a LOT easier if you go ahead and flatten now.

In the code the OP posted he has one though He is just using a deprecated version. Which is his issue as far as I can tell.

This is why your TE is not appearing, this method needs to have a IBlockState parameter.

@Override public NBTTagCompound writeToNBT(NBTTagCompound compound) { super.writeToNBT(compound); compound.setInteger("cooldown", cooldown); if(compound.hasKey("CustomName", 8)) { compound.setString("CustomName", this.customName); } return compound; } This will never be true. This public void updateTick(World worldIn, BlockPos pos, IBlockState state, Random rand){ if (!worldIn.isRemote){ if(worldIn.getTileEntity(pos) instanceof TileEntityTrebuchet) { ((TileEntityTrebuchet)worldIn.getTileEntity(pos)).setCooldown(0); } } } doesn't do what you think it does. It fires each tick, sure... for one random block in all of loaded chunks. Implement ITickable in your TileEntity and do the stuff with the cooldown there. What makes you think no tile entity is created? Have you placed a breakpoing in any of your methods that get the tile entity and inspected the TE local?

Separating them into 2 blocks creates a lot of confusion since your will have 2 meaningless blocks (BlockThingOne and BlockThingTwo). That said this way is pretty good if you want to save on block ids. Creating a unique block for each variant is a more intuitiva approach. This is also how variants function in 1.13. So this approach will allow you to update your mod to 1.13 easier and is more intuitive but it's less conservative on block ids. Alternatively you can store all your variants in a single block by using a TileEntity. Since TEs can be non-tickable now this approach is also viable.

In modern computing having something that is checked occasionally isn't going to be a performance problem. Even every tick there are literally 10's of thousands (maybe more) checks going on. The only things that will really bog down a computer nowadays are things like large loops or recursions especially if they include expensive operations. But just doing a couple straight-forward checks for value and/or type on the occasion where the music attempts to start won't be a problem. When programming it is good to think about performance optimization but you should always start with trying to make your code well-structured logically. This helps prevent bugs and aids maintenance and collaboration. If you think there is a possible performance concern then profile your code and see what is really causing problems and focus on that. There is no point fretting over the little stuff when performance is going to be dominated by a couple big offenders.

@LenManos Your staff / mods / whoever works with you was complaining about my mod code and cussing at me as well, and even other people i know said the forge forms are assholes to everyone and idc if i get baned. because you cant speak to someone like that saying you know everything. & you all so stop saying well we dont support this version any more youtubers still play with 1.7.10 & above so you really need to think twice

First off, you can't even spell my name right, secondly for those who see this, this is the thread he got a warning for, specifically the post where he called us all assholes http://www.minecraftforge.net/forum/topic/65936-forge-server-error/ As you can see, nobody cussed at him. As for us being assholes, because we are blunt and have rules, and refuse to support older versions does NOT make us assholes. The analogy I like to take is you going to Microsoft, and asking for support with Windows 95. They will tell you to either sod off or pay them a ABSURD amount of money. As for the way we speak to you, like we know 'everything', it's because piratically we do. In regards to the software WE'VE WRITTEN and spent the last 5+ years supporting and developing! You coming in, and failing to follow our directions on the SIMPLEST of errors just shows your arrogance and stupidity. {Note, I used stupidity, and not ignorance, because ignorance implies a ability to update your thinking} As for the youtubers who still play 1.7.10, that's fine. People can PLAY whatever they want. Hell you can {tho its highly discouraged} develop for whatever you want. However the line is drawn with your trying to force US to develop/support the old versions. It's a simple concept, if you want our help, stay updated. If not you're on your own. So ya, your last ban was for a week, you obviously didn't learn your lesson, so now enjoy the lifetime.

A fix to what? What's broken? You haven't given us any information about how to diagnose what's wrong. All you've said is "doctor, it hurts."

Define not working

Define not working.

I think I'm going back to my 1.12 worlds. I'm finding that it's not all that fun trying to explore without a map. Besides, in my 1.13 worlds so far, none of the turtles have hatched shells for me to use to craft helmets. Not knowing if there will be a point when the mods can rely on a 100 percent completion of Forge is discouraging, I have to say.