PackRat: script version 1.0
[This version of the script is OBSOLETE. For more informations and newer versions check the PackRat Helper category.]
Since the release of the 1.0-beta version of the script a month ago, the script has improved greatly on the stability and features level. That’s why we are now proud to present the first stable 1.0 release.
The stalking module that was broken a couple of days ago by an update in the PackRat application is working again and some minor features you requested were added.
I’d like to thank Donna for her donation to this project.
Changelog:
- The script takes into account the new changes to buying introduced by the PackRat developers. Market stalking will work again.
- There is an option to browse only through Rats in the Browse section.
- An option to stalk every market (instead of only those were there are known cards from the shopping list) has been added. Use it if you are looking for cards that are not already in the database.
- A fourth shopping list was added: “Empty”. It can be useful if you are looking only for cards that are not in the database.
- There is an option to steal locks even if they are not in the shopping list. It can be useful to free some space in the pack, while not buying any lock from the markets while market stalking.
- A couple of new script commands were introduced: “Show pop-up statistics” and “Show unknown cards”. The second one can be useful to correct some misspelling done by the PackRat Devs. E.g. if the image file for “Any Card” has a name that is different from “any-card” (e.g. “Any%20Card” or ‘any-cadr”, etc.) I must take this into account in the database to correctly detect it.
Download PackRat Helper: version 1.0
Also available at UserScripts.org, where you find a short manual.
For more informations about the installation process please check the FAQ.
Wonderful script. A few comments as always.
1: I find that if you attempt to override the script by clicking on something, a script error occurs. For example…
A: You go to your pack.
B: Before the script completes (The script status box shows up) you click on another page… Let’s say your pack page again.
C: Error message usually occurs here, and it forces a reload of the page. If you clear out the error message before the page completely reloads (and the script to complete), it will trigger another reload, causing another error message to pop up again. I find the solution is to be patient and wait for the script status box pop up before clearing out the error message.
2: An auto stop browsing when shopping list is complete. This would be overridden by the hunting for unknown cards of course. This would be desired when all you are hunting for is a couple of pop ups.
3: The stalking delay “revisit every market every X seconds”… I would rather set a “visit each market X seconds.” This means that time spent in each market remains consistent, so when markets are no longer being stalked, remaining markets. When there are no more markets with stuff in the shopping list, of course auto stop. Auto stop would of course not trigger if hunting all markets for unknown cards.
I’m suggesting the auto stop, mostly because if I can obtain all I need, it would keep FB wondering why I stayed up all night, clicking on credits that I don’t need. (Okay, maybe they won’t, but I would rather be safe than sorry)
Comment by Max — 7/9/2008 @ 7:28 am
Market stalking works fine now. However since yesterday, the script has not been able to automatically pick up popups on the shopping list. The popup highlights but will not pick up. Hope you can look into it, thanks!
Comment by Chris — 7/9/2008 @ 12:34 pm
Reduce, Reuse, Recycle is still being unknown. shows up as
green-scene/reduce-reuse-recycle
I also had this pop up as unknown
oh-the-drama/redcarpet
oh-the-drama/unknown
in my unknown statistics.
Also, I’ve not had problems with pop ups… as far as I know.
Comment by Max — 7/9/2008 @ 2:50 pm
Oh, and the error message…
Error in module ‘page’ on line 53: div is null
Error in module ‘card’ on line 175: div is undefined
Error in module ‘preferences’ on line 526: document.getElementsByTagName(”body”)[0] is undefined
Error in module ‘menu’ on line 665: document.body is null
Error in module ’stalk’ on line 1585: notes is null
Error in module ‘browse’ on line 1922: notes is null
Seems like initializing variables early in the script is in order… unless this behaviour is intended…
Comment by Max — 7/9/2008 @ 2:56 pm
The auto popup pickups now seem to work, although I do get error messages now and then mentioned in the above comment. Thanks again for the update!
Comment by Chris — 8/9/2008 @ 7:14 am
About the error: I will delete the line that shows up the pop-up in the next releases. For your information, the error appears because when you click on a link while Firefox is still loading, it will stop loading the page and signal the script that the page is complete, while it is not the case. The script does not find anything familiar in the page and issues an error.
Max: About 2. and 3.: the script regenerates the list of markets to go every time, so if the shopping list is empty, the market list is empty too and the script stops stalking. I chose to have a regular interval between two visits to the same market rather than switching markets every a fixed number of seconds, but I don’t have a preferences in the matter.
Comment by Piotr P. Karwasz — 9/9/2008 @ 2:33 am
Been having problems the last few days - the script runs only for a short time ( sometimes only scrolling to 2 packs) then i get this ( screenshot) http://i264.photobucket.com/albums/ii197/ostle73/error.jpg
I hit ok then have to hit refresh to get it started again.. Its really frustraing as i leave the script to run overnight to collect credits and pop ups mainly.I have re installed the script but its no different - went to 5 packs then back to this again…
Can you advise if i need to do something?
Thanks Barb
Comment by Barb — 10/9/2008 @ 12:23 am
Barb: I removed the pop-up from the new release (1.0.1), though your screenshot looks a little weird to me, the script should reload after 30 seconds automatically to recover from the error.
Comment by Piotr P. Karwasz — 10/9/2008 @ 12:52 am