looks awesome man

if i wanna take lobbys from bank it wont take it, it just doesnt move

 

plz fix it - thanks:P

 

Can you please screenshot you GUI? Withdrawing works fine if you set up the GUI right.

 

Eric

looks awesome man

 

Thank you.

Any progress on running when you have a random reward?

 

Also you should think about making the GUI a little more idiot-proof.. examples:

 

1) Make it so when you hit Start all of the boxes are considered filled in(So that people can't forget to hit enter)

2) For the food section, split the String and capitalize the first letter.(So that people stop saying it won't withdraw lobsters, etc)

3) Eat At should be Eat At(%) so people realize it's eat at 60% not 60 hp.(Would stop people who say "the bot isnt eating at 30 hp wtf")

 

Also setting up a save\load settings sooner rather than later would be awesome since you're very active and are pushing like 10+ updates a day. :P

Any progress on running when you have a random reward?

 

Also you should think about making the GUI a little more idiot-proof.. examples:

 

1) Make it so when you hit Start all of the boxes are considered filled in(So that people can't forget to hit enter)

2) For the food section, split the String and capitalize the first letter.(So that people stop saying it won't withdraw lobsters, etc)

3) Eat At should be Eat At(%) so people realize it's eat at 60% not 60 hp.(Would stop people who say "the bot isnt eating at 30 hp wtf")

 

Also setting up a save\load settings sooner rather than later would be awesome since you're very active and are pushing like 10+ updates a day.

 

Hey, thanks again for your suggestions!

 

Version 0.2.5 takes care of those rewards, (hopefully, haven't tested). I still haven't coded the auto log off if you've been teleported somewhere random.

 

It also no longer auto-wipes your settings, so you shouldn't have to type in your settings every time I update anymore :P I'll try to make that a bit more advanced later though.

 

I've followed your suggestion to auto-capitalized and added the %. As for the auto-enter... I haven't figured out how to do that, since that's internal to JTable.

 

Eric

 

Any progress on running when you have a random reward?

 

Also you should think about making the GUI a little more idiot-proof.. examples:

 

1) Make it so when you hit Start all of the boxes are considered filled in(So that people can't forget to hit enter)

2) For the food section, split the String and capitalize the first letter.(So that people stop saying it won't withdraw lobsters, etc)

3) Eat At should be Eat At(%) so people realize it's eat at 60% not 60 hp.(Would stop people who say "the bot isnt eating at 30 hp wtf")

 

Also setting up a save\load settings sooner rather than later would be awesome since you're very active and are pushing like 10+ updates a day.

 

Hey, thanks again for your suggestions!

 

Version 0.2.5 takes care of those rewards, (hopefully, haven't tested). I still haven't coded the auto log off if you've been teleported somewhere random.

 

It also no longer auto-wipes your settings, so you shouldn't have to type in your settings every time I update anymore I'll try to make that a bit more advanced later though.

 

I've followed your suggestion to auto-capitalized and added the %. As for the auto-enter... I haven't figured out how to do that, since that's internal to JTable.

 

Eric

 

You may want to check out the stopCellEditing method, here's a pretty easy solution to the problem. I believe it's applicable.

 

http://tips4java.wordpress.com/2008/12/12/table-stop-editing/

Edited July 21, 201312 yr by RSPlayer9669

 

You may want to check out the stopCellEditing method, here's a pretty easy solution to the problem. I believe it's applicable.

 

http://tips4java.wordpress.com/2008/12/12/table-stop-editing/

 

 

Thanks a lot! How come I couldn't find that page ...

 

Version 0.2.6 implements this.

 

Eric

Edited July 21, 201312 yr by ericthecmh

Im glad your working on a script like this! But... atm its like "works, doesnt work, works, doesnt work" and so on, it gets a little annoying.

Im glad your working on a script like this! But... atm its like "works, doesnt work, works, doesnt work" and so on, it gets a little annoying.

 

Hmm... none of my updates have broken the script... people just post new bug reports or suggestions and I change my code to fix them or update the suggestions.

 

Eric

Im glad your working on a script like this! But... atm its like "works, doesnt work, works, doesnt work" and so on, it gets a little annoying.

If you're basing that off of the replies on this thread, then read the ones where people were saying it doesn't work, 90% of them are human error("lobster" instead of "Lobster", not using item id for loot, not hitting enter) which with the latest update have been made moot anyways.

 

The other 10% are mostly compromised of the bot not solving randoms correctly.. which is the fault of OSBot not this script, sadly.

 

That said, the script is pretty flawless.. yes there are a few minor things wrong with it, but it was released yesterday.. so it's to be expected.. nothing is wrong that breaks it, though.

 

Im glad your working on a script like this! But... atm its like "works, doesnt work, works, doesnt work" and so on, it gets a little annoying.

If you're basing that off of the replies on this thread, then read the ones where people were saying it doesn't work, 90% of them are human error("lobster" instead of "Lobster", not using item id for loot, not hitting enter) which with the latest update have been made moot anyways.

 

The other 10% are mostly compromised of the bot not solving randoms correctly.. which is the fault of OSBot not this script, sadly.

 

That said, the script is pretty flawless.. yes there are a few minor things wrong with it, but it was released yesterday.. so it's to be expected.. nothing is wrong that breaks it, though.

 

 

No from personal experience with it.

First time i thought the script was messing up, it was myself not having the latest update, but since then i made sure OS and the script was the latest version before drawing conclusion on the functionality. Also all names and ID's were tripple checked (not that it was the main problem, except once when the script picked 20 food twice from bank). Checklist on first page also followed.

 

Main problem seems to be the pathing (gets stuck at doors) and it rarely works while starting in room (has to start in edgeville bank).

Main problem seems to be the pathing (gets stuck at doors) and it rarely works while starting in room (has to start in edgeville bank).

 

Hmm thats odd I started at Edge bank and it had trouble going down the hole in the Barb village.

But when I start the script next to the monsters I select it to fight its flawless.

Script has gotten me from 30-40 ranged very fast and made me about 200k doing the clue scrolls that dropped, and other loot.

Best Combat script on this site IMO...

 

Im glad your working on a script like this! But... atm its like "works, doesnt work, works, doesnt work" and so on, it gets a little annoying.

If you're basing that off of the replies on this thread, then read the ones where people were saying it doesn't work, 90% of them are human error("lobster" instead of "Lobster", not using item id for loot, not hitting enter) which with the latest update have been made moot anyways.

 

The other 10% are mostly compromised of the bot not solving randoms correctly.. which is the fault of OSBot not this script, sadly.

 

That said, the script is pretty flawless.. yes there are a few minor things wrong with it, but it was released yesterday.. so it's to be expected.. nothing is wrong that breaks it, though.

 

 

) with your help (and other people's), I've been slowly patching up the minor things thanks a lot! You've given a lot of good help to me. I really appreciate it

 

 

 

Im glad your working on a script like this! But... atm its like "works, doesnt work, works, doesnt work" and so on, it gets a little annoying.

If you're basing that off of the replies on this thread, then read the ones where people were saying it doesn't work, 90% of them are human error("lobster" instead of "Lobster", not using item id for loot, not hitting enter) which with the latest update have been made moot anyways.

 

The other 10% are mostly compromised of the bot not solving randoms correctly.. which is the fault of OSBot not this script, sadly.

 

That said, the script is pretty flawless.. yes there are a few minor things wrong with it, but it was released yesterday.. so it's to be expected.. nothing is wrong that breaks it, though.

 

 

No from personal experience with it.

First time i thought the script was messing up, it was myself not having the latest update, but since then i made sure OS and the script was the latest version before drawing conclusion on the functionality. Also all names and ID's were tripple checked (not that it was the main problem, except once when the script picked 20 food twice from bank). Checklist on first page also followed.

 

Main problem seems to be the pathing (gets stuck at doors) and it rarely works while starting in room (has to start in edgeville bank).

 

 

I dunno why you are having so much trouble with this script tbh... It seems to be working fine for others, and I know it works fine for me.

 

 

Main problem seems to be the pathing (gets stuck at doors) and it rarely works while starting in room (has to start in edgeville bank).

 

Hmm thats odd I started at Edge bank and it had trouble going down the hole in the Barb village.

But when I start the script next to the monsters I select it to fight its flawless.

Script has gotten me from 30-40 ranged very fast and made me about 200k doing the clue scrolls that dropped, and other loot.

Best Combat script on this site IMO...

 

 

thanks. As for the having trouble going down the hole, does it still have trouble with that? I thought I patched that up in a recent release...

Edited July 22, 201312 yr by ericthecmh

1.0.1 is asking for a login and it also adds your ESSMiner to my script library.

 

 

 

I dunno why you are having so much trouble with this script tbh... It seems to be working fine for others, and I know it works fine for me.

 

 

 

I would not say that "its me" that is having troubles with the script, as i have followed the steps you have written on the first page of this thread aswell as updating OS and the script before running it.

 

You have however, updated it perhaps 5 times today? That is more likely to be a cause of issues for users.

 

Now that you are sort of putting the blame on me (for reasons unknown) i have to say that i probably wont be posting more of the bugs i find, because i simply wont use the script any more. Seems to me that your the kind of person who only hears what he wants to hear, wich isnt a good basis for writing good scripts.

 

One last thing before im out: OS already have the account information and other scripts uses that directly, there is no need for a second log in screen in your script.

1.0.1 is asking for a login and it also adds your ESSMiner to my script library.

 

Yah I know, I just consolidated everything together lol.

 

 

 

 

 

I dunno why you are having so much trouble with this script tbh... It seems to be working fine for others, and I know it works fine for me.

 

 

 

I would not say that "its me" that is having troubles with the script, as i have followed the steps you have written on the first page of this thread aswell as updating OS and the script before running it.

 

You have however, updated it perhaps 5 times today? That is more likely to be a cause of issues for users.

 

Now that you are sort of putting the blame on me (for reasons unknown) i have to say that i probably wont be posting more of the bugs i find, because i simply wont use the script any more. Seems to me that your the kind of person who only hears what he wants to hear, wich isnt a good basis for writing good scripts.

 

One last thing before im out: OS already have the account information and other scripts uses that directly, there is no need for a second log in screen in your script.

 

 

Relax buddy, nobody is blaming you. I'm just saying that I haven't been able to reproduce your errors and other people don't seem to have been able to either so I haven't been able to work on it.

 

And sure maybe other scripts do, but I'd like to keep mine separate from OSBot's. As much as I like OSBot, we all know that nothing lasts forever, and other bots will pop up from time to time.