Currently, KX_Scene.addObject takes three arguments:
- object (KX_GameObject or string) – The object to add
- other (KX_GameObject or string) – The object’s center to use when adding the object
- time (integer) – The lifetime of the added object, in frames. A time of 0 means the object will last forever.
Although other is only used as a positional argument (i.e., where the new object will be added) a Vector cannot be used.
The user must maintain a “spawn object” even if they intend to alter the new object’s location “manually” using Vectors.
Not allowing a Vector to be used as a positional argument seems rather counter-intuitive.
Allow Vectors to be passed in as the positional argument other.
Possibly, make other an optional argument. If no position is given, the new object will be added at the origin of the scene.
Eliminates the need to maintain a “spawn object” in your scenes.
Brings this method in line with the rest of the API, where KX_GameObjects and Vectors can occasionally be used interchangeably to describe positions (see KX_GameObject.rayCast)