Kali's Bod Sorter for openEUO

[KaliOfLS]

Ok, I will look into it.

[KaliOfLS]

I only changed two lines in the script, one that made it easier for users to define their index, and one that was creating an unnecessary table.  I am completely shocked that this change would cause a crash.  I will give it a run through when I get home to test it out.  On that note, my hypothesis about opening too many gumps seems bunk.  I've constantly cycled 3 bod books opening 1/second, for the last 2 hours without a single connection loss.  I'll test the script out when I get home.  I need more bods!! I'm working on collecting.  I will have about 8 characters that can collect 3/day I think, so I will try to collect 24 bods per day for the next month, and then I'll be up to about 1000 bods.    Then we will give it a real test, but until then, I'll recombine the ~1k I have now and test again tonight.

[Nellie]

I am not sure whats doing the crashing, maybe i have too many bags open? i have 9 with bods in and 18 to sort into, of the ones that i am sorting into only 8 are on the screen, i am guessing with the spacing the last 2 bags are in my daughters bedroom

This is the last line i just got when UO crashed again ...User\Desktop\Stuff\OpenEUO\scripts\kalibodsorter.lua:240: attempt to perform arithmetic on a nil value.

Not sure if that means anything. or just the fact that the script closed because the client crashed.

Nel.

[KaliOfLS]

Yeah, that is because the client crashes.

I call UO.Property on your backpackID to figure out how many items are in your pack.  If it cannot find your backpack, it will return nil and then I calculate 124-items, so arithmetic on a nil is because the client crashed.

Try this version, I've added debug information to try and capture the crash location. And made it so your daughter doesn't have to put up with those ridiculous backpacks in her bedroom.

[Nellie]

ok will try that one, i just tried it with 3 bags to sort from, and 8 bags to sort to, it dropped about 8 bods to my bp and crashed.

Nel.

[KaliOfLS]

Anyword nel?  Did it break?  I just opened a bod book and shoved it's container position into the 20k, so I don't think that is the case either.
I'll be heading home soon.

Edit:  Well, I just tore through 897 bods, no crash, no time out.  Two source bags, Two reward bags. :-/

[Nellie]

Well its a new day, will try again, see if it was just my computer playing up yesterday., nearly finished now so even with all the breaks and crashes still sorted about 10k bods yesterday, so cant complain.

Nel.

[The Ghost]

SO look like I miss an exciting night. So let me refill my BOD and see it I'm having the same problem as you guy with Ver 2

[KaliOfLS]

Please do so! I'd love to see if you are.  I'm having a problem reproducing.. not just because I'm ugly.

[Endless Night]

Script move to approved library
Thank you for your submission.

If you feel the script is in the wrong section please send me a pm.

[The Ghost]

Hi Kali

[The Ghost]

Hi Kali

          I have 2400 BOD to sort.  I have download 2.2.  have 5 chests with BOD and 4 with sorted BOD.  after min the client crash,  hit play again and one again 20 min later it crash again.  In both case I have a tailor turn in on me wit 345 bod.  that make the secure overload.  So right now  I  have only 1 tailor turn in per secure ( 3) and rest between 2 secures.   let see if that will fix the problem.  It seen that you done drop the book into a new container if this one if full.  I only have the kalibodsorter running. I don't index yet;  not sure how to use it )

let you know how the 1500 remain BOB go.  Running then right now.

[KaliOfLS]

Hi Ghost,

I do not have a check to make sure the resulting container can hold the full book.  I suggest for the very common ones like the turn in books, that you have one per bag when sorting a high volume.  However, that should not cause a crash (also, if you could describe crash.. i.e. is the client crashing and you get an error message, does oEUO crash, or does the script just 'break'?) but cause the script to break because it cannot move the book back to the original reward bag.  

I ran this script on 3.7k bods without a single problem.  I did however, have it set up with one book/bag for the common ones, and had one bag with the higher end rewards in it.
If you are having issues with the client actually crashing, could you try increasing the lagOffset to 250 or 500?  It will slow the script down by increasing wait times between drags/drops.  However, that is the only command being sent to the client other than mouse clicks to empty the bod books.  

If you're experiencing an actual client crash, then you're not the only one experiencing client crash issues, but I do not know how to trouble shoot it since I cannot reproduce the problem on my machine.  I will ask some experienced scripters if they could try the script to see if they can reproduce the client crashes.

[The Ghost]

On the third attempt, I have put all the turn in into the separate secure,  same with other one and it run smooth.  I'm please with the result.    I forget that you put 345 bob into a book. 

I crash, mean the client close completely.   Guest he didn't like the msg container full )    I have a request to ask.  Can you add a display msg  that tell us that we are done.  And how can we only put 250 BOB in the turn in BOD.  thx.     

Gonna take me a few day before I can try high volume of BOD again. 

[KaliOfLS]

Yes, I can add a finished message  
250 BOB? 
You mean you want to put only 250 bods into each book?