Sliptip on 23/4/2013 at 11:27
I've got this bug going on and it's driving me nuts because I just can't seem to track it down. Every so often an object is created at 0,0,0 (I realize that's normal), but I can't figure out what's calling it into existance :confused:
Is there a way to determine (through monolog perhaps) what object created another object? I don't see that info in monolog but maybe I'm missing something.
LarryG on 23/4/2013 at 13:28
Periodically I go to 0,0,0 and remove stuff that has showed up there. I was under the impression that this is a normal result of DromEding, so a regular dusting of the corners is called for. This has been happening to my missions for years.
There is also the possibility that using NVItemGiver with NVItemGiverOn="Destroy" may have the unintended consequence of creating stuff when the host object is destroyed in edit mode. Scripts may trigger in the editor. I think NV once said that he didn't think any of them cared what mode they're in, they just listen to messages. If those messages are generated in editor mode, then...
Sliptip on 23/4/2013 at 13:36
Thanks Larry,
I'd say something like the latter is probably what's happening here. It's one of the newer adds to the object heirarchy, but it has a relatively low object #.
So what I'm guessing is that somewhere along the line I created something that specifically calls the object number, but then years later I deleted the object that is being called, and created a new item that took it's number.
But I've been all over the gamsys file - I just can't figure out what's calling it. I wouldn't mind so much, but it's a piece of text that automatically displays an creation, so even if I move the entire mission, it'll still be a nuisance - plus I don't like loose ends or Dromed doing extra work it shouldn't be doing!
