Vid,

I think there may be a bug in the STEALFACTOR calc that writes the SF value to the twxdb .cfg file. I ran this for the first time in a new game, so I didnt know what to expect for results.

Then the next 2 days I was botted for SDTs and I happen to see that I was only stealing ~60 holds with ~4k+ xp.

It turns out that the TWX SF was set for 70 and not 21.

I also just checked the mombot settings too.

MBBS     COLO_REGEN     PTRADE     SF     RF     PORTMAX
1          65535          100      70      50      32760

And I could be barking up the wrong tree altogether, can you take a look and let me know?

Helix

Look in your Steal Factor variable in your data/gamename.cfg file.....if it says 70 your good but someone change this in the newer mombot to Steal factor 21 instead....the script does the math from 70 percent not 21 holds.

if this is the case then you will need to mod your mombot to get correct value.

Kbot uses 70 percent for the calcs on all our scripts so we cant change now.

The older mombots used the steal factor from the * screen also.

The current mombot uses 21, and many of it's scripts are based on that.

This basically creates 2 standards fighting for the same variable. Not good.

mombot code that changes the sf and rf from 70/50 to 21/6 and saves it to the .cfg
setVar $steal_factor ((30*$steal_factor)/100)
saveVar $steal_factor
setVar $rob_factor ((3*100)/$rob_factor)
saveVar $rob_factor

Going to go through each of the bot's red cashing scripts and see whats what. (timed colo is on hold)

Vid, from what I can see now, your calcs are okay, its the bot thats off

Helix

I agree which is why it never should have been changed.

the mombot setting file (which i assume some scripts use or why have it?) lists it as 70

The mombot code was cut and pasted directly from stbot.

Stbot listed steal factor as 70 not 21.

The '*' screen at T-Menu shows all config data , or it should , and keeps record of MBBS and SF .. when MBBS , SF = 70 .. set in stone.
most scripts or some functions look for the factor 21 , but infact it is a Steal Divider . . so I think in k-bot style config files .. the $Steal_Div is an mathed out answer for SD.
Now the config has extra vars saved , but the cal can be done on any setting.
Just have to LoadVar the right thing.

The biggist reason most scripters are trying to keep to common vars in config and parameters.

I think it was SupG who coined the $Steal_Div var back in the day.

My 2¢

Looking at old ST bots, it's 21/30. Has been for years. At least since 2006. Mombot may have went
w/ the steal percentage for a time, but a lot of code doesn't anymore.



The original st bot didn't have any of this. It wasn't until the 2.0 series that it was added. In st bot
2.01, it is 21. I'm looking right at an old ver that hasn't been changed in years. It uses the term
$steal_percent for the percentage.

My copy has $steal_factor as 70 not 21 and does the math to $steal_div.

all this info right from the * menu.

the older mombots were 70

the mombot gamesetting is 70

but peeps can use what they want I perfer to be backwards and forward compatible when possible.

For example my bot uses the var. $LSD_GENCOST for the cost of gentorps. Why? Because this way Lonestar's shopper doesn't exit enter me and Tax me to get these variables prior to running.

By being compatible we can use both older scripts (some slightly modded for bot work if needed) and anything developed for mombot.

Personally I find this trend of putting a ego tag on variables as over the top but its all in fun so whatever works is fine.

just my penny.

You sure you didn't change that? I've got an st 2.01 from 2006 (is on a CD that I burnt, so it's not been modded)
that uses the post-calc (21) numbers.



Nod



Hrm. What version, specifically? I've got a version from BH that he sent me while working on it, it's got
21 in it. I vaguely remember having a similar discussion with misb around then, too. I'm wondering if
maybe it got changed to the % later on.



The text file shows it as 70, but that's because of the way it's written. It actually does the rest of the
calc afterwards and stores i that way. Not sure why...



Nod. Which is why this is a useful thing to figure out, so that stuff works together when possible.



LOL. Most of my vars have something in front of them too, but it's just to denote what script they're for.

Generic * info is different, tho.