Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002042Core InformUnderstandingpublic2017-12-01 17:132018-01-16 10:32
Assigned To 
PlatformOSOS Version
Product Version6M62 
Target VersionFixed in Version 
Summary0002042: Can't use parsed value in when clause for understand as a thing.
DescriptionIn the example below, the condition in the when clause gets executed before the number is parsed, causing it to incorrectly use the value parsed from the previous successfully parsed command, if any.
Minimal Source Text To Reproduce
There is a room.

Understand "meaning of [number]" as a thing when the number understood is 42.

Test me with "x meaning of 42 / trace 42 / x meaning of 5".
TagsNo tags attached.
Effect(serious/mild) Game compiles but misbehaves
Attached Files

- Relationships

-  Notes
rockwalrus (reporter)
2018-01-16 10:32

Looks like this is a documented limitation, but the misbehavior is surprising. An error (or doing the expected behavior) would be better.

I was implementing a different way of referring to things, so the documented recommendation of having the understand match everything and then using a check rule for every action wasn't really a good option.

I'm happy enough with the I6 code I wrote to workaround this bug and a limitation of ParseNumber ( [^]), but it's theoretically possible I could have done both things with the "reading a command" activity, so the documentation should mention that as another alternative. I still don't think that check rules and the "reading a command" activity together cover all the usages that being able to actually use parsed values in the when clause would.

- Issue History
Date Modified Username Field Change
2017-12-01 17:13 rockwalrus New Issue
2018-01-16 10:32 rockwalrus Note Added: 0004762

Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker