Add new function testSphereAgainstWorld (Close #646)

[FileEX]

This PR adds a new function testSphereAgainstWorld, which allows checking if there are any obstacles within a given radius.

Syntax

bool hit, element hitElement, int modelID, float elementPositionX, float elementPositionY, float elementPositionZ, float elementRotationX, float elementRotationY, float elementRotationZ, int lodID, string type = testSphereAgainstWorld(float x, float y, float z, float radius [, element ignoredElement = nil, bool checkBuildings = true, checkVehicles = true, checkPeds = true, checkObjects = true, checkDummies = true, ignoreSomeObjectsForCamera = false ] )

hit - Indicates whether a collision was detected.
hitElement - The element that was detected. If it wasn't created in MTA, it will be nil.
elementPositionX, elementPositionY, elementPositionZ - World position of the detected element
elementRotationX, elementRotationY, elementRotationZ - World rotation of the element
modelID - The ID of the element.
lodID - The ID of the element's LOD (or 0).
entityType - The type of the element (building, vehicle, ped, object, dummy)

The modelID, lodID, and entityType parameters are returned even if hitElement is nil.

Closes #646

[Einheit-101]

Would it be possible to return the XYZ where the hit got detected?

[FileEX]

Would it be possible to return the XYZ where the hit got detected?

Yes, I'll add it tomorrow

[CrosRoad95]

make 7 arguments in total: from, to, options "processLineOfSight" already has shown that using function with extensive amount of arguments is problematic, prune to errors, hard to extend.
Same with return value

[FileEX]

Personally, I don’t see anything difficult in using functions like processLineOfSight, which return multiple values. You just need to familiarize yourself with the syntax and the example on the wiki. It doesn't cause any problems, errors, huge and difficult bugs, or any other made-up issues

[Nico8340]

If you solve TheNormalnij's request, then everything's fine