I'm looking into creating an account scanner to scan accounts you own to find all aspects of the account without needing to manually log in and check each account individually. It'd be written in Python as it's my favoured language, as well as the fact I use both Mac OS & Windows. The question I have here is what aspects of an account should be scanned for an in-depth scan? So far, I've considered the following;
- Neopoints on hand
- Neopoints in the bank
- Stock value
- Inventory
- Shop till
As you can see, it's a pretty basic concept I have, though I'm not too sure what other areas of an account are a good place to scan. Any help/ideas would be appreciated.
- edit -
Finished an extremely basic (and ugly) scanner
Next, I'll be looking into adding SDB + Gallery scanning, I'll also be looking into creating a JN wrapper to assign prices to each item an account has. Finished SDB + Gallery scanner, moving onto a JN wrapper.
Finished JN wrapper:
I discontinued updating and altogether ditched the concept of my account scanner years ago to stop supporting account crackers, hoping it'd kill the interest altogether.
For use with your own personal account(s), this could be handy in case you need to retrieve the account from TNT support someday.
I should have mentioned this would only be for personal accounts you actually own and not public accounts you don't have access to for obvious reasons. The main goal for this is to keep track of all of your accounts stats without manually logging in to each account. Plus, it could be useful if you ever needed certain information on an account for TNT down the line.
For the most part, the concept of this is done. The code is incredibly hideous, which will likely need to be refactored before anything. That way, I can continue to add new scans into it without much issue. I'll probably add price caching into the JN pricer, which is valid for 2 weeks. This way, if accounts share the same items, it won't need to query JN for the prices constantly. Instead, it can refer to the local database with the prices stored in it.
Price caching has been finished. Before querying JN For prices, it'll check out the local database and only query JN if it doesn't have the item already in the database. The caching is valid for 14 days. Once 14 days passes it'll then query JN again and update all prices for the items it comes across on accounts.
Not sure if this will help since you've already built the whole SDB checker + price caching and all, but I recently found out that JN has it's own SDB price checker (page-by-page, not all at once)