Draco18s

This is nonsense. You need to return an instance of IMana

@diesieben07 : do we have a common issue for this yet?

What are you using this information for?

Why do you care?

Please do not scatter bold text like that, it actually harms the readability of your post.

ItemStack#isEmpty does not work on null stacks. It will crash.

For reference, you can scan an entire chunk and replace blocks in about 400,000 nanos (0.4 ms). You don't really need to worry about time slicing.

I think he means the baked item model. Which wound be the IBakedModel instance.

Items have models, and models have one or more textures.

Just to check: How are you storing these additional properties?

someUuid == otherUuid

Entities swimming in water is handled by the entity class(es) and checks specifically for Material.WATER

Again, you check to see if your data contains the player before adding the modifier (and if they're not in it, you don't add the modifier). You also don't do a damn thing with hasHealthBoost

That had nothing to do with what I said, at all. Imagine a player equips your armor set for the full time. They will not exist in your playersWithSet collection.

Note: IStateMapper / StateMapperBase are client side only.

I just want to look at this section for a bit: Boolean hasMithrilSet = ArmorMithril.isFullSet(player); if(playersWithSet.contains(key)) { //do stuff } else if(hasMithrilSet) { playersWithSet.add(key); } Equipment changed! Player has a full set! We have no idea who this player is! Store player in list! Done! Wot.

You really should dig through the Item class at some point. public int getMaxDamage(ItemStack stack) { return getMaxDamage(); } ItemStacks can store data beyond just what Item it represents, but also capabilities and NBT data, all of which is accessible in the above Item method.

Blocks are singletons, there exists exactly 1 instance of your block class. All of your blocks would share a reference to the singular TE. You cannot do this. @diesieben07 candidate for common problem.

This: https://gist.github.com/Terrails/60cb566ea175bef4ca92ff5bd246bdb5#file-gistfile1-java-L1 Will never work. You want to get the material for the block based on its state, then you need to provide that state information via getActualState

I take it this was too hard to arrive at: player.getEntityAttribute(SharedMonsterAttributes.MAX_HEALTH).applyModifier(new AttributeModifier(uuid, name, 2, 2)); UUID is a unique UUID (you can create one at random, then save it as a hardcoded value). name is just whatever you want to call it.

Caused by: java.lang.IllegalArgumentException: Cannot set property PropertyBool{name=powered, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in BlockStateContainer{block=null, properties=[]} You haven't overriddencreateBlockState

Ok, two three things: 1) This particular error is found all the time, there's literally dozens of threads. A little searching would have gone a long way. 2) Yes, this error is huge and hard to understand, but it's because the main error ("unable to load model") can have multiple root causes: The file could be missing, it could be improperly formatted, be missing a key piece of data. The first error you see is only helpful in knowing "a problem exists with this item" you have to dig deeper to find out what caused that error. 3) The error you just posted is literally the same error you were just told to fix.

Learn to read your own damn errors.

Let me see here, of the core mods you have present... I've heard of these ones: IC2core (industrialcraft-2-2.7.81-ex111.jar) CCLCorePlugin (CodeChickenLib-1.11.2-3.0.0.298-universal.jar) CoFH Loading Plugin (CoFHCore-1.11.2-4.2.8.16-universal.jar) Inventory Tweaks Coremod (InventoryTweaks-1.62.jar) SoundFixPatchingLoader (AmbientSounds v2.1.2 mc1.11.2.jar) I can be pretty confident that these are not at fault: CCLCorePlugin (CodeChickenLib-1.11.2-3.0.0.298-universal.jar) CoFH Loading Plugin (CoFHCore-1.11.2-4.2.8.16-universal.jar) Inventory Tweaks Coremod (InventoryTweaks-1.62.jar) My suggestion is to remove all mods that are not the coremods, check to see if the problem persists. Regardless of the outcome you will perform a binary search to locate the mod at fault: 1) If the problem is present: remove half of the mods most recently added 2) If the problem is not present: add half of the mods most recently removed Repeat until adding/removing a single mod causes the issue.

I have a feeling most of your issues stem from the fact that you're using two blocks.