We discovered when working in class the other day that queries were becoming too long, and were getting cut off in process, causing errors. Because of this, we switched to using queries at a depth of 1. This has, however, wreaked havoc in the print code, because it can't see the attributes it needs to use to describe the object, and therefore doesn't think they exist. Thus, we are currently getting very lackluster item descriptions like 'A chair.' and 'A table.'
Presumably, fixing this shouldn't be too hard - we had to get around the same problem when working with other nodes, as I recall. However I have forgotten what we did to make it work, and wasn't able to immediately fix the issue. If anyone knows the fix, it would be welcome.
We discovered when working in class the other day that queries were becoming too long, and were getting cut off in process, causing errors. Because of this, we switched to using queries at a depth of 1. This has, however, wreaked havoc in the print code, because it can't see the attributes it needs to use to describe the object, and therefore doesn't think they exist. Thus, we are currently getting very lackluster item descriptions like 'A chair.' and 'A table.' Presumably, fixing this shouldn't be too hard - we had to get around the same problem when working with other nodes, as I recall. However I have forgotten what we did to make it work, and wasn't able to immediately fix the issue. If anyone knows the fix, it would be welcome.