They always say EVERYTHING is the client's issue.

 

I have tried to explain to explain some key points within a few scripts that mess up on the scripting side, and they say it is the client's issue. It truly isn't. There are times when a script fails because of a small bug that you didn't hear about because it is impossible to iron out every single bug in a script. It is impossible. But this does not give them the right to go around and saying that everything is the client's issue.

 

 

I have tried the the mage stunner script. I was watching it and I noticed a bug within the script. If it doesn't click on the correct spell the first time, it will just hover over the spell and not click it. Thus not letting random's activate because of the script.

 

There are tons of small bugs like this in every script that needs to get ironed out. And I do understand that it takes some time to fix it and it isn't an overnight issue. If I went onto a different site for botting, and there was an issue, they would understand and say sorry and have it fixed. Not give an excuse that lets them just sit there and do nothing.

 

 

 

I am not attacking anyone in osbot, I simply want to let others know that not everything is the client's issue. There might have been a small update that broke the script in 1 small area and when it had to do that 1 small thing, it made the script break. But I have been trying to get script writers to listen to what I have had to say since the first script had a bug that needed to be fixed. I don't go around posting things on the thread for the script if it is a client issue. I know when it is the client's issue and script issue. 

 

 

 

 

The correct way to deal with client bugs is to fix them in your script

When you understand and are capable of scripting yourself, you can tell scripters whether or not they're wrong, or that they suck.

 

No one cares about your ignorant opinion.

The correct way to deal with client bugs is to fix them in your script

Good advise here.  Also it is true, it often is the clients fault.  But the reason why the have not been updating the client at all is because they've been spending all their time on osbot 2.  We shall see if it is worth the wait or not so soon.

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.

i would say 50/50

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.

LOL! As if 10 messages is a lot. Get over it broski, you write a script and have it paid you better know you're gonna be answering many questions during the day.

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.

Well said.

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.

They always say EVERYTHING is the client's issue.

 

I have tried to explain to explain some key points within a few scripts that mess up on the scripting side, and they say it is the client's issue. It truly isn't. There are times when a script fails because of a small bug that you didn't hear about because it is impossible to iron out every single bug in a script. It is impossible. But this does not give them the right to go around and saying that everything is the client's issue.

 

 

I have tried the the mage stunner script. I was watching it and I noticed a bug within the script. If it doesn't click on the correct spell the first time, it will just hover over the spell and not click it. Thus not letting random's activate because of the script.

 

There are tons of small bugs like this in every script that needs to get ironed out. And I do understand that it takes some time to fix it and it isn't an overnight issue. If I went onto a different site for botting, and there was an issue, they would understand and say sorry and have it fixed. Not give an excuse that lets them just sit there and do nothing.

 

 

 

I am not attacking anyone in osbot, I simply want to let others know that not everything is the client's issue. There might have been a small update that broke the script in 1 small area and when it had to do that 1 small thing, it made the script break. But I have been trying to get script writers to listen to what I have had to say since the first script had a bug that needed to be fixed. I don't go around posting things on the thread for the script if it is a client issue. I know when it is the client's issue and script issue. 

I sort of agree..I would suggest all scriptwriters who have their scripts on sale to keep them updated,since we are paying for them.As for the free scripts its their choice whether they wanna fix script or not.

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.

What is your definition of a "real bug"?

 

Just because it can be fixed in a script, doesn't mean it is a script bug; it could be a API bug.

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.

 

Ok, so check to make sure the spell is selected before it does anything else?

 

Most of the time I don't even use Osbot's interact functions because they're so buggy.  I find the rectangle for the interface child, create a mouse destination, move the mouse to that destination, check to make sure the mouse is in the destination, then click.  After that I check to make sure the first Option is use or cast or whatever it should be.

 

You can fix so many of the bugs just by doing most things this way.

Edited January 26, 201412 yr by dreamliner

LOL! As if 10 messages is a lot. Get over it broski, you write a script and have it paid you better know you're gonna be answering many questions during the day.

If the questions are retarded and wouldn't be asked if you knew anything about what the client is supposed to handle and what not, then no I'm not going to answer you.

I sort of agree..I would suggest all scriptwriters who have their scripts on sale to keep them updated,since we are paying for them.As for the free scripts its their choice whether they wanna fix script or not.

When I post something on the thread of a script, it is the script's bug.

 

When I post something about the client,  it is the client's bug.

 

 

 

I do understand their pain of not having people understand what is the client's issue and script's issue. When I was coding for a game, I had tons of people who didn't know what a Boolean is pming me about bugs. But they where legit bugs. It did get annoying when you receive 500+ PM's a day and have to read through them and most of them are about bugs that you are working on and other bugs that came up.

Ok, so check to make sure the spell is selected before it does anything else?

 

Most of the time I don't even use Osbot's interact functions because they're so buggy.  I find the rectangle for the interface child, create a mouse destination, move the mouse to that destination, check to make sure the mouse is in the destination, then click.  After that I check to make sure the first Option is use or cast or whatever it should be.

 

You can fix so many of the bugs just by doing most things this way.

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