tag:blogger.com,1999:blog-6672290740704164025.post2977137990693512955..comments2023-05-10T01:06:42.623-07:00Comments on PyramidIF: Instead of Instead (Inform 7)Hanonhttp://www.blogger.com/profile/14545045515532487079noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6672290740704164025.post-56075625226801142482016-12-14T05:54:08.173-08:002016-12-14T05:54:08.173-08:00Thanks for the correction (and sorry I missed this...Thanks for the correction (and sorry I missed this reply for so long), your advice is very sound. Pure INSTEAD rules do have a place but it is very easy for beginners (myself included) to overuse them and end up doing more coding than is required when the action-processing rules are there to help authors along.Hanonhttps://www.blogger.com/profile/14545045515532487079noreply@blogger.comtag:blogger.com,1999:blog-6672290740704164025.post-77851900648287811042016-07-28T13:22:40.786-07:002016-07-28T13:22:40.786-07:00This is an excellent explanation
BUT
every time ...This is an excellent explanation<br /><br />BUT<br /><br />every time you say "bypassing the parser" I think it should be "bypassing action-processing" or something like that. By the time all this stuff is happening, the parser has done the work of converting a command into an action. It's the general behavior of the action that's getting short-circuited. <br /><br />There's basically two things that I've found "Instead" rules useful for. One is redirecting actions completely--things like "Instead of pushing the button, try switching the kettle on." Another is when I have to do something pretty complicated that involves printing text and carrying out effects, and they can't easily be broken up into different rules (for instance, if the action changes the printed name of the noun and you need to refer to the old name). But looking at my code most of the "Instead" rules are just things I coded in a hurry.Matt Weinerhttps://www.blogger.com/profile/15731711604182232484noreply@blogger.com