dcOnEmpty

[Nicodareus]

Code: Select all

getAuto White Potion {
	minAmount 0
	maxAmount 30
	passive 0
	dcOnEmpty 1
}

Does it not work properly with <relogAfterStorage 1>?
I woke up to my rogue having lost all exp cause it kept repeatedly dying from not having a way to heal itself, but it was supposed to disconnect when out of white potions..

[Cozzie]

Sounds like a bug. Moved over to bug report.

[SkylorD]

Code: Select all

getAuto White Potion {
	minAmount 0
	maxAmount 30
	passive 0
	dcOnEmpty 1
}

Does it not work properly with <relogAfterStorage 1>?
I woke up to my rogue having lost all exp cause it kept repeatedly dying from not having a way to heal itself, but it was supposed to disconnect when out of white potions..

He relogs, but doesn't quit.
In other words, When your item->storage is doesn't exists, your bot relog and after 5 second (default), he is on again and calculate route to your lockMap.

[Nicodareus]

Yeah i just took out the relog after storage. The documentation said it was there to work around a storage bug, but i haven't noticed anything bad without it.

[SkylorD]

Yeah i just took out the relog after storage. The documentation said it was there to work around a storage bug, but i haven't noticed anything bad without it.

I think about this bug, and i see this :

if (!$config{relogAfterStorage} && $args->{retry} >= 3 && !$args->{warned}) {
# We tried 3 times to get the item and failed.
# There is a weird server bug which causes this to happen,
# but I can't reproduce it. This can be worked around by
# relogging in after autostorage.
warning T("Kore tried to get an item from storage 3 times, but failed.\n" .
"This problem could be caused by a server bug.\n" .
"To work around this problem, set 'relogAfterStorage' to 1, and relogin.\n");
$args->{warned} = 1;
}

Is because this you not have noticed.
Don't happen this with you (The kore will try storage the item, if the item is failed, its not stored, the kore will stop.


Nhaauum.

[Cozzie]

Yeah i just took out the relog after storage. The documentation said it was there to work around a storage bug, but i haven't noticed anything bad without it.

I Think which about this bug, is refer to this :

if (!$config{relogAfterStorage} && $args->{retry} >= 3 && !$args->{warned}) {
# We tried 3 times to get the item and failed.
# There is a weird server bug which causes this to happen,
# but I can't reproduce it. This can be worked around by
# relogging in after autostorage.
warning T("Kore tried to get an item from storage 3 times, but failed.\n" .
"This problem could be caused by a server bug.\n" .
"To work around this problem, set 'relogAfterStorage' to 1, and relogin.\n");
$args->{warned} = 1;
}

Is because this you not have noticed.
Don't happen this with you (The kore will try storage the item, if the item is failed, its not stored, the kore will stop.


Nhaauum.

Regardless, dcOnEmpty should take precedent over relogAfterStorage 0 as a proper fix so both can work together.