[1.10.2] SpawnEntityInWorld

[ErnstLustig]

I'm still new to modding, so sorry if this is a stupid question.

I want to drop a new item when I right click with a tool. I think you do that with spawnEntityInWorld if I figured that out correctly.

But if I do that I get the item, but it has no texture. Apparently it doesn't get initialized correctly. What do I have to do instead?

 

@Override
    public ActionResult<ItemStack> onItemRightClick(ItemStack stack, World world, EntityPlayer playerIn, EnumHand hand) {
        world.spawnEntityInWorld( new EntityItem( world, playerIn.posX, playerIn.posY, playerIn.posZ, new ItemStack( new ItemTest() ) ) );
        return new ActionResult<>(EnumActionResult.SUCCESS, stack);
    }

[ErnstLustig]

Nevermind I figured it out. Instead of new ItemSaddle() for example I need to use Items.SADDLE. Makes sense.

But then I noticed that it spawns 2 copies of that item, one of which is not really there. I fixed it with if( !world.isRemote ), but I'm not sure if that's correct. Shouldn't the server know about that item?

[Matryoshika]

I fixed it with if( !world.isRemote ), but I'm not sure if that's correct. Shouldn't the server know about that item?

If anything, you should only spawn it if !world.isRemote (if not client) or return if world.isRemote (if client) so that the entityItem is only spawned server-side.

If you "fixed" it by making the ghost item vanish, then you removed the client-side spawned one.

[gurujive]

You will need an entity class, entity model class, entity render class, item class, and item model for the entity.

(scratch the item class and item model if you are just looking to summon/spawn it)

 

(I recommend techne and mcrayfish model maker)

 

Here is an examplemod src of what I'm talking about, So you can clearly see what needs to be done, It has one entity that is also a wieldable item that can be thrown:

https://www.dropbox.com/s/npqsjfyga587vyq/examplemodsrc.7z?dl=0

 

(I wrote this for 1.10.2 using java 8.)

 

My guess would be to make an item like a stick and when you right clicked spawn a new entity in the world similar to how you would create a new explosion.

[Draco18s]

You will need an entity class, entity model class, entity render class, item class, and item model for the entity.

(scratch the item class and item model if you are just looking to summon/spawn it)

 

For this (dropping an item), no you do not.  You've told like three people now that they need a custom entity and in all three cases you have been flat wrong.  Stop doing this.

[gurujive]

You will need an entity class, entity model class, entity render class, item class, and item model for the entity.

(scratch the item class and item model if you are just looking to summon/spawn it)

 

For this (dropping an item), no you do not.  You've told like three people now that they need a custom entity and in all three cases you have been flat wrong.  Stop doing this.

 

Why wouldn't you create your own? Its not clearly stated if its "custom" or not. Since there is problems with the textures i figured it was not a vanilla entity he/she was looking to spawn. (I may be wrong though)

In which case they would already have a custom entity but may not be registering it right, or may not have a render model. Or be rendering the wrong model, or have an incorrect texture.

 

You could spawn an entity that's already in game though you're right.

 

And the previous posts you were talking about:

Fireworks entity is an entity, and the topic i posted on was for a custom fireworksrocket entity.

The 2nd I suggested a possibility of an invisible/x entity. That you could put on blocks.

[Draco18s]

Why wouldn't you create your own? Its not clearly stated if its "custom" or not. Since there is problems with the textures i figured it was not a vanilla entity he/she was looking to spawn. (I may be wrong though)

In which case they would already have a custom entity but may not be registering it right, or may not have a render model. Or be rendering the wrong model, or have an incorrect texture.

 

If an item has the wrong texture (e.g. missing) there is a problem with the item's JSON model or with its registration, there is nothing wrong with Vanilla's EntityItem class.

 

There is no reason to create a custom EntityItem class unless you need to override certain EntityItem behavior.

 

Please stop suggesting a complicated solution to a simple problem.

[gurujive]

Why wouldn't you create your own? Its not clearly stated if its "custom" or not. Since there is problems with the textures i figured it was not a vanilla entity he/she was looking to spawn. (I may be wrong though)

In which case they would already have a custom entity but may not be registering it right, or may not have a render model. Or be rendering the wrong model, or have an incorrect texture.

 

If an item has the wrong texture (e.g. missing) there is a problem with the item's JSON model or with its registration, there is nothing wrong with Vanilla's EntityItem class.

 

There is no reason to create a custom EntityItem class unless you need to override certain EntityItem behavior.

 

Please stop suggesting a complicated solution to a simple problem.

 

You are repeating what I stated.

"(scratch the item class and item model if you are just looking to summon/spawn it)"

[Draco18s]

In which case:

 

Stop suggesting custom entities for simple problems.  It is the wrong solution.

[gurujive]

In which case:

 

Stop suggesting custom entities for simple problems.  It is the wrong solution.

 

No, YOU, are the wrong solution.

 

lol... I just had to...

getting off here now. Have a goodn'

[ErnstLustig]

I tried to drop vanilla items as well and they had a missing texture too, but the problem is solved as described above. Initializing objects after the register phase seems like a bad idea, I got it.

@Matryoshika: Yeah, that was what I was confused about. I fixed it, but it didn't make sense to me. I know now that I got the meaning of isRemote mixed up because I'm not a native speaker. I thought isRemote==true means Server side, but it's vice versa, right? This means now that if( !world.isRemote ) is the correct thing to check for server side and this is how I accidently fixed it. Not sure what you mean with "if not client" though. Doesn't !world.isRemote already check for server side only?

[Matryoshika]

... if !world.isRemote (if not client) or return if world.isRemote (if client)...

Not sure what you mean with "if not client" though. Doesn't !world.isRemote already check for server side only?

First, I merely described what each check does.

However, there are two ways of fixing the issue: 1) Nest code inside if-statement that checks if it is run on the server

if(!world.isRemote){
    //do stuff serverside
}

 

or 2) have your code do nothing client-side.

if(world.isRemote)
    return;

//do stuff serverside