err, my mistake, 'list' Attributes don't use a 'key' field, so you only need to look for your 'dictionary' Attributes
-----------------
here's the (syntax) documentation for 'dictionary' Attributes:
http://docs.textadventures.co.uk/quest/ ... aries.htmland specifically for your troubleshooting needs (if the code error exists within the 'dictionary' Attribute itself):
http://docs.textadventures.co.uk/quest/ ... onary.html (String Dictionary Attribute)
http://docs.textadventures.co.uk/quest/ ... onary.html (Object Dictionary Attribute)
http://docs.textadventures.co.uk/quest/ ... onary.html (Script Dictionary Attribute)
-------------
for example of a possible cause of the error:
(quest is case sensitive)
say she has an Object named (ID'ed) as:
Key1
in code:
<object name="Key1">
// blah Attributes
</object>
but in her Object Dictionary Attribute, named 'key_dict', she accidentally names her 'key' Object as:
key1 // which is NOT the same as: Key1
in code:
<object name="Key1">
// blah Attributes
</object>
<object name="Key2">
// blah Attributes
</object>
<object name="Key3">
// blah Attributes
</object>
<attr name="key_dict" type="stringdictionary">
<item>
<key>key1</key>
<value>1</value>
</item>
<item>
<key>Key2</key>
<value>2</value>
</item>
<item>
<key>Key3</key>
<value>3</value>
</item>
</attr>
so quest tries to find an Object named 'key1', but no such Object exists for it to use with the Object Dictionary operations she using/doing, so you get the errors seen, quest is throwing all the underlying code errors in trying to handle an Object Dictionary, with an incorrect 'key' field input, as that 'key1' Object input doesn't exist, so quest can't handle an unexisting Object with its Object Dictionary and thus any operations that use that item in the Object Dictionary.