QDK Weirdness
Dr.Froth
04 Jun 2006, 18:27
paul_one
05 Jun 2006, 07:40I've never heard of changing a later part of the game, effecting the earlier part...
If you could find something to reproduce it then that'd be helpful.
If you could find something to reproduce it then that'd be helpful.
James2
05 Jun 2006, 19:35I've had a slightly similar thing with quest, in that if an object name is repeated, by you creating a new object with the same name as an existing one (easly done in a large game) OR cloning an object, and not changing the name, then the new and old objects are visable in the interface but you can do diddly-squit with them.
paul_one
06 Jun 2006, 07:55That's understandable - as Quest/QDK get's confused over them both.. Two objects with the same name will ruin it - and in QDK I thought Alex had stopped this from happening - but perhaps not.
Arbutus
09 Jun 2006, 02:24QDK does not let you add a second object with the same name as another (not case sensitive); but you can create objects during the game with duplicate names. Then the disambiguation menu comes into use so make sure you use good 'alias' or 'details' properties. Script performed on an object will affect all objects with the same name. More testing could be done in this area or you could avoid the problem altogether.
Dr.Froth
09 Jun 2006, 17:30Thanks guys...I'll check it out.