Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Raycast always acts as if command_along_ray_only_on_hit is true #410

Closed
muon-rw opened this issue Jan 19, 2024 · 0 comments
Closed

Raycast always acts as if command_along_ray_only_on_hit is true #410

muon-rw opened this issue Jan 19, 2024 · 0 comments
Labels
bug

Comments

@muon-rw
Copy link

muon-rw commented Jan 19, 2024

Whether command_along_ray_only_on_hit is set to true or false, the command_along_ray will only ever execute if the raycast hits a target.

Using origins-forge-1.20.1-1.10.0.5
@muon-rw muon-rw changed the title Raycast's command_along_ray_only_on_hit nonfunctional Raycast always acts as if command_along_ray_only_on_hit is true Mar 6, 2024
MerchantPug added a commit to EdwinMindcraft/apoli that referenced this issue Mar 13, 2024
@MerchantPug
Apoli: Fix EdwinMindcraft/origins-architectury#410
22e30b9
MerchantPug added a commit to EdwinMindcraft/apoli that referenced this issue Mar 13, 2024
@MerchantPug
Apoli: Fix EdwinMindcraft/origins-architectury#410
9fe9526
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MerchantPug @muon-rw