NetHack 3.6.7 r1 and r2 can't find NetHack folder on flashcart. r0 works fine.

[signer-ink-beast]

I was upgrading my installation of NetHack DS to the latest 3.6.7 version, since I was missing some files (probably due to file corruption; that has since been rectified).

I run NetHack DS via my Ace3DS+ X flashcard launched directly from my 3DS home menu, with Twilight Menu installed and used as my primary kernel (autoboots Twilight Menu). It uses my flashcard kernel for homebrew. It auto patches dldi drivers with no problems with every release up to and including 3.6.7 r0. It still seems to patch just fine with r1 and r2, but it cannot find my data folder regardless of where it is located (of the 4 locations).

Just to make sure, I tried patching r2 manually on my computer, and disabled firmware auto-patching. Patched successfully. Same behavior: can't find NetHack folder.

I know you said there will be no more work done on this version of the game. Wanted to report this anyway in case anyone wanted to fix this. Thank you for your work! Being able to play NetHack away from a computer without a keyboard, and on the DS, is awesome.

[signer-ink-beast]

hi bro, to fix your trouble try this fix, i see it in another issue, Removed Link password: changeme when you installing it, you need to place a check in install to path and select usx

I reported the user profile to GitHub. I suspect that encrypted rar contains a virus or malware.

OG comment is still up at the time I write this, with the original link. Quote replying so message contents aren't lost (minus the original MediaFire link).

Uh, I was about to post this, and another bot is doing the same thing. Sigh What the actual eff. That is annoying.

I haven't reported that one yet, and don't have time to, but I've linked this issue in my other report already, so uh... that sucks.

[fancypantalons]

Just noticed this. The comments are deleted and I've also reported the behaviour.

Getting back to your comment, so it was working in r0 and broke starting in r1? Interesting.

I can certainly take a look at the code in the next couple days and see if any obvious bugs jump out. Clearly something broke if it worked before, so we can safely assume it can also be fixed presuming I can figure out what's going on...