Jump to content

Recommended Posts

Posted

Spawn:
https://ibb.co/NKnvqXk
How i would like:
https://ibb.co/BLYgwW7

 

public class BulletEntity extends AbstractBullet implements IEntityAdditionalSpawnData {
	...
	public static BulletEntity shoot(Level world, Player entity, float power, double damage, int knockback, RegistryObject<SoundEvent> soundName, float 	spreading) {
        BulletEntity entitybullet = new BulletEntity(world,entity);
        entitybullet.shootFromRotation(entity, entity.getXRot(), entity.getYRot()+0.4F, 0.0F, power, spreading);
        //entitybullet.shoot(entity.getViewVector(1).x, entity.getViewVector(1).y, entity.getViewVector(1).z, power, spreading);

        ...

I tried changing the arguments shootFromRotation, shoot. By height (y) I succeeded, but x did not. But when you turn the mouse, the coordinates of the entity are distorted
 

Actions in AbstractBullet(Identical to AbstractArrow) did not help

public abstract class AbstractBullet extends Projectile {
	...
	protected AbstractBullet(EntityType<? extends AbstractBullet> p_36717_, LivingEntity p_36718_, Level p_36719_) {
        this(p_36717_, p_36718_.getX()-0.5F, p_36718_.getEyeY()+0.5F, p_36718_.getZ(), p_36719_);
        this.setOwner(p_36718_);
        if (p_36718_ instanceof Player) {
            this.pickup = AbstractBullet.Pickup.ALLOWED;
        }

    }


 

Posted

So, there are two parts to getting the bullet to shoot out from the camera location. For the position, you need the eye position, which has the same x/z coordinates, but a separate y coordinate (can be obtained through #getEyeY). Second, you need the rotation of the view camera. This is done through the view vector commands, though you don't need to call it three times, just store the vector.

Posted
6 hours ago, Luckydel said:

Where should I insert this vector?

Basically you are just setting the x and y rotation of the projectile. I was simply stating you could store the result of the vector in a variable and get the values from that.

Posted
On 10/25/2022 at 2:07 AM, ChampionAsh5357 said:

Basically you are just setting the x and y rotation of the projectile. I was simply stating you could store the result of the vector in a variable and get the values from that.

I'm sorry, I don't understand how this will help me.
I need the projectile to spawn exactly in the center of the intersection. Right now he appears on the side. 

 

On 10/24/2022 at 4:04 AM, ChampionAsh5357 said:

Second, you need the rotation of the view camera

Am I not getting them here?

entitybullet.shootFromRotation(entity, entity.getXRot(), entity.getYRot()+0.4F, 0.0F, power, spreading);

 

 


 

Posted (edited)

 

I understand getXRot() gives values from -180 to 180 around the player, if i make getXRot()+0.5F it will be a mistake.

It seems to me to do if(getXRot()>0) +0.5F and (getXRot()<0) -0.5F not very correct

Edited by Luckydel
Posted
2 hours ago, Luckydel said:

I'm sorry, I don't understand how this will help me.

Well, if you don't set the rotation correct, it will go off in a different direction than from the intersection.

2 hours ago, Luckydel said:

Am I not getting them here?

That is just setting what direction it will fly off in. It does not set the position of the entity. And again, you need to set it to the player's x/y/z where the y represents the eye height as mentioned in the first post.

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

    • Back then there was a number which determined the tier of an item and block. If the block tier is lower or equal to the item number, the block would be mined. this however, has changed and now it goes by "needs_netherite_tool" which is fine, until you realized that some mods had items and blocks that exceeded these values. You can make you own "needs_mod_tool" but I feel that this is more limiting(and just more work) than before. So is there anyway to use something similar to the old tier system while also still being compatible with a lot of other mod tools?
    • Well, when I log in to the server, sometimes within an hour, sometimes within a minute, the server closes and informs me that there was a Ticking entity error. Below is the crash report
    • This forum is for Forge, not NeoForge. Please go to them for support.
    • Forge version: 55.0.0 Minecraft version: 1.21.5 Downloads: As this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes. Downloads page Intro: Good evening! Today, we have released our initial build of Forge 55.0 for Minecraft 1.21.5. 1.21.5 is the newest member of the 1.21 family of versions, which was released yesterday on March 25, 2025. As a reminder, the first minor (X.0) of a Forge version is a beta. Forge betas are marked as such on the bottom left of the title screen and are candidates for any breaking changes. Additionally, there are a couple of important things to note about this update, which I've made sure to mention in this post as well. Feel free to chat with us about bugs or these implementation changes on GitHub and in our Discord server. As always, we will continue to keep all versions of 1.21 and 1.20 in active support as covered by our tiered support policy. Cheers, happy modding, and good luck porting! Rendering Refactor For those who tuned in to Minecraft Live on March 22, 2025, you may already know that Mojang have announced their intention to bring their new Vibrant Visuals overhaul to Java in the future. They've taken the first steps toward this by refactoring how rendering pipelines and render types are handled internally. This has, in turn, made many of Forge's rendering APIs that have existed for years obsolete, as they (for the most part) can be done directly in vanilla. If there was a rendering API that was provided by Forge which you believe should be re-implemented, we're happy to discuss on GitHub through an issue or a pull request. Deprecation of weapon-like ToolActions In 1.21.5, Minecraft added new data components for defining the characteristics of weapons in data. This includes attack speed, block tags which define efficient blocks, and more. As such, we will begin marking our ToolActions solution for this as deprecated. ToolActions were originally added to address the problem of creating modded tools that needed to perform the same actions as vanilla tools. There are still a few tool actions that will continue to be used, such as the shears tool action for example. There are some existing Forge tool actions that are currently obsolete and have no effect given the way the new data components are implemented. We will continue to work on these deprecations and invite you to chat with us on GitHub or Discord if you have any questions.
  • Topics

×
×
  • Create New...

Important Information

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