rexxar said: ↑ In order to balance this and prevent server-ending abuse, the camera has a cooldown. Currently it's distance/2ms. That means you can do a 30m scan every tick, or one 2km scan every second. IMyCameraBlock has properties that tell you how long the current cooldown is, and if there is an active cooldown. Click to expand...

Syncaidius said: ↑ used to kill server performance should definitely be removed or implemented in a non-exploitable way Click to expand...

Is there an upper limit to the scan distance? If not, there probably should be, otherwise a grind-weld arrangement could bypass the cooldown for very long scans.Alternately, rather than a cooldown you could have it "charge up" instead. In other words, you would keep some maximum distance that the call would accept, and that value would increase by 30m every tick and decrease whenever a call is made (by the distance requested). This prevents the grind-weld exploit because they'd always start from 0 on weld.Also, can we get the actual intersection point of the raycast? I'm thinking about planets, where presumably the returned struct only gives us the center of the planet, which isn't very useful. If we could get the contact point, then the method could be used for height-above-ground among other things.Oh, and (sorry this is turning into a long list) it would be nice if the cooldown scaled with the maximum speed limit. With the default 100m/s speedlimit, a 2km detection gives you at worst 10sec to respond so a 1sec cooldown is plenty of time. But if someone is using a 1000m/s speedlimit mod, at 2km you may only have 1 sec to respond, so by the time you've detected something it's likely already too late to do anything about it.While I don't disagree in principle, I don't think using up valuable dev time for this reason alone is worth it. The reason is that there are simple exploits that can destroy a server's performance using nothing but basic C# and not even touching any API created by the devs. A malicious person can use these (unfixable exploits) as well as anything provided by the dev's, so removing an alternative doesn't gain you much in this respect.On the other hand, the reason I agree with removing GetFreeDestination is that it is a serious gameplay exploit. So removing it does gain you a lot in terms of gameplay improvement.