improved nodes

there are two nodes that come to question I think it will be really use for an addition like this to them node Contact if it could output more data of the contact that happened will be really useful

we have a go to location node that regardless of the object rotation wicks a point on the nave mesh and translate your obj to that position it aloes gives you a speed and turning property to modify it doesn't work with obj that are not using the navmesh a new node for go to location that can
be used with dynamic objects and non dynamic outside of the nevmesh system like so or a bool you can check off in the go to location node

current method for go to in armory

the ray cast can be tweak a bit to be used as a sensor instead of using trigger boxes the ray cast can be rework to accommodate this need

"Xray" is a bool that if checked will allow the ray to go through any other objects that don't have the property you are looking for until it hits the one with the assign property
"property" is an input that can be assign to look for a specific property on an object your ray is hitting and if it has it it will output the node

"local" is a bool that if checked it will use the input "Distance" and multiply the to vector by the object transform and add to the object location so if the ray caster Obj moves the ray cast will be relative to the objects movement

current method for raycast from Object out in armory

No files or tests are named. Start by locating the existing Contact, Go to Location, and Ray Cast node implementations and documenting their current inputs and outputs; done would require an agreed, testable design for contact data, non-navmesh movement, and filtered or local ray casting.

Written by the indexing model from the issue text.