Not right now, I just changed the source code so that it just completely ignores any connection errors, rather dirty solution but at least I've got over 200 SRs without any crashes, I couldn't get more than 10-15 before.
What I know is that the crashes always happened when the bot checked if the dialog is still running, so basically somewhere in here:
Code:
case (int)srbotStates.testdialog2:
Report("Test if dialog has finished");
waitTaskbool = Program.helper.memoryinrange(dialogOff, dialogOut, 0x01);
if (await waitTaskbool)
{
attempts = 0;
botState = (int)srbotStates.readparty;
}
else if (Program.helper.lastRead == 0x0F || Program.helper.lastRead == 0x03)
{
attempts = 0;
botState = (int)srbotStates.exitdialog;
}
else if (Program.helper.lastRead == 0x11)
{
attempts = 0;
botState = (int)srbotStates.nickname;
}
else
{
attempts++;
botresult = 3;
botState = (int)srbotStates.continuedialog;
}
break;
What I said before about it always crashing at a specific part of the dialog was wrong though, it just always happens sometime during the dialog.
I don't really understand how you determine wether a dialog is still active or not so I don't know what the problem is, but I do guess that it has something to do with the fact that the dialog when receiving Type:Null is very long compared to the dialog for an event Pokemon.
@
BigOnYa:
