Hendrikos

When starting bot I get the next error:

Request Template: - Script name Blast Furnace - trial length 24 hour please - Reason for trial Smithing XP & Money - Are you ging to give feedback on the script? Of course, I'll be baby sitting it anyways.

Can I have a trial please?

Can I have a 24 hour trial on your Thiever? Thanks in advance.

Humidfy is working much better now, in some occasions it is still a bit too fast to click. Perhaps it's an option to re-click the bank faster then? As failure, especially being impatient seems to be human-like to me?

Thanks alot, will give it a shot tomorrow if the update is pushed. Will post feedback when I've tried it with the new update.

Do I have to perform a certain action to "refresh" the script? As the bot is still clicking too fast. It switches properly to the inventory but clicks just before the items change to "watered" ones. By the way, for Humidify the interface says Pie name instead of raw material or something.

I'll try Humidify again today. Thanks for the quick fix. I'll give you feedback when I have tried it.

How comes I have version 0.63, while you said version 0.64 should be online on page 96. Also the scripts says to be up to date in my client. Edit: I also would like to notify that when using Humidify the banking is very slow. It seems to appear that the bot clicks to early on the bank, and then waits around 5 secons to try again.

Nevermind.

Is there a way you can pay the scritps which you've to renew each month. Without a creditcard? Like you have to pay each month manually.

Not knowing the password would mean you've to brute force it. Which does pretty much mean, loop true every possible option, hash it, and check if it equals the hash string. As mentioned above you won't crack the encryption so there is no fast method. SHA does spit out the same password for the same string. However there is a solution which pretty much solves this problem. Which is called a salt. There are pretty much two types of salts. A static one, which is defined somewhere in the class, and a dynamic one which is saved often in a database, however this isn't really save since when someone has access to your database he has the hash and the salt, and just need the password. So the salt has no use. I often hash my passwords this way: $salt = 'random_string_of_characters'; $password = 'password'; $email = 'users_email'; $hash = hash('sha256', $password . $email . $salt); This way you've a static salt, and a dynamic one. The reason why you should use a dynamic salt is, when someone hash to equal hash strings(the chance is little, but it could happen). You can't use the same password to login, since the dynamic salt is different, which will create a different string, which will become a different hash. The chance of getting the same hash with the same password and a different salt is too little, I don't even know how little it is.

I am not sure if I understand your problem, however I'll try to answer you though. To get the password hash, you need to know what type of encryption is used(For exampe SHA256). As second you need to hash the plain password. To check if the username and password are right you need to create a SELECT query in MySQL. You would get something like this: <?php $username = 'Username'; $password = 'yourpassword'; $password = hash('sha256', $password); $query = mysql_query("SELECT * FROM users WHERE username = $username AND password = $password"); $count = mysql_num_row($query); if($count == 1) echo "Username and password matches."; else echo "Invalid username or password."; ?> Note: The mysql_* function is deprecated as of php 5.5.0, but I used it to make the example clear and simple. And you probably are not using a newer version.