The sendPing function has been updated on the Production Servers, and the bug mentioned in this Suggestion has been resolved. As mentioned, that brought up a few other points of undesirable functionality. The Good News is we were able to include those enhancements. The sendPing API function option moveAll = True now moves all players, not just the GM, if they are all on page specified in the API call . When it is false, no players are moved, and all connected players see the ping. If no value is provided for moveAll, the default is a false value. The sendPing API can now ping the same location more than once in a row. The sendPing function only affects players on the Page specified in the script or the page where the ping originated, if a page is not specified. The sendPing now has a new option available, visibleTo , which can be used to specify which players are affected by the ping. Other players will not be moved or see the ping. If sending to a single player, you can include their player ID as a string or variable. If sending multiple IDs, they can be included either as an array, or as a comma-delimited text string. With the correction of the initial post as well as the subsequent requests, and because there is a new thread in the API form, I'll be closing this Suggestion as Complete. The visibleTo option will allow for the functionality to target the GM only, created by the long standing bug. However, we hope the added ability to target any player or group of players is even more helpful. Because this changes how some API scripts may currently be set up, a hotfix for APIs is scheduled to be deployed Friday morning, June 21, 2019. Please see the API forum thread for more detail. More documentation and an example script is posted to the API script wiki . Please report any issues with the sendPing update to the API forum thread .