gummby8

I have a monster that has a % chance to teleport away when it receives damage. When it teleports it creates a cloud of particles. All the random number gen and damage takes place server side, and the particles occur client side. Currently I am using a datawatcher to tell the client when to spawn particles, but it doesn't always work, sometimes it is late and the mop teleports away, then creates the particles. I was thinking of having the monster spawn an invisible entity once it teleports and that entity could generate the particles instead, unless there is an easier way that I am not thinking of. Thank you,

I would look into Tabula, I think ichun did just port it to 1.10. I still maintain a 1.8 client to use it. There was an updated standalone modeler that supported animations like Tabula does, I can't find it at the moment though.

Ah... Reading.... Got it

What do I need to do in LivingHurtEvent to prevent the entire event? The damage is not delt, but the mob is still knocked back and flashes red

I did cancel the event. Setting the hurtResistantTime to 0 does not cancel the knockback or red flash.

That did it. Thank you. I was not aware there was an onUpdate for items......

I have a note item. the player can read. I have 10 textures for said note item. Rather than creating 10 different notes with 10 different renders I wanted to just create 1 note class and 1 renderer that will change the resourcelocation based on a variable that is set in the note item when it is created in game. So if a mob drops a note, that note class will randomly pick a number 1-10 and the renderer will use that number to determine what texture to display on the note. I think I want to use dmg values, but I can't see how to randomly set that value when a new note itemstack is created.

K understood, good call. New problem "Where it is needed" is when it is rendered, specifically during the RenderHandEvent. Which is of course client side. Which will not make the itemstack damage persistent. So at the moment, it swaps textures fine, but if I drop and pickup the item it reshuffles the textures because according to the server the damage is still 0. What other event or time would be best, server side, to set the itemstack damage?

If you set your texture size properly on your boat model it will tile the 16x16 texture for you. What are you using to model your boat?

I have a mob that takes on the texture of the block it is spawned on. This is easy enough to get client side. IBlockState iblockstate = this.worldObj.getBlockState(this.getPosition().down()); BlockRendererDispatcher blockrendererdispatcher = Minecraft.getMinecraft().getBlockRendererDispatcher(); IBakedModel ibakedmodel = blockrendererdispatcher.getModelFromBlockState(iblockstate, this.worldObj, new BlockPos(0,0,0)); String string = ibakedmodel.getTexture().getIconName() + ".png"; String[] parts = string.split(":"); ResourceLocation textureLoc = new ResourceLocation(parts[0] + ":textures/" + parts[1]); Main problem with this is BlockRendererDispatcher is client side only. I only need the IBlockState of the block, which I can get on the server. but how can I get that to the client via IEntityAdditionalSpawnData? I thought of using x, y, z cords and then this.bPos = new BlockPos(x,y,z); this.fallTile = this.getWorldObj().getBlockState(this.bPos); but that block could change. So saying you are fighting the monster, you die or whatever, and come back later. If the blockpos that the monster was using for its texture was broken or changed, then the monster would change. Is there a different way to get a blockstate without having a blockpos? Like a block ID or something?

Are those variants different blockstates? Because it picked up different color wool and stairs

It does work console output for the texture location mb:textures/blocks/control_block/output.png So it picks the texture for the "front" side of the block. according to the model json

I tested it with a few mods, but now that you say that, I went back to check their git, they do not have sub folders, all the textures are at the root of the blocks folder. I'll create a test block and bury it in some sub folders to see what results I get.

How long does the entity last? You only save to NBT when the chunk unloads. Like when you move far away, or leave the world, of gracefully shutdown a server. If the entity is gone before the chunk unloads, it will never save, and thus never need to load. read and write to NBT is only to be used to preserver vital entity data when the chunk unloads from the ram. It saves all that data to disk so when the chunk is loaded again, when a player walks close enough, then the entity is brought back into existence. Cast your charm, them before the entity dies, save and quit out of the world. Reload your world and see if you get an NBT read. Many times I see a crash report because I derped up my NBT read and write on projectiles. So just in the off chance the client is closed while a projectile entity existed, it would safely die or reload when the client was re-opened.

I could be wrong, because I am used to working in 1.8, but your model class looks off. You are creating a new ModelRenderer every render frame, which I am pretty sure is wrong. Here is one of my most basic model classes https://github.com/gummby8/ModularBosses/blob/master/main/java/com/Splosions/ModularBosses/client/models/projectiles/ModelBoulder.java Note super.render. That could be what you are missing. public void render(Entity entity, float f, float f1, float f2, float f3, float f4, float f5) { super.render(entity, f, f1, f2, f3, f4, f5); setRotationAngles(f, f1, f2, f3, f4, f5, entity); part.render(f5); }

NBT is writing and reading from the disk. You shouldn't be reading from NBT unless you are loading an entity that was not already loaded. Like when you log into a world for the first time, or move into an entity load range. Also Reading and Writing to NBT is a server side method. So if you are hoping to get it to pass something to the client that won't happen. You can probably use IEntityAdditionalSpawnData if that is still a thing...I am stuck in 1.8 for now.

So you want to find how high your entity is from the nearest solid block directly below the entity? BlockPos blockPos = new BlockPos(this.posX, this.posY, this.posZ); while (!worldObj.getBlockState(blockPos).getBlock().getMaterial().blocksMovement()) { blockPos = blockPos.down(); } That will find the nearest solid block straight down. Then you can calculate the distance

Something I learned, that I'll put here in case someone else is looking to do this later. Because the crash report you get from it didn't really point to the problem line. public void getTexture() { if (textureBlockID == -1) { BlockPos blockPos = new BlockPos(this.posX, this.posY, this.posZ); while (!worldObj.getBlockState(blockPos).getBlock().getMaterial().blocksMovement()) { blockPos = blockPos.down(); } IBlockState iblockstate = this.worldObj.getBlockState(blockPos); textureBlockID = Block.getStateId(iblockstate); System.out.println("" + textureBlockID); this.hardness = iblockstate.getBlock().getBlockHardness(this.worldObj, blockPos); this.getEntityAttribute(SharedMonsterAttributes.maxHealth).setBaseValue(this.golemMaxHealthMulti * this.hardness); this.heal((float) (this.golemMaxHealthMulti * this.hardness)); } } @Override public void readSpawnData(ByteBuf additionalData) { textureBlockID = ByteBufUtils.readVarInt(additionalData, 4); IBlockState iblockstate = Block.getStateById(textureBlockID); BlockRendererDispatcher blockrendererdispatcher = Minecraft.getMinecraft().getBlockRendererDispatcher(); IBakedModel ibakedmodel = blockrendererdispatcher.getModelFromBlockState(iblockstate, this.worldObj, new BlockPos(0,0,0)); String string = ibakedmodel.getTexture().getIconName() + ".png"; String[] parts = string.split(":"); textureLoc = new ResourceLocation(parts[0] + ":textures/" + parts[1]); } @Override public void writeSpawnData(ByteBuf buffer) { getTexture(); ByteBufUtils.writeVarInt(buffer, textureBlockID, 4); } I am a bit fuzzy on the math part but when you write and read to the ByteBuf, you have to specify how many bytes to use. When I looked at how many some of the other classes in MC use, it was 2. But with blockstateIDs, colored wool blocks in particular, their int ID was too big for just two bytes, so I increased it to 4 bytes for the ByteBuf, and now it works.

So how would one make an entity look like the block it spawned on nowadays? For when I update.

I derped, I could have sworn I had done this before a year or so ago....I did

I had my own troubles with world edit back in the day and ended up swapping over to Schematica schematics. World edit for 1.8 didn't work right with custom blocks between worlds because their block ids would change? Schematica made a block map to fix it. Not sure if WE has issues with custom tile entities either, but I never had an issue with Schematica.

But that is if you have the class already, the EntityList.getEntityNameList() gives a list of strings doesn't it? So doesn't one have to take those names, create entities Entity entity = EntityList.createEntityByName(name, world); and then check if they are an instanceof EntityLiving...or whatever.

Am I missing something here? Can you elaborate a bit.

I have a mob spawner that lists all EntityLiving in the selection gui. But yes I needed to create an instead first and then check with instanceof

So i came across something even more interesting today. Since I have the build speed turned up so far that each room would build in 1 tick, if there was ever an incident with missing blocks it is a LOT more pronounced. I thought there could be an issue in the schematic build logic, but today I saw a hole span across 2 separate rooms. a chunk sized hole either. it was rectangular. and the way the schematic is built it makes no sence, the schematic is built left to right bottom to top. But this hole spanned, partially left to right, and all the way from bottom to top. It was like those blocks either got re-written back to air, or never had their block states updated. and to have it span across 2 separate rooms, it means that hole persisted over at least 2 ticks. It was like the blocks in the hole refused to take on the new blockstate. And to make things even more frustrating, it is completely random! I can generate 20 dungeons, and maybe 1-2 will have these holes in them. I'll try to add some markdirty or scheduleblockupdate in there and see what happens.