It’s not possible to call a routine with the can_go property. Would this have an additional cost?
Oh, seems we’ve made a mistake there. Will be fixed in the next PunyInform version. Thanks!
I’m glad you’re fixing that. I recently used
cant_go in an Inform 6 port of a mainframe game as a way of dealing with all directions in a one-room maze with lots of conditions and random factors from all directions. I’d hate to have to repeat the code for every direction. Hmmm, maybe a subroutine would do the trick.
I’d probably put that in a before routine for the room(s) instead, although it should be possible to do it in a cant_go routine.
That’s an idea. I didn’t think of that. Thanks.