ok that's good, because I have a game concept based on an unfinished book that would require more than one physics object. It would require "duplication" of a really nice flight physics law. Heres the back story so far:
In the year 2049, an 8 year old kid named Colin gets these things called "Arm Pax" for his 9th b-day, and so he decides to try them out in the middle of the night (even though his mom said not to), and as he progresses though the years, he gets better and better. But, he also has a few enemies...
So basically what i'm saying is the script needs to simulate jet-pack behavior (even though the things go on his arms
).
the reason why I need
MULTIPLE physics objects is because the enemies have similar devices, so they need to be able to fly too
. I was thinking about making a HUGE movement path for the enemies, but then they would be too predictable and boring.