Reply to Re: File bugs so far.
If you don't have an account, just leave the password field blank.
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)
