Problems with Storage!

Forum closed. All further discussion to be discussed at https://github.com/OpenKore/

Moderators: Moderators, Developers

Message
Author
blank92
Noob
Noob
Posts: 4
Joined: 11 May 2012, 18:12
Noob?: Yes

Problems with Storage!

#1 Post by blank92 »

The storage is perfectly fine; bot stores all items that i want, when at 49% or after death, but the thing is, after doing so, he dont move at all! I think the problem is because he can't close the storage, every time that this happens if i use the command "storage close" he then proceeds to the lockmap

i have downloaded the files over and over and reconfigured everything, any help here?

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Problems with Storage!

#2 Post by EternalHarvest »

storageAuto_keepOpen?

blank92
Noob
Noob
Posts: 4
Joined: 11 May 2012, 18:12
Noob?: Yes

Re: Problems with Storage!

#3 Post by blank92 »

yes, I forgot to mention, i changed it to 0, -1, 1, 2, nothing seems to change

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Problems with Storage!

#4 Post by EternalHarvest »

Sounds like a bug, then.

blank92
Noob
Noob
Posts: 4
Joined: 11 May 2012, 18:12
Noob?: Yes

Re: Problems with Storage!

#5 Post by blank92 »

no way to fix it then? i tryed to set to other kafras and never it seems to work, bot dont close storage!
=/

andy12345
Moderators
Moderators
Posts: 174
Joined: 04 Apr 2008, 10:21
Noob?: No
Location: In your dreams...

Re: Problems with Storage!

#6 Post by andy12345 »

blank92 wrote:no way to fix it then? i tryed to set to other kafras and never it seems to work, bot dont close storage!
=/
A workaround could be relogOnStorage? http://www.openkore.com/index.php/RelogAfterStorage
If not you can always try to write a macro that would relog after storage.

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Problems with Storage!

#7 Post by EternalHarvest »

blank92 wrote:no way to fix it then?
It's now in bug reports and should be fixed eventually, either by you or somebody else.

Or a good enough workaround may be found, too.

Locked