You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a cross bow is loaded with a Explosive firework rocket the render of trajectory of it is infinite in distance.
Trajectory module doesn't respect the short distance due to explosion of fire work.
It would be better if it displayed the actual distance the firework rocket will travel.
Steps to reproduce
1. Get explosive firework rocket: /give @p firework_rocket[fireworks={flight_duration:1,explosions:[{shape:"large_ball",has_twinkle:0,has_trail:0,colors:[I;2437522],fade_colors:[I;14602026]}]}] 1 2. Activate Trajectories module and load the crossbow 3. Observe the rendering and remember 4. Fire the Crossbow
Meteor Version
dev_build (latest)
Minecraft Version
1.20.1
Operating System
Windows
Before submitting a bug report
This bug wasn't already reported (I have searched bug reports on GitHub).
This is a valid bug (I am able to reproduce this on the latest dev build).
The text was updated successfully, but these errors were encountered:
Describe the bug
When a cross bow is loaded with a Explosive firework rocket the render of trajectory of it is infinite in distance.
Trajectory module doesn't respect the short distance due to explosion of fire work.
It would be better if it displayed the actual distance the firework rocket will travel.
Steps to reproduce
1. Get explosive firework rocket: /give @p firework_rocket[fireworks={flight_duration:1,explosions:[{shape:"large_ball",has_twinkle:0,has_trail:0,colors:[I;2437522],fade_colors:[I;14602026]}]}] 1
2. Activate Trajectories module and load the crossbow
3. Observe the rendering and remember
4. Fire the Crossbow
Meteor Version
dev_build (latest)
Minecraft Version
1.20.1
Operating System
Windows
Before submitting a bug report
This bug wasn't already reported (I have searched bug reports on GitHub).
This is a valid bug (I am able to reproduce this on the latest dev build).
The text was updated successfully, but these errors were encountered: