-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Counting flowers #2249
Counting flowers #2249
Conversation
213514f
to
e06f586
Compare
In order to provide useful playtesting feedback, I have not inspected the yaml file for the counting flowers scenario. I haven't solved it yet, but here's what I've tried so far:
My main idea would have been to |
e06f586
to
471326f
Compare
@kostmo Oh, sorry, this PR is not ready for review yet! It is unsolvable since there is still more stuff I need to add. I'll let you know when it's ready for you to give it a try. |
Oh, hmm, I will have to think how to rule out this unintended solution. 😄 |
025a594
to
ae158dd
Compare
@kostmo OK, this should be ready for test playing! There's still one more thing I want to iron out but it's only cosmetic. |
ae158dd
to
b438bab
Compare
b438bab
to
4ba94fc
Compare
4ba94fc
to
9ad1c26
Compare
9ad1c26
to
8ec7048
Compare
This is now all rebased and fixed up on top of the changes in #2245, should be ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's my solution. I enjoyed having the fuse as time pressure.
def forever = \c. c; forever c end | ||
|
||
def judge = | ||
numFlowers <- resonate "flower" ((-59,-19),(60,20)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a (off-by-one) bug in my code that I finally diagnosed by entering creative
mode to use my own resonate
command. Perhaps that is the intended use of creative
mode, but it may be fun to have an "in-scenario" method to double-check one's count. Perhaps some oblique way to obtain a gradiator
that is an instant-lose condition, but nonetheless can help a player debug.
As I was trying to solve #2249, I was rather confused after trying to `meet` a built robot and `give` them an item, but the item was not delivered. It turns out that I had been `meet`-ing the `judge` robot instead. We should distinguish between robots that are intended to be interactive or not, and only allow `meet`-ing an interactive robot.
Another challenge scenario to showcase the use of
print
/read
.