It doesn't matter what the item is. It's all oriented in the same order, just with a different image. It could have contained an image of a suap, he just needed to get an idea of how the code is formatted.
Rare I did this a while ago for myself (privately)
See in the HTML source where it says "<b>Smugglers Cove</b>", extract the string inside that text and this closing tag "</DIV>" and just compare each refresh for the string length. If it changes, there is an item to purchase. You just scan that string for the buyout link.
1.You load a list of accounts , these accounts refresh the cove once every 10 seconds until rs blocked then move to the next account. By the time the end of the list is reached the first accounts are no longer rs banned.
2.Have a main "buy account" loaded with dubloons and logged in but not doing anything at all ,but we have the cookie saved to a string
3.If the search accounts find a item , the buy account cookie instantly gets used to buy the item.
This means theres no need to have 60 accounts all with dubloons or to make functions that trade the dubloons between users. Infact I could run the buy account from a seperate ip adress and look really legit ;D.
Why i need the html:
I did not know the buy url and post data needed to buy a item. Another words , the url of the page you are taken too after clicking "buy item". Without this all I could do was detect items , not actually buy them. I do not need the html of the result page , I will grab that just buy detecting a buy then saving the html to a file of any result. Once I have a bas result/good result i can set flags in my program to detect what a result was. But without the above code it was impossible to do in a way i considered worth investing the time.