I am running 0.3.9. I received this error message,
oddly enough while I didn't think the program was
running and must still have been running in the
background even after I selected "Log Out."
"Error 13 in mscorlib: The given path's format is not
supported.
Error occured in module Utility.vb on line 0
Error occured using character Enter the Kingdom:"
Immediately after clicking "OK" I received this error
message.
"Error 0 in :
Error occurred in module Login.vb on line 0
Error occurred using character Enter the Kingdom:
Error saved to file .\Errors\Login.txt"
I have attached the file referenced in this error
message. Note where it says "Invalid" above the login
form in the HTML contained in the file.
I reran the program afterwards to identify its process,
which was not running after I got the second error
message, so I'm presuming the program did actually
close after that.
Logged In: YES
user_id=448458
I think this is related to the error you posted earlier. When
you closed KoLmelion earlier, it probably didn't release memory
because something was running in the background, until this
point. It just looked like the current "incarnation" of
KoLmelion threw this error.
Your attached file is just the KoL login page... not exactly
sure how you got stuck there.
Logged In: YES
user_id=485454
I got the same error message again shortly after getting a
message saying that idling for more than 20 minutes or so
had caused my session to expire and that I needed to log out
and log in again. I would think that would be something that
could be automated, though, couldn't it?
Logged In: YES
user_id=485454
Sorry, forgot to mention a few specifics. I got the FIRST
error message I specified in the original bug report. I got
an additional error message immediately after, but it was
different from the second one I originally specified.
"Error 91 in KoLmelion: Object reference not set to an
instance of an object.
Error occurred in module CharSheet.vb on line 0
Error occurred using character Enter the Kingdom:"
Logged In: YES
user_id=448458
This should be fixed in 0.5.3. I'll leave it open just in case,
though.