Folk ARPS

Initial assessment: no change
Documentation: no change

I am considering whether or not to drop this component, now that we have the Mission Observers component. If the mission-maker fails to disable this component after use, it's possible for every player in a session to suddenly find themselves with magical teleportation powers mid-mission.

We've had reports of the mission maker teleport being a bit buggy anyway. Maybe consider a rewrite/debug?

fer wrote:I am considering whether or not to drop this component, now that we have the Mission Observers component. If the mission-maker fails to disable this component after use, it's possible for every player in a session to suddenly find themselves with magical teleportation powers mid-mission.

As a mission maker I find this component an important time-saver, and useful for quick debugging in ways the mission observers component cannot do.

Perhaps it would be possible for it be only active where (isServer == true) by default. That way it could still be used in the editor, but won't be active when published as a .pbo and run on the Folk-ARPS server.

We could tie it in with the Debug Mode, maybe even remove the action and just have the player unit teleport on map(double)click straightaway.

It's supposed to be already tied to the debug mode, iirc? Although that's bugged for sure.
Also, as it was (unless it's been fixed in 2-7-1, there was no OnMapSingleClick "", so once you had activated the action, you would teleport everytime you'd click on the map.
Kale's idea of tying it to the server only sounds good (although it might still be problematic in the case of non-dedicated servers. Remember, we're not the only users of the framework! Still, it's a good new layer of security.).

This is now altered so it must be enabled in the INIT file and Debug Mode must be enabled for the action to be available. A better long-term solution is on the cards, I'm sure.