File bugs so far.
Lost Shoes (The)
Warning: MASSIVE SPOILER, but you probably will read this anyway.
I played through to the point where you get the shoes back to the man and right after Dink kills him and has three pairs of shoes, the controls lock up, the screen lock stays, and when I went to my System Monitor to kill the process (the last resort to turn off a program) I got the "'dink' not found" message. And this is with the freedink version that got rid of that problem for the others. Is this just another scripting error?
I played through to the point where you get the shoes back to the man and right after Dink kills him and has three pairs of shoes, the controls lock up, the screen lock stays, and when I went to my System Monitor to kill the process (the last resort to turn off a program) I got the "'dink' not found" message. And this is with the freedink version that got rid of that problem for the others. Is this just another scripting error?
I think the Freedink bug was that certain scripts caused the engine to crash, and when Freedink crashes the frontend doesn't know if it crashed or can't be found, hence the error.
The newest Freedink probably fixed the bug that caused it to crash in the first place, but they probably didn't fix the frontend glitch. Fredink shouldn't crash so often anymore, but the frontend still can't tell the difference between crashing and not finding.
Summary:
It says "Dink not found" because you forced it to quit, this is a problem with the frontend. Freedink probably froze due to a scripting error, not an error in Freedink.
Solution:
Have you tried ALT+Q (I don't know if this still works in Freedink btu it's worth a try)
The newest Freedink probably fixed the bug that caused it to crash in the first place, but they probably didn't fix the frontend glitch. Fredink shouldn't crash so often anymore, but the frontend still can't tell the difference between crashing and not finding.
Summary:
It says "Dink not found" because you forced it to quit, this is a problem with the frontend. Freedink probably froze due to a scripting error, not an error in Freedink.
Solution:
Have you tried ALT+Q (I don't know if this still works in Freedink btu it's worth a try)
I just kill process out of habit whenever anything freezes up.
Someone should either examine the code or coontact the author and tell him to examine it and tell him fix it.
I got this too, but with Dink 1.08. It's probably just the end of the D-Mod, shoddily scripted.
