Feature adventure() should (optionally) respect fortune cookie timers

I only recently discovered that adventure() will plow through fortune cookie timers, unlike adventuring from the Main Interface.

Is there a good reason for this? If not, it ought to change, for two reasons: (1) My assumption was that the behavior of adventure() would match the Main Interface's behavior - and I think this would be a reasonable assumption on anyone's part. So this difference doesn't make any sense. (2) adventure() would be more useful if it behaved this way.

Maybe adventure(int, location) can respect fortune cookie counters automatically, or maybe there's a new adventure(int, location, boolean) that sets the behavior.

Discuss?
 
You can already control this using a counter script set to abort on fortune cookie timers or anything else you want.

I say it should stay as it is. The functionality you want exists already.
 
Back
Top