Userscripts.org

Fixed two spots with the debug messages I use... prolly not useful for you guys though. Anyway, 1 of these caused the error on v1.07.

ROR messages now a part of the debug window to show you what auto-buy is going after.

Also note the Global Variables section from line 2043 to line 2062:

/* Global variables */
var reload = true;
var got_captcha = false;
var boss;
var itemlist;
var maxcash = 10000;
var towait = 0;
var taskdelay = 0; // 5 seconds was default but that was slow...
var max_evades = 3; // max evades to ignore the hitlist
var auto_on = false;
var auto_off = true;
var crit_level = 33; // critical health at less than 33%
var min_stamina = 0;
// refresh time in seconds
var norm_refresh = 600;
var long_refresh = 1200;
var debug_msg = '';

norm_refresh *= 1000;
long_refresh *= 1000;

Some of these are hard-coded settings that you can fine tune.
auto_on, when true (on), will automatically turn on aggressive refresh when your stamina is maxed out.
auto_off, when true (on), will automatically turn off aggressive refresh when your stamina hits the value you set for min_stmina.
crit_level is a percentage of health (to max) that must be there in any situation. The hitlist bot, for example, will bravely hit its target in respect to the 25% minimal set by the game which allow you to hit anything, even if you have the 60% set to heal, it will keep hitting because it sense a chance for victory (hrrmph), so use this to "save your butt" before you "kick someone's butt".

The way my hitlist mechanism works, is to refresh against the main page, instead of the hitlist page, while it is arguably to be slower to reach the actual hitlist, but it reduces the chance of being blocked by the game, as the game is jotting down who's over-refreshing the hitlist page itself. Besides, the first one to hit the target is not always the one to do the final blow & claim the prize... On the other hand, max_evades is a figure that sets how many times you have ignored targets in the hitlist, and will not check the hitlist again until the hitlist has more than 1 target, which should normally suit all situations.

towait and/or taskdelay was default to 5 seconds in the original script, I have it moved here and changed to 0 because I simply do not want to wait 5 seconds before making any action.

Also note lines 906 through 920 where it generates minimum and maximum values for bounties. These values suit my levels for the past 2 weeks, so far I manually adjust them only when necessary (such as adding a 0 to the end to the 50000000).

Unless CAPTCHA appears, which will gain focus, the script always focus on the "aggressive refresh" checkbox, so you can use spacebar to toggle it on/off in case your mouse is not handy.

I'll be moving some of these settings into the preferences later.

Additional notes:

When auto-hit is turned on in the preferences, it means it WILL attack a target that is within the range of your bounty limitations (min/max) when you *ARE* inside the hitlist. If you're in other pages, it will not hit anyone, of course.

So you have two options:
1) manually click into the hitlist
2) turn on aggressive refresh to check if anyone's on the hitlist & the script will take it from there

Because the "Aggressive Refresh", is refreshing against the MW homepage. IF you don't plan on hitting bounty targets in the hitlist, then do not turn this on. While this is active, unless there are other "more important tasks" at hand, such as completing a job, healing, buy some real estates, it will keep refreshing until it detects an active hitlist and visit it only after it appears. This is to refrain from visiting the hitlist itself as much as possible. As mentioned in the top post, MW monitors the hitlist refreshes and block people who refresh it excessively (used by most other bots I would imagine.)

You're welcome. Autofighter is in the plans. When implemented, though, it the script will think like me, though. Haha. I'm sorry but most of the time FBMWH+ is suited to my play style.

BTW, I just noticed a little mistake I made when moving the debug messages to avoid an earlier error in v1.07. Now the CAPTCHA image is shoved off to the debug too.. which won't appear until you've entered CAPTCHA... so it means v1.09 should be right up. Sorry.