FBMW++

By Pea Cracker Last update Feb 24, 2009 — Installed 39,024 times.

1.22 is up

in
Subscribe to 1.22 is up 21 posts, 13 voices



Pea Cracker Script's Author

Yup it's hot... my head is all messed up reading little lines, now I can't even remember what I did. Maybe the "diff" function in the source code in UserScripts will help out. As far as I can recall, it was mainly reorganizing lines, correcting some typos, add the filter to fix the current hosting company's javascript insert and added a in-panel captcha image placeholder for reports from the back scene (medics for now). Good luck, folks.

 
GNomad Scriptwright

Smooth so far. Testing it all out.

 
@cid Scriptwright

so far so good. Pea dont mind me asking where you from?

 
DTAN User

any reason why i can't download and install 1.22 ? when i click install, it direct me to source code page . :(

 
Superviza User

DTAN - You dont have GM enabled then ;)

 
DTAN User

i just noticed that .. and installed it .. unfortunately i still face the same issue on earlier version .. 1.17 onward ..

not healing, doing jobs, as well as bounty hunting. i'll post in bugs thread

 
vazelky User

no problems here so far PC!

 
Pea Cracker Script's Author

Ok I found a bug... that will disable it from correctly updating the data for the "Cure for CAPTCHA"...

 
Nozama User

It all looks good now that I skipped from 1.15 to 1.18 to 1.22. 1.18 ran all day and 1.22 is going with no issues so far.

 
Superviza User

Nice work PC.

I'm still experiencing the problem where the agg refresh will stop after a hit.

Apart from that, looking good

Superviza

 
Phazoni User

The autobuy feature is working for me again. Thanks PC.

 
WelshY User

Pea Cracker I must Say One hell of a coder Well done on the Hard work you put in to this
Really most the people on face book apps hate you for it But I love you For it ;) make every thing a lot easier Ha-ha!!
Would be good if you can get that captcha to type the image in the box that pops up saying that the image is need text then we can just leave the pc on and let it do it in stead of worrying about the captach popping up
If any one no any code scripts to do this would also help in this script
Keep the good work up Pea Cracker and don’t lose too much sleep over it: D

 
Phazoni User

WelshY, that's kind of the point of captcha. The graphics are not easily readable by a machine and therefore needs a human being to interpret the image and type the letters. The captcha is there specifically to stop folks from using 'bots.

 
WelshY User

There are scripts out there to do it and there are software to do it
but the people that are doin theys scripts are askin £ $ for 300 captcha's

 
vazelky User

PC, great job on v22. works perfectly for me now after a few cycles. at first the agg refresh would disable after a bounty kill but that has stopped happening now. thanks for a great script.

 
Grneop User

Thank you PC. It is working great on all 3 computers and on my Mac book pro.
now out of the subject, knowing that this is NOT a BUG, are any of you guys getting this message?

"This page is being heavily rate limited. Please avoid constantly refreshing this page."

Does not let me refresh the hitlist screen,no graphics at all, even when I set preference for Home, then send me back to home. Consequences: I don't get bounty kill.

 
Pea Cracker Script's Author

As the message suggests, you are refreshing the hitlist more often than FB/MW would like you to. My personal suggestion (for everyone, actually) is to scan off the HOME instead of the HITLIST. That was how I first coded it but added the option to scan off the HITLIST because some believed they would hit more bounties that way.

I know that there is a logic bug if the user has set the scanning to HITLIST, put on Aggressive Refresh, and that "This page is being heavily rate limited. Please avoid constantly refreshing this page." thing comes up -- the script will identify this and reload HOME. But once landed HOME, since the user has Aggressive Refresh turned on, and has set to scan HITLIST, it goes to the HITLIST again... and guess what? FB/MW complains again with "This page is being heavily rate limited. Please avoid constantly refreshing this page.", and yet the script reacts... so there, the LOOP... as some have reported already.

So now you know why it is happening, and that there is an option to get out of it...

 
Grneop User

Thank you again PC.
That is what I thought. I was using Home but try exactly what you said HITLIST instead, and for sure didn't work.

 
Keleas User

Pea - Here's what I usually do.

Use scan hitlist, till I hit the refresh limit.

Disable aggressive refresh - set the script to scan Home instead for around 15minutes or so, then back to the hitlist scanning for about another hour till it hits the limit again ~ and so on.

So the script could just pause the aggressive refresh (Bounty hunting) for 10 minutes or so before starting again, or just automate the process I do, or just neither. o_o If someone is planning to leave the computer, Home scanning is better for them.

 
outofideas52 User

my jobs thing isnt working still. nor is agg refresh. im in a crappy mood so im sorry if i sound pushy

 
remarkable Scriptwright

Great job on 1.22 it works great but the location of the script at the top of the page just isnt as convenient as 1.5 so i'll be switching back. Watching the bounties pile up on the screen just seems to be a much nicer feature and i believe the page loads faster for me - even though the bounty calculation is a bit off and the timing of jobs is too, its just a better interface.

Cross
Presentational HTML allowed.
Use <code> for inline code and <pre> for code blocks. Use &lt; and &gt; for literal < and >.
We help break paragraphs and link your links.
or cancel