-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRASH ON $start A #34
Comments
You will need to add dfrotz not to the games folder but to your path. I've assumed that you're using Windows because that screenshot looks like the Windows file explorer, but please correct me if otherwise. In general, you should follow these steps:
Of course, replacing Please let me know if those instructions are useful. |
Can you try running the game in the terminal using dfrotz directly? IE.
And let me know if that runs as expected? |
Per discussion on Discord, this looks like an actual bug with the bot, which I'll try to address. The game in question seems to be
On a Windows machine. |
Experiencing same issue. dfrotz is installed normally, can be used to play the game from any location. Running Raspbian (Debian variant). All packages reinstalled and updated with npm wherever possible. |
I've created #39 as a direct copy of your comment, @KawaiiFiveO , just so I can keep the two discussions separate. If it turns out they are related, then I'll update this issue with the findings. |
The bot has been updated to a new framework, so this bug might be solved, but since I couldn't reproduce it, I'll leave it open for a bit. |
crash on game load and yes i got dfrotz.exe but where do i place it in what path and who to get a .z5 game to run
Loaded Game: A
events.js:183
throw er; // Unhandled 'error' event
^
Error: spawn dfrotz ENOENT
at _errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
The text was updated successfully, but these errors were encountered: