intfiction.org

The bug fix is out; you will see it if you look at your App Store updates.

If you downloaded the thing in the first place, I mean.

UnwashedMass, if you still see the input bug after the update, try restarting. That is, typing "restart" in the game, not force-quitting.

A fire was lit under me! Hilariously, the first time I attempted to restart, it was auto-corrected to "restate". Then, with the mistake drilled in, I figured it would let me... and my second restart was corrected to "redraft".

OK, third time's the charm, restart achieved. Direction letters and i for inventory just return blank output in response without moving me from the starting location. But holding my nose and keying in "go e" from the starting location, direction initials seem to work everywhere else, only giving me the "I only understand you as far as wanting to n" error in places where N is not a valid direction ... which isn't the /most/ helpful error message for that particular mistake, but a big step up! (Correction: sometimes the single letters work, sometimes they don't, in some locations, according to no particularly perceivable rhyme or reason. Rigorous testing done here! At least i finally is returning useful output once there is something IN the inventory.)

So, hm, not perfect, but definitely /changed/.

Yeah, this really does not make any sense at all. My handywavy theory was that garbage was being appended to the input buffer. That does not appear to be the case.

If you are okay with deleting the app and reinstalling it (and losing all your saved games), that would be another thing to try. But it will probably just confirm that there's still a bug in there. (I'd do it, but I have a pile of test devices and I only care about the saves on one of them.)

Are your language or keyboard settings set to something I might not have encountered? I have not tested it with non-US keyboard layouts, for example.

My settings should be Canada standard; the iPod is quite old however. I will try your radical solution when I can -- I seem to have inadvertently bricked my device while trying to remove the game and put it back on.

OK, restored the app to its native state, which appeared to wipe all the apps, reinstalled the Dreamhold, the game resumed from my last position... I deleted it, re-reinstalled it -- got a clean start!

Okay, thanks.

I now have one other person reporting this -- also on an iPod 2nd-gen with iOS 4.2. (That's what you've got, I think?) Unfortunately, I *also* have one of these, and the problem does not seem to appear.

I'll keep looking at it.

I have the same iPod model (running 5.x), and definitely don't see this.

_________________
Glimmr: Advanced Graphics for I7
blog | download | bug-tracker

The 2nd-gen iPod tops out at iOS 4.2.1, so you have the next model. :)

Model "MB533C", iOS 4.2.1 indeedy.

Huh, now I feel silly. This thing is 3rd-gen after all. I never looked up the model number before.

Not that this helps track down the bug. But I may try snarfing a 2nd-gen off the Internet just to have another test platform.