Quote:
Originally Posted by kolton1
Are you absolutely sure the window wasn't frozen? I can tell d3stroy3r to increase the timer before d2bot closes it. It already waits like 10 seconds before closing due to unresponsiveness.
NIP checker is a complex script so it'll take some time to port it.
Merc stomp issue was mentioned on one of previous pages, add this to your character config:
Congig.TeleStomp = true;
|
added the telestomp thx
and yeah about the freeze yes im absolutely sure
and it cant be possible that i have like every ~2 runs a restart
edit
btw just saw another restart
bot was teleing to cs almost there
bam window close (displayed the standard d2 unhandeld exception error for a sec)
edit so far the crashes
it happens mostly only in a script
[19:31:47] <PalaTwo> Window is not responding... restarting profile
[19:33:12] <PalaOne> Window has unexpectedly exited... restarting profile
[19:40:29] <Sorc> Window is not responding... restarting profile
[19:44:38] <PalaOne> Window is not responding... restarting profile
[20:33:21] <PalaOne> Window is not responding... restarting profile
[20:33:24] <Sorc> Window is not responding... restarting profile
[19:56:13] <PalaOne> Window has unexpectedly exited... restarting profile
[20:59:17] <Sorc> Window is not responding... restarting profile
[21:14:06] <PalaTwo> Window has unexpectedly exited... restarting profile
[21:20:18] <PalaTwo> Window is not responding... restarting profile
[21:21:22] <PalaOne> Window is not responding... restarting profile