Jump to content

Recommended Posts

Posted

Hello, i'm trying to make a function to reduce the player knockback, so i did this :

   public void reduceVelocity(EntityPlayer player) {
        if(isVelocityToggle){
            mc.thePlayer.sendChatMessage("on");
            player.motionX *= 0.5;
            player.motionY *= 0.5;
            player.motionZ *= 0.5;
            mc.thePlayer.velocityChanged = true;
            String motionX= player.motionX+"";
            String motionY= player.motionY+"";
            String motionZ= player.motionZ+"";
            mc.thePlayer.sendChatMessage("motion X : "+motionX);
            mc.thePlayer.sendChatMessage("motion Y : "+motionY);
            mc.thePlayer.sendChatMessage("motion Z : "+motionZ);
        }
        else{
            mc.thePlayer.sendChatMessage("off");
            player.motionX *= 1;
            player.motionY *= 1;
            player.motionZ *= 1;
            mc.thePlayer.sendChatMessage(player.getName());
            String motionX= player.motionX+"";
            String motionY= player.motionY+"";
            String motionZ= player.motionZ+"";
            mc.thePlayer.sendChatMessage("motion X : "+motionX);
            mc.thePlayer.sendChatMessage("motion Y : "+motionY);
            mc.thePlayer.sendChatMessage("motion Z : "+motionZ);
        }


    }

But the knockback of the player remains the same, even if the values of the motions have changed. :/ 

Screenshot

 

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Looks like I've figured it out, after entirely too much time wasted on trial-and-error.   The solution was to create /resources/data/minecraft/ and place the tags under there, rather than the mod's data directory. I also needed to add  "replace": false, to the JSON files under /resources/data/minecraft/tags/block/ -> needs_stone_tool.json and mineable/pickaxe.json.   I cannot overstate how dumb this is. I don't think developers should be needing to create additive Minecraft subdirectories for files that belong to a mod. These properties should belong to the block properties anyway, since we're specifying that a tool is required... we should be specifying what that tool is in the same place. (I'm so glad I came back to this mess!) Anyway, it is fixed. Hopefully this helps some poor unsuspecting newbie somewhere down the road.
    • I downloaded Forgematice, moved the file to the mods folder, but after starting Minecraft it does not detect any modifications, I need help
    • Upon registering a new account on here, there's a simple security question. Something along the lines of "name a tool you can craft in vanilla Minecraft" and "name a weapon you can craft in vanilla Minecraft". I answered these with answers that are correct. Yet I'm told I "didn't pass the security check". This happens with every answer to every question. If you can't craft a pickaxe, or use a sword as a weapon in vanilla Minecraft then you and I must be playing a totally different game!!
    • Hello, and happy new year! I've returned to modding while on break from work, and cannot make heads or tails of the method for setting the correct tool for breaking a custom block. This should be a simple affair, but after digging through the vanilla files, all I could find was  assets/data/minecraft/tags/block/mineable/pickaxe.json (and axe, hoe, shovel). So I figured this must be how they're specifying the tool for each block. Yet, after implementing a similar file in my own data folder, it still doesn't work. Plus, this doesn't address the issue of specifying what level of tool is required (wood/stone/iron, etc).   So, please... how should this be being done, properly? And could it be done through the Java code rather than JSON files, without overriding functions for block breaking? I'm either missing something obvious, or -- as is more likely the case -- this is just far more convoluted than it ought to be, for something that should just be a field or two in the Block Properties.
    • and this forge error, is just for forge 1.19.2
  • Topics

×
×
  • Create New...

Important Information

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