Reply to Re: stuck in goblin village
If you don't have an account, just leave the password field blank.
Sounds like a problem with FreeDink rather than with the DMOD.
From your errorreport I think this is the problem:
The script r3-language.c is called when the screen is entered. Then the screen is still fading up, so FreeDink ignores the request of r3-language to fade down. Seemingly it ignores the rest of the script from there. Normally Dink doesn't ignore the fade down command when loading the screen.
So an errorreport for freedink it is then I suppose. I can't replicate it myself though as I don't have freedink.
If you just want to continue the DMOD you can edit the script in question. There should be this command:
Change the 1 to something larger, 1000 will probably do the trick:
This will make the game pause for a second, so don't move when you enter the screen!
From your errorreport I think this is the problem:
The script r3-language.c is called when the screen is entered. Then the screen is still fading up, so FreeDink ignores the request of r3-language to fade down. Seemingly it ignores the rest of the script from there. Normally Dink doesn't ignore the fade down command when loading the screen.
So an errorreport for freedink it is then I suppose. I can't replicate it myself though as I don't have freedink.
If you just want to continue the DMOD you can edit the script in question. There should be this command:
wait(1);
Change the 1 to something larger, 1000 will probably do the trick:
wait(1000);
This will make the game pause for a second, so don't move when you enter the screen!
