TrailMyx's Advanced CLAw FULL - The Ultimate Autolooter - Public Release!

[jenovauh]

How many rules in total do you have?  Also, are you running any other scripts in parallel with the looter? 

I have seen sometime when loot time increases as run time also increases, but not nearly what you're experiencing.

The real only thing that we have control over is the size of the variables that are accumulated over runtime.  You might want to take a snapshot of your vardump (Tools/VarDump) when you first start the script, and then take one when you start experiencing slowness.  Then compare the sizes (in bytes or lines) of the 2. 

It's been a while since I did an analysis like this.  Feel free to PM me your results, but don't post the actual vardumps because there's account specific information.

Also, there's an older version still posted.  You might want to try that and see if it works differently.

I had tested the old version too. They are both about the same after 1 to 2 hours of nonstop looting. I had pm you my vardump files. By the way, how can we control the size of the variables that accumulated over runtime? Is there a way to clear easyuo cache while running it or the namespace data?

[TrailMyx]

Thanks for the PM.  Nothing is changing very much from the variable world.  I recommend you going through all your Rules in the "Rules" tab and de-selecting everything that has a "Log?" checked.  This will prevent the "History" tab from getting too large and this might slow things down.  You can also check your history tab and see how many items have been cataloged over time.  If the number is large, then removing the logging might speed things up a bit. 

Actually, there's a variable at the top of the script called "%use_history" that you can change to #FALSE to turn off all history collection.  You might try that first instead of unchecking everything to be logged.

If that doesn't work then I'm at a loss.

[jenovauh]

Thanks for the PM.  Nothing is changing very much from the variable world.  I recommend you going through all your Rules in the "Rules" tab and de-selecting everything that has a "Log?" checked.  This will prevent the "History" tab from getting too large and this might slow things down.  You can also check your history tab and see how many items have been cataloged over time.  If the number is large, then removing the logging might speed things up a bit. 

Actually, there's a variable at the top of the script called "%use_history" that you can change to #FALSE to turn off all history collection.  You might try that first instead of unchecking everything to be logged.

If that doesn't work then I'm at a loss.

I had sent you a pm, anyway I will try to use set %use_history #FALSE and see if it helps. I will keep you posted, thanks a lot for your help. I realized noone else is having the issue as I did not see anyone replied in the post or because noone is using long enough to notice the issue?

[TrailMyx]

I had sent you a pm, anyway I will try to use set %use_history #FALSE and see if it helps. I will keep you posted, thanks a lot for your help. I realized noone else is having the issue as I did not see anyone replied in the post or because noone is using long enough to notice the issue?

The last thing that was really an issue that people had was the history thing, so I added that variable so that people could turn off that function.  I know quite a few people still use the CLAw, but less people use EasyUO anymore now that there are faster/better tools out there.

Anyhow, I'll test a bit this weekend running the script looting my MIBs and see if I see a drift in loot times.

[jenovauh]

Anyhow, I'll test a bit this weekend running the script looting my MIBs and see if I see a drift in loot times.
[/quote]

Thanks for spending your time to test it, I am still using easyuo for everything possible in UO. Usually the delay will happen quite bady after 2 hours of looting. And I dont see that looting anything or nothing make a different. I tested only looting gold and a few rules which will almost loot nothing. Doesnt make much different.

[TrailMyx]

Your use case is much similar to mine.  I use the both the FaF and the MIBAutoFarmer to loot over hours, so I'll keep a running total of the average rules/second found in the STATS tab from chest to chest to see how this number changes over time.  I'm doing a 20 MIB run as I type.

For context, my loot profile has:
Rule count: 44
Active rules: 21
Complex Rules: 5
Omit Rules: 3

[jenovauh]

Doing MIBs, the CLAW issue doesnt kick in so soon. Will takes a lot of MIBs like 100 and above to see slowness happening. The fastest way is to kill and get CLAW to scan all corpse at high spawn rate area. 

[Insideout]

oKAY HOW DO i ADD RESOLVE'S BRIDLE TO THIS LOL THE ' MESSES UP USER DEFINED

[TrailMyx]

oKAY HOW DO i ADD RESOLVE'S BRIDLE TO THIS LOL THE ' MESSES UP USER DEFINED

Just add the keyword "Resolve".  That should be enough since I'm not sure much of anything else has that name.

[Insideout]

oKAY HOW DO i ADD RESOLVE'S BRIDLE TO THIS LOL THE ' MESSES UP USER DEFINED

Just add the keyword "Resolve".  That should be enough since I'm not sure much of anything else has that name.

TM I did that still no luck. Tried adding the GHH which is what the ID tool says it is. Still no luck. I added reslove >= to 1