I do not understand exactly what you mean by “links between objects”, but
there are boxes that upon collision with the warrior, they spawn a skeleton. They do this with logic bricks, like this:
Collision with (warrior property) -------> AND -----------------> Edit Object / Add Object creature.002
(where creature.002 is the skeleton).
If it is any help, In the previous (crashing) version Linux 2.78 64 bit, I tried numerous things =
Changed the above spawning logic brick with Python code (ie the collision called a script which called addObject). ----> crash
Deleted the armature from the creature —> worked
Spawned the armature along with the creature but not connected anymore, like two different objects (with two add object bricks) —> crash.
Eventually deleted everything and spawned only the armature —> still crash
Created a new armature with just one bone and spawned only that —> EDIT = still crash, but not the 4-th time. MOre spawns were required, but still crash.
Spawned the creature (without the original armature, that was deleted) along with the new bone armature --> EDIT = still crash, but also not the 4-th time, but more spawns were required. But still crash.
So there was something wrong with the specific armature and generally with spawning an armature
again and again. The original armature was rather default, had not changed much in it.
However the bones had restrictions “copy rotation” from some cubes, which I rotate with Python
(this is a trick I use because you can not directly rotate bones of an armature with Python, AFAIK)
However in some tests I disabled and even deleted the restrictions, and it still crashed.
PS: In all cases, the crash was at the addObject call, either logic brick or Python code. I printed
a message before the addObject (it appeared always), and printed a message after (never saw it).