Jump to content

(1.16.5 MCP) getShooter in DamagingProjectileEntity throws nullPointerException


Recommended Posts

Posted (edited)

so i have an entity that extends DamagingProjectileEntity and it has tick method and i want to play a sound(inside of my projectile class) when a little time passes but im trying to do getShooter.playsound or getShooter.getEntity().playsound but it doesnt work(as i said it throws nullPointerException) by the way the crash log ONLY says nullPointerException in that line

 

@Override
    public void tick() {
        super.tick();
        ++this.time;
        System.out.println(time);
        if(!world.isRemote) {
            if(time == 70) {
                getShooter().playSound(ModSounds.MYSOUND.get(),1,1); //or getShooter().getEntity().playSound(ModSounds.MYSOUND.get(),1,1); doesnt work either
                 this.remove();
            }
        }
    }

 

Edited by ElTotisPro50
Posted
58 minutes ago, diesieben07 said:

getShooter must be explicitly set by you and even then it can return null (e.g. if the player logged out). So you can't just use it directly, you must check first.

Are you sure you want to play the sound at the shooter's position? Why do you not just use this.playSound?

check if shooter is playerentity?

if(getShooter() instanceof PlayerEntity)

 

this.playsound will play the sound in the throwable entity's position right?if i throw my entity with acceleration or motion the player could'nt hear it because the entity is far enough

Posted
5 hours ago, diesieben07 said:

Yes, this will also ensure the shooter is not null.

Just making sure. If you do want to play it at the player's position then what you did is correct. You just have to actually set the shooter when creating the projectile.

is not throwing nullPointerException or crashing or something it just doesnt do anything

@Override
    public void tick() {
        super.tick();
        ++this.time;
        System.out.println(time);
        if(!world.isRemote) {
            if(time == 70) {
                if(getShooter() instanceof PlayerEntity) { //if(getShooter().getEntity() instanceof PlayerEntity) { this just will throw null again
                    getShooter().playSound(ModSounds.MYSOUND.get(),1,1); //getShooter().getEntity().playSound(ModSounds.MYSOUND.get(),1,1); doesnt work either
                }
                this.remove();
            }
        }
    }

 

Posted
10 hours ago, diesieben07 said:

Show more of your code, specifically the whole projectile class and where you spawn the projectile.

My item class

public class MyItem extends Item {

    public MyItem(Properties properties) {
        super(properties);
    }

	@Override
    public ActionResult<ItemStack> onItemRightClick(World world, PlayerEntity player, Hand handIn) {
        ItemStack stack = player.getHeldItemMainhand();
        if(player.isSneaking()) {
            world.playSound(player,player.getPosition(),ModSounds.SOUND.get(),SoundCategory.MASTER, 1, 1);
        }
        if(!world.isRemote) {
            if (player.isSneaking()) {
                if (stack.getItem() instanceof MyItem) {
                    ThrownMyEntity entity = new ThrownMyEntity(ModEntityTypes.THROWNMYENTITY.get(), world);
                    Vector3d aim = player.getLookVec();
                    entity.setPosition(player.getPosX() + aim.x * 1.7,
                            player.getPosY() + (aim.y + 0.5) * 1.7,
                            player.getPosZ() + aim.z * 1.7);
                    entity.rotationYaw = player.rotationYaw;
                    entity.rotationPitch = player.rotationPitch;
                    double throwSpeed = 0.7;
                    entity.setMotion(aim.x * throwSpeed,aim.y * throwSpeed,aim.z * throwSpeed);
                    world.addEntity(entity);
                    player.setItemStackToSlot(EquipmentSlotType.MAINHAND, ItemStack.EMPTY);
                }
            }
        }
        return super.onItemRightClick(world, player, handIn);
    }
}

 

ThrownMyEntity Class

public class ThrownMyEntity extends DamagingProjectileEntity implements ITickableTileEntity {

    private int time;

    public ThrownMyEntity(EntityType<? extends DamagingProjectileEntity> entityType, World world) {
        super(entityType,world);
    }

    //This makes that the entity cant be pushed
    @Override
    public boolean canBePushed() {
        return false;
    }

    //This makes the entity can be hurt(like a ghost)
    @Override
    public boolean canBeCollidedWith() {
        return false;
    }

	@Override
    public void tick() {
        super.tick();
        ++this.time;
        System.out.println(time);
        if(!world.isRemote) {
            if(time == 70) {
                if(getShooter() instanceof PlayerEntity) { //if(getShooter().getEntity() instanceof PlayerEntity) { this just will throw null again
					getShooter().getEntity.DOSOMETHINGTOTHESHOOTER
                }
                this.remove();
            }
        }
    }

    @Override
    protected void registerData() {

    }

    @Override
    public boolean isInWater() {
        return false;
    }

    @Override
    public boolean isInLava() {
        return false;
    }

    @Override
    public boolean isBurning() {
        return false;
    }

    @Override
    public boolean isGlowing() {
        return false;
    }

    @Override
    public IPacket<?> createSpawnPacket() {
        return NetworkHooks.getEntitySpawningPacket(this);
    }

    @Override
    public boolean isWet() {
        return false;
    }

}

 

Posted
1 hour ago, diesieben07 said:

You never set the shooter on your entity. How do you expect getShooter to return anything? Magic?

what does that mean cast the player to shooter?

PlayerEntity player = (PlayerEntity) getShooter().getEntity(); 

Posted
1 hour ago, diesieben07 said:

No. Look at the available methods on the projectile. It is very obvious which one sets the shooter.

in the same tick method

if(getShooter() instanceof PlayerEntity) {
     setShooter(getShooter());
     getShooter().setGlowing(true);
}

right?

Posted
23 minutes ago, ElTotisPro50 said:

right?

no not to getShooter, call setShooter from your Item in onItemRightClick then use the Player which you get as a parameter

4 minutes ago, ElTotisPro50 said:

what i just told you didnt work, throws null again

yeah since:

Entity entity = getShooter(); // shooter is at this point null
setShooter(entity); // the new shooter is null since the old shooter was null

 

Posted
1 hour ago, Luis_ST said:

no not to getShooter, call setShooter from your Item in onItemRightClick then use the Player which you get as a parameter

yeah since:

Entity entity = getShooter(); // shooter is at this point null
setShooter(entity); // the new shooter is null since the old shooter was null

 

it worked :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • "I want to understand how complex mods with ASM transformation and coremods work, such as Xray or AntiXray. Why do they break when you simply rename packages? What features of their architecture make refactoring difficult? And what techniques are used to protect these mods? I am interested in technical aspects in order to better understand the bytecode and Forge loader system."
    • I can't figure out if you're looking for help trying to steal someone elses work, or cheat at the game....
    • Title: Why Is It So Hard to Rename and Restructure Mods Like Xray or AntiXray? 🤔 Post text: Hey everyone! I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice. Here’s the issue: When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward. But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart. Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function. So my question is — why is this so much harder with cheat mods like Xray? Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features? I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing. Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals? Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it. Thanks in advance for any help or discussion. ✌️
    • just started making cinamatic contect check it out on my channel or check out my facebook page    Humbug City Minecraft Youtube https://www.youtube.com/watch?v=v2N6OveKwno https://www.facebook.com/profile.php?id=61575866982337  
    • Where did you get the schematic? Source/Link? And do use an own modpack or a pre-configured from curseforge? If yes, which one On a later time, I can make some tests on my own - but I need the schematic and the modpack name
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.