I used that as an example, and as do I.

The script was coded to click on the spell ONE time, then click on the NPC. Then go back to the spell and click the NPC. The fact that it missed and couldn't click the spell again would be the script's fault because it doesn't have a failsafe on it. 

When you actually get to debugging everything, you will notice, like I did, that after a certain amount of time unexplainable from my perspective things happen, and only logical explaination would be to say the client is at blame. I have spent a lot of my own time checking how well OSBot's API works, and it fails at a lot of things at the moment to be honest.

 

I am just going to wait for OSBot 2, and see how it works from that point on.

Well in my case, the obfuscation process that your script goes through to reach the SDN could be messing up your scripts. Having bugs which are impossible to recreate using my own local copies, so there is really no way to fix it. Though when I let a user that is having trouble with the SDN version, use a local copy, all of a sudden it works perfect. Its rather annoying.

When you actually get to debugging everything, you will notice, like I did, that after a certain amount of time unexplainable from my perspective things happen, and only logical explaination would be to say the client is at blame. I have spent a lot of my own time checking how well OSBot's API works, and it fails at a lot of things at the moment to be honest.

 

I am just going to wait for OSBot 2, and see how it works from that point on.

This. I receive errors on the dumbest things sometimes for absolutely no reason. My code can literally be click this inventory object, but the script will click everything around it or something weird like that. The scripters are at the mercy of what kind of data the client is reading from the game, and if it is correct or not.

Well in my case, the obfuscation process that your script goes through to reach the SDN could be messing up your scripts. Having bugs which are impossible to recreate using my own local copies, so there is really no way to fix it. Though when I let a user that is having trouble with the SDN version, use a local copy, all of a sudden it works perfect. Its rather annoying.

The thing is. When I see a bug, I tell them what it is and how they could fix it. Considering I don't know JAVA, it would only be a guess on how they would fix it. Because for some reason, you are 'limited' to what you can do apparently. 

The thing is. When I see a bug, I tell them what it is and how they could fix it. Considering I don't know JAVA, it would only be a guess on how they would fix it. Because for some reason, you are 'limited' to what you can do apparently. 

 

If a user reports a problem in which I can recreate, then I will fix it almost immediately. Though in most cases with the bugs I receive, directly deal with how the scripts are handled once in SDN. Also the most bug reports I receive almost make no sense, to the point where I ask myself, "Did I even write a method that does that?"; and in most cases no, it's just a obfuscation bug.

If a user reports a problem in which I can recreate, then I will fix it almost immediately. Though in most cases with the bugs I receive, directly deal with how the scripts are handled once in SDN. Also the most bug reports I receive almost make no sense, to the point where I ask myself, "Did I even write a method that does that?"; and in most cases no, it's just a obfuscation bug.

I wouldn't have a problem if every bug I tried to tell them about says it is the client. And I mean EVERY BUG I have reported they just pushed it off to the side and called it a client issue. If it was the client's issue, I would have reported it under the thread for client issues. When I use scripts, I want them to work perfectly just as much as the person who is writing it. I always give how the bug has happened and in most cases what is causing it. It would take them less then 10-20 minutes to find the error in the coding and fix it. I do understand what it is like when it is coding and you have 20,000+ Lines of code that you have to work with and finding the exact spot where it messes up can be hard at times. But when they go out of their way and do nothing and just say that every single bug is client's issue. Then I have a problem because I just wasted my time explaining the bug and it makes it so I don't want to use their scripts because the next script I use from them, I might have a different problem and they will do nothing about it again. I rarely see any bugs in a script, but when I do I try to help them understand where the bug is, and how it happens. I just want to be able to have a friendly chat about a bug, and within a week or two have it patched. I don't mind if they take a bit to patch it but as long as I see that they aren't just pushing it off and saying that they can't do anything about a simple error that can be fixed if they just took a bit of time to understand what it is and where it comes from pisses me off. 

 

If the writer isn't able to put time into maintaining the script, then they shouldn't be allowed to sell scripts for money, instead it should be free.

Meh i think it's client issues and maybe, I said MAYBE scripters issue. -_-

Guys, noone is saying it's only the scripters fault. We all know verry well that the client is pretty laggy sometime and messes up.

 

BUT

 

If the script would contain some failsaves, the lag could be compensated and would not be a huge deal anymore.

Sure it's more work, but from paid scripts i expect an indestructible built, that can't be messed up with a bit of lagg. and if it ever failes and does something dumb i want it to fix itself.

Do you know how annoyed we get over time? I myself receive close to 10 messages PER DAY as well as posts on my script threads about things that aren't even script related (most of the time randoms). If a user is complaining that something as small as not clicking the right spell happened it's most likely not going to be the #1 priority for us as it barely effects the scripts performance.

 

It was a small issue that could be caused by lag, and it arguably is the clients fault if the scripter thinks there should be a check to make sure everythings alright to do that action located in OSBot the method their using.

You can't rely on the client to handle everything, I get about 50 messages per day on client bugs that are most of the time a script issue(yes it goes the other way around aswell, and a lot more often!), but there's no reason to get anoyed.

And a not 100% flawless working script should be priority number 1 if you actually want to have a decent script, just my 2 cents.

Edited January 26, 201412 yr by Solution

Realistically no bot is perfect. You're going to have many problems because we have a middle man such a Jagex creating issues for us on the daily. I see how bots are created they are limited, but this isn't the excuse that anyone should be using. You're going to have bugs on every script you use some might be minor some might crash the client. The client developers have real things in life to do and they are working on a large project for everyone here to use. So, after a while I think the bot will progress but then again we are only working with limited scripters here.

 

Client issues are always going to be there. They do get fixed but new ones will appear when RuneScape does a large update to cause issues with the bots. Look at the new icons that they added we had a large amount of complaints that scripts weren't working when attempting to run, people would then blame this on the scripter because it's there fault yes and no, because this would need to be added into the API where the scripters can move on from. Someone correct me if I'm wrong here.

I have been coding in a different language for 5+ years. I just don't know JAVA. I would love to learn but I have to spend time on other things now.

I am talking about when it is a REAL Bug on a script that can easily be fixed and that does affect the script.

 

If you know OOP design and coding then the language doesn't really matter, that's just a matter of briefly familiarizing yourself with Java's syntax and libraries and the slight differences between languages, so I don't consider your excuse valid (i.e. I do know Java, I'm now taking a course which uses C#, and I've had no trouble transitioning). Anyways, yes, scripts should contain failsafes in case of lag or whatever. A lot of scripts are based around "tell the bot to do this. The bot says it did it. Let's move on." You're blaming scripters for making the assumption that the bot performs what it says it will when it returns to the client that it did so. And as other people have said, SDN scripts =/= what a scripter sees when he or she develops and tests their scripts locally. Basically, your complaint could be partially resolved by scripters creating their own hooks and methods by themselves. Then there's the error in translation which occurs during the local script -> SDN script process, which I know nothing about. I would just say, for you to place so much blame on the scripter is misguided.

Why botters on OSBot fail:

 

1. They think that when they get banned it's the scripter's fault for not including enough anti-ban.

2. They think that anti-ban holds precedence over their idiotic botting habits such as suicide botting at a popular botting spot.

3. Many of them try and tell the scripter what they need to do to fix problems using their deluded pseudo code 
(one time a user told me to use "strings" for rocks instead of "ids", little does he know that all rocks wheter runite or tin are all called "rocks").

4. They think scripts are made overnight.

5. They will frequently try scripting only to release terrible scripts because they have no knowledge in programming.

6. They think that randoms are handled by the script.

7. When a hook or method is broken on an RS Update, they scream and chargeback scripters because they think it's the script's fault.

8. They don't read client debugs

9. They don't read instructions on how to use the script on the script topic, instead they make a post stating that it doesnt work. One example is where to start a script and/or required items.

10. They have a limited knowledge of Runescape outside Lumbridge and Varrock and any scripts that require a quest will never be as popular as a flax picker or bow stringer.

 

Why botters on OSBot fail:

 

1. They think that when they get banned it's the scripter's fault for not including enough anti-ban.

2. They think that anti-ban holds precedence over their idiotic botting habits such as suicide botting at a popular botting spot.

3. Many of them try and tell the scripter what they need to do to fix problems using their deluded pseudo code 

(one time a user told me to use "strings" for rocks instead of "ids", little does he know that all rocks wheter runite or tin are all called "rocks").

4. They think scripts are made overnight.

5. They will frequently try scripting only to release terrible scripts because they have no knowledge in programming.

6. They think that randoms are handled by the script.

7. When a hook or method is broken on an RS Update, they scream and chargeback scripters because they think it's the script's fault.

8. They don't read client debugs

9. They don't read instructions on how to use the script on the script topic, instead they make a post stating that it doesnt work. One example is where to start a script and/or required items.

10. They have a limited knowledge of Runescape outside Lumbridge and Varrock and any scripts that require a quest will never be as popular as a flax picker or bow stringer.

Well said.

I can't speak for all the scripters here, but when I say something is a client-related bug, then it IS a client-related bug. Like recently the method for checking if an NPC is user attack stopped working. Not much I can do unless I hook the fields and shit myself. Considering I'm a scripter and not a developer this isn't my responsibility. so I inform my users to wait for the admins to fix the problem.