muczachan
Member
This got lost somehow, so here I go again:
Current way of handling fortune cookie expiration is to abort execution and inform user that Fortune Cookie counter expired.
I think this lacks the main point of interest for the user, mainly: where not to adventure right now -- because you can not get the same semi rare twice in a row. This information can be easily reached by using "counters" command, but I do not think this should be really necessary.
Attached is a patch that adds the previous semi-rare location to CLI message about Fortune Cookie counter expiration.
Current way of handling fortune cookie expiration is to abort execution and inform user that Fortune Cookie counter expired.
I think this lacks the main point of interest for the user, mainly: where not to adventure right now -- because you can not get the same semi rare twice in a row. This information can be easily reached by using "counters" command, but I do not think this should be really necessary.
Attached is a patch that adds the previous semi-rare location to CLI message about Fortune Cookie counter expiration.