Use one unique keyword per GlobalObject system
e.g. "farming" is a vanilla system keyword, "portal" is a modded system keyword.
This is referred as key in the code and below.
Use your own key in your mods.

see SGlobalObjectCreator.lua (top of the file) for interface or:

e.g. SMoatsGO.lua from Moats
e.g. SPortalCore.lua from Portal Gun
objectModDataKeys:[optional] list of parameter names to save over time.
Those are mostly the parameters passed through args in ShGO.createCGO and other client functions described below.
e.g. see Moats.modDataKeys from Moats

see CGlobalObjectCreator.lua (top of the file) for interface or:

e.g. CMoatsGO.lua from Moats
e.g. CPortalCore.lua from Portal Gun

Code below must be called during the game.
It requires init phases to be completed.
e.g. CPortalManager.lua from Portal Gun
Note: pos can be directly the IsoGridSquare instance.
Note: this is only for the initial object instance creation. At server restart (or game restart in solo) as well as when the associated square is re-loaded, creation is handled by the generic code. You have nothing to do. You can still receive the potential creation messages if you have specific code to do, see client events.

e.g. CPortalManager.lua from Portal Gun

Events subscription requires ShGO.initCGO(key) to have been called before.

New client event on specific Global Object creation.
Use event registration as usual:
luaObj:luaObject associated to the IsoObject
Very important: the IsoObject may not be loaded at this point, only the lua object.
All data that can be used while the object is not loaded must be in the luaObject.
To know if the IsoObject is loaded, you have to store the luaObject and poll by calling
Do this the less you can to maintain optimum cpu cost.

New client event on specific Global Object deletion:
Use event registration as usual:
luaObj: notice it is likely not valid anymore (because the IsoObject may already be removed or altered)

New Event can be used client side.
Use event registration as usual:
context: the usual context to add your option
isoObj: client side Global Object of type 'key' you clicked on
playerNum: local num of the clicking player
x: position on screen
y: position on screen
test: boolean, vanilla, not sure, you probably should not do anything when test is true

This is very advanced, do not bother with it until you are familiar with the points above.
Event subscription requires ShGO.initCGO(key) to have been called before.

New event can be used server side.
Use event registration as usual:
command: string (e.g. 'add_'..key)
playerObj: server side player obj related to the client initiating the command
args: client command arguments
result: depends on the command:

• add_-> nil if failed or created lua object if succeeded
  
• remove_-> lua object about to be removed from system.
  
• custom command -> nil

objectSystemInstance: the instance of the object system for ease of use. (you probably should neglect that, it seems broken I still do not know why)

e.g. SMoatsContinuity.lua from Moats.