Suggestion
When using Skbee’s raytrace expression, I constantly find myself having to look back at the docs to figure out where what needs to go. It’s also sort of annoying to follow what's happening when using the expression. I think a section for raytrace could be a good idea, ex:
Something like set {_ray} to raytrace from {_player} with max distance 1 with ray size 1 while ignoring passable blocks while only allowing entities becomes
set {_ray} to raytrace from {_player}:
range: 1
size: 1
ignore passable blocks
only allow blocksI’m not sure if it really needs a section, but it is better than the current syntax imo.
Could also maybe provide parse tags for block or entity raytracing?
Maybe add parse tags for entity raytrace and block raytrace?
like [:entity|:block] [ray[}trace] [from] %entity|location%: or however the syntax is defined in skript.
Additional Information
No response
Suggestion
When using Skbee’s raytrace expression, I constantly find myself having to look back at the docs to figure out where what needs to go. It’s also sort of annoying to follow what's happening when using the expression. I think a section for raytrace could be a good idea, ex:
Something like
set {_ray} to raytrace from {_player} with max distance 1 with ray size 1 while ignoring passable blocks while only allowing entitiesbecomesset {_ray} to raytrace from {_player}: range: 1 size: 1 ignore passable blocks only allow blocksI’m not sure if it really needs a section, but it is better than the current syntax imo.
Could also maybe provide parse tags for block or entity raytracing?
Maybe add parse tags for entity raytrace and block raytrace?
like
[:entity|:block] [ray[}trace] [from] %entity|location%:or however the syntax is defined in skript.Additional Information
No response