Possible to make a block that adds the wither affect upon entity collision?

[Aideux]

Just like the title says, is it possible to make a block that adds the wither status effect upon entity collision? I'm assuming that something would be added to the block constructor, but I'm not entirely sure what the correct terminology is. Can someone point me in the right direction? Thank you!

[LexManos]

Look at soul sand, it does things when the entity collides with it.

[Aideux]

  On 4/27/2016 at 4:56 AM, LexManos said:

Look at soul sand, it does things when the entity collides with it.

How do I access another block's code?

[Draco18s]

Define "access."  If you want to look at it, like Lex said, then open up the Forge-src jar in the project hierarchy and browse down to net -> minecraft -> blocks -> BlockSoulSand.java

[Aideux]

  On 4/27/2016 at 2:55 PM, Draco18s said:

Define "access."  If you want to look at it, like Lex said, then open up the Forge-src jar in the project hierarchy and browse down to net -> minecraft -> blocks -> BlockSoulSand.java

So I looked at the code, and it doesn't seem like there's any explicit method call to make entity collision instantiate the wither effect.

[Choonster]

  On 4/27/2016 at 3:02 PM, Aideux said:

  Quote

Define "access."  If you want to look at it, like Lex said, then open up the Forge-src jar in the project hierarchy and browse down to net -> minecraft -> blocks -> BlockSoulSand.java

So I looked at the code, and it doesn't seem like there's any explicit method call to make entity collision instantiate the wither effect.

 

Soul Sand doesn't apply the Wither effect, it slows down entities.

 

There are only two methods in

BlockSoulSand

excluding the constructor: one defines the bounding box (so entities can collide with it), the other slows down entities when they collide with the block.

 

When an entity collides with your block, check if it's an

EntityLivingBase

and then use

EntityLivingBase#addPotionEffect

to apply the Wither effect to it.

[Aideux]

  On 4/27/2016 at 3:18 PM, Choonster said:

  Quote

  Quote

Define "access."  If you want to look at it, like Lex said, then open up the Forge-src jar in the project hierarchy and browse down to net -> minecraft -> blocks -> BlockSoulSand.java

So I looked at the code, and it doesn't seem like there's any explicit method call to make entity collision instantiate the wither effect.

 

Soul Sand doesn't apply the Wither effect, it slows down entities.

 

There are only two methods in

BlockSoulSand

excluding the constructor: one defines the bounding box (so entities can collide with it), the other slows down entities when they collide with the block.

 

When an entity collides with your block, check if it's an

EntityLivingBase

and then use

EntityLivingBase#addPotionEffect

to apply the Wither effect to it.

 

So here's what I've come up with, but it still doesn't work! Can you please help me out? I'm really confused.

package com.aideux.cursedblock;

import net.minecraft.block.Block;
import net.minecraft.block.material.Material;
import net.minecraft.block.state.IBlockState;
import net.minecraft.creativetab.CreativeTabs;
import net.minecraft.entity.Entity;
import net.minecraft.entity.EntityLivingBase;
import net.minecraft.potion.Potion;
import net.minecraft.potion.PotionEffect;
import net.minecraft.util.BlockPos;
import net.minecraft.world.World;
import net.minecraftforge.fml.common.registry.GameRegistry;

public class BlockCursed extends Block 
{
public final String name = "cursedBlock";

public BlockCursed()
{
	super(Material.rock);
	GameRegistry.registerBlock(this, name);
	setUnlocalizedName(CursedBlock.MODID + "_" + name);
	setCreativeTab(CreativeTabs.tabMisc);
}
public void onEntityWalking(World world, int par2, int par3, int par4, Entity entity)
{
	if(entity instanceof EntityLivingBase)
	{
		((EntityLivingBase) entity).addPotionEffect(new PotionEffect(Potion.confusion.getId(), 100, 1));
	}
}

}

[Choonster]

There is no

Block#onEntityWalking

method in 1.8+, so your method doesn't override a super method and is never called. This is why you should always use the

@Override

annotation, you would have gotten a compilation error telling you this.

 

Use your IDE to auto-generate override methods.

 

Block#onEntityCollidedWithBlock(World, BlockPos, Entity)

is called when an entity that can trigger walking (i.e. returns

true

from

Entity#canTriggerWalking

) walks on top of the block.

 

Block#onEntityCollidedWithBlock(World, BlockPos, IBlockState, Entity)

is called when an entity collides with the block in any direction.

[Draco18s]

Note that the block boundary must be smaller than 1x1x1 in the direction you wish for collisions to occur in.

[Aideux]

  On 4/28/2016 at 4:42 AM, Draco18s said:

Note that the block boundary must be smaller than 1x1x1 in the direction you wish for collisions to occur in.

Hey, I got it to work, thank you! For some reason, however, the wither effect is only added when the entity collides with the top of the block. This may have to do with the fact that I just copied and pasted the collision bounds from the soul sand class, so is there any way I can fix this? Thank you again, I really appreciate you helping me out!

[Choonster]

An entity can only collide with a block on a given side if the block's bounding box is inset by a small amount on that side. Soul Sand is only inset on the top (i.e. the maximum y coordinate is less than 1), so entities will only collide on the top.

[Aideux]

  On 4/28/2016 at 12:42 PM, Choonster said:

An entity can only collide with a block on a given side if the block's bounding box is inset by a small amount on that side. Soul Sand is only inset on the top (i.e. the maximum y coordinate is less than 1), so entities will only collide on the top.

 

So now the player can collide with the top and two sides to produce the wither effect, but the bottom and the remaining two sides do nothing... I'm sorry for being so persistent, but could you please point me in the right direction? Here's my code:

float f = 0.125F;
return new AxisAlignedBB((double)pos.getX(), (double)pos.getY(), (double)pos.getZ(), (double)((float)(pos.getX() + 1) - f), (double)((float)(pos.getY() + 1) - f), (double)((float)(pos.getZ() + 1) - f));

[Choonster]

If you want entities to be able to collide on all sides, call

Block#setBlockBounds

in the constructor with

OFFSET

as the minimum coordinates and

1 - OFFSET

as the maximum coordinates (where

OFFSET

is some small value like 0.125). This removes the need to override

Block#getCollisionBoundingBox

.

 

In 1.9, create a static final

AxisAlignedBB

field with these coordinates instead and override

Block#getCollisionBoundingBox

to return it.

[Draco18s]

0.125 is a fairly substantial amount: 2 pixels!

 

If you want something that looks like a full block you can have an offset amount of 0.0001 which IIRC is sufficient for collisions, but small enough that after being rendered you can't tell.

[Choonster]

I just tested this here, the smallest possible offset (to 4 decimal places) is 0.0011. With an offset of 0.0010, the player can only collide by walking into a corner of the block rather than anywhere on any face.

[Draco18s]

I typed that and had the sneaking suspicion that I may have added too many zeros.  The last time I futzed around with it (needing a full-cube block that was collidable from all sides) was in 1.6.4

[Aideux]

  On 4/28/2016 at 5:00 PM, Choonster said:

I just tested this here, the smallest possible offset (to 4 decimal places) is 0.0011. With an offset of 0.0010, the player can only collide by walking into a corner of the block rather than anywhere on any face.

So I gave your test code a shot and now I just fall through the block. I do get withered though haha, but I'm passing right through it like it doesn't exist.

[Esophose]

You likely made the bounding box size only 0.0011 rather than 1 - 0.0011 which would make it a microscopic dot on the corner of the block.

[Choonster]

  On 4/29/2016 at 2:33 AM, Aideux said:

  Quote

I just tested this here, the smallest possible offset (to 4 decimal places) is 0.0011. With an offset of 0.0010, the player can only collide by walking into a corner of the block rather than anywhere on any face.

So I gave your test code a shot and now I just fall through the block. I do get withered though haha, but I'm passing right through it like it doesn't exist.

 

Are you using 1.8.9 or 1.9? My code is for 1.9, for 1.8.9 you'd need to call

Block#setBlockBounds

with the coordinates instead of creating a static field and overriding

Block#getCollisionBoundingBox

.

[Aideux]

  On 4/29/2016 at 9:34 AM, Choonster said:

  Quote

  Quote

I just tested this here, the smallest possible offset (to 4 decimal places) is 0.0011. With an offset of 0.0010, the player can only collide by walking into a corner of the block rather than anywhere on any face.

So I gave your test code a shot and now I just fall through the block. I do get withered though haha, but I'm passing right through it like it doesn't exist.

[/quot

Are you using 1.8.9 or 1.9? My code is for 1.9, for 1.8.9 you'd need to call

Block#setBlockBounds

with the coordinates instead of creating a static field and overriding

Block#getCollisionBoundingBox

.

 

I'm using 1.8.9. What's the syntax look like for setBlockBonds as opposed to getCollisionBounding?

[Choonster]

  On 4/29/2016 at 2:16 PM, Aideux said:

I'm using 1.8.9. What's the syntax look like for setBlockBonds as opposed to getCollisionBounding?

 

Call

setBlockBounds

in your constructor. Look at the method definition in the

Block

class for the arguments.