Marc-Alexandre Côté

This issue is now resolved in pyparsing 3.0.3. That should probably be reflected in the requirements of `pydot`.

@mhauskn this PR is really messed at the moment. I'm going to clean it up, but I wanted you to have an update on the fix. I now believe after...

My bad. I pushed the missing file. That will enable computing the md5 hash for a game state directly in C instead of having to get the state from Python,...

Oh, I should have mentioned I have yet to test the valid_action code. I was focusing on making sure the commands from the walkthroughs appropriately trigger `world_changed`. Also, I was...

@mhauskn I'm back working on it. I've done the initial validation for a few more games. Also, I've left a couple of comments (see above) to show some bug fixes...

> However, I'm detecting some issues with Zork1's walkthrough: > > * Step 162. NoWorldChange gold_act: Press yellow button, obs: Click. > * Step 165. NoWorldChange gold_act: Turn bolt with...

I finally have some time now to tidy it up. One thing that is still missing is to check whether no-op action (e.g., inventory, examine obj, look) doesn't change the...

@mhauskn what should we do with timers? For instance, in curses.z5, there seems to be a timer of 5 steps on 'antiquated wireless' before the radio plays random music. Should...

You made very good points. I agree with the overall rationale behind `clean=True`. Something we can do actually is instead of zeroing out the properties, we can first check their...

You are right. It doesn't impact the story progression. I actually had to zero a bunch of internal counters! But I manage to go through curses.z5. I'll go over the...