I've tried to contact the developers about so many issues, but I guess OSBot 2 is their top priority right now. Kinda sad how their attempting to make a number 2 when they can't even get 1 working.

 

Maybe OSBot 2 is a perfected version of 1? Although, many releases of 2 but not that flawless. Let's just hope these issues resolved soon!

 

support, developers are being hard headed and need to fix this.

supp

I talked about this with Maxi like 2 months ago, he said he would look into it xd

I talked about this with Maxi like 2 months ago, he said he would look into it xd

So were screwed

support 

Zach responded to my PM and asked me for proof this is happening.

Ok then.

and.. this is how a human follows the object

Your turn @Zach

Edited February 17, 201412 yr by dreamliner

The clips just show that it isn't broken. Glitched sure, broken no.

If you're going to send a PM that says something is broken when it isn't, you're just losing credibility and wasting my time looking at it when there are bigger issues to deal with.

Also, if you send me a private message, I expect the conversation to continue there and not end with "your move". Because my move at this moment is the same as it was when you send the first PM. Your proof is just proof for my point and I still don't see an immediate issue.

The clips just show that it isn't broken. Glitched sure, broken no.

If you're going to send a PM that says something is broken when it isn't, you're just losing credibility and wasting my time looking at it when there are bigger issues to deal with.

Also, if you send me a private message, I expect the conversation to continue there and not end with "your move". Because my move at this moment is the same as it was when you send the first PM. Your proof is just proof for my point and I still don't see an immediate issue.

When something doesn't work the way it's supposed to, it's broken. 'Glitch' is derived from broken.

I also said that because you questioned my credibility. Two can play at this game.

On a more serious note, the fundamentals are what speaks for your bot. Miss clicks are part of the fundamentals. If the bot can't even click properly, what assures me other things in the bot are going to work properly too? Please do all of us fellow scripters a favor a listen to what we want fixed, instead of devoting all of your time to fixing something which won't be fully released for a few months. I'm not telling you how to run your business, but maintaining the thing that makes you money should be precedence.

But what do I know.

Edited February 18, 201412 yr by dreamliner

When something doesn't work the way it's supposed to, it's broken. 'Glitch' is derived from broken.

I also said that because you questioned my credibility. Two can play at this game.

On a more serious note, the fundamentals are what speaks for your bot. Miss clicks are part of the fundamentals. If the bot can't even click properly, what assures me other things in the bot are going to work properly too? Please do all of us fellow scripters a favor a listen to what we want fixed, instead of devoting all of your time to fixing something which won't be fully released for a few months. I'm not telling you how to run your business, but maintaining the thing that makes you money should be precedence.

But what do I know.

 

Because I doubted that it was "broken". And I still don't consider it broken. Yea, it could use improvements, but there are things higher on my priority list than this. And "broken" simply sets off unnecessary alarms and uses my time (checking the problem) when it could have been better spent on an actual urgent problem.

Because I doubted that it was "broken". And I still don't consider it broken. Yea, it could use improvements, but there are things higher on my priority list than this. And "broken" simply sets off unnecessary alarms and uses my time (checking the problem) when it could have been better spent on an actual urgent problem.

I am not a scripter, but I see they are frustrated giving the analogy that they are given tools, and these inefficient tools are plastic. and makes it very hard for them. arguing over the difference between a glitch and being broken seems very immature when you could just accept it is inefficient and needs work.

That being said you are amazing, the fact that you can code a client Iv'e been told it takes insane amount of work but you are not being amazing now, atm you are being hardheaded.

Support!

I am not a scripter, but I see they are frustrated giving the analogy that they are given tools, and these inefficient tools are plastic. and makes it very hard for them. arguing over the difference between a glitch and being broken seems very immature when you could just accept it is inefficient and needs work.

That being said you are amazing, the fact that you can code a client Iv'e been told it takes insane amount of work but you are not being amazing now, atm you are being hardheaded.

 

Well, when I've got 2 bugs in my inbox that demand my immediate attention. This report is taking up time that doesn't need to be taken up right now. I'm not saying this isn't important, I'm just saying it isn't as important as other matters I'm tending to. And yes, they're bugs scripters are actually moaning about. I've gotten 1 PM about this bug (from a non-scripter/the OP). On the other hand, 5 messages from scripters about a different bug. Which one do you think I'm going to deal with first? Hint, it isn't going to be this one unless it actually was broken. The broken part obviously made sure that I verified parts of it to ensure that it wasn't broken.

You're looking at it from a user standpoint, where priority doesn't matter. At this level, priority is everything when PMs flood your inbox with requests (hence why most PMs get deleted). Then it really does matter because spending time looking at something that didn't need to be looked at right away takes time away from something else. If you still think I'm "hardheaded", then I'd rather stay that way so that the most critical issues get dealt with first. Instead of turning everything into a popularity contest or spam the dev contest.

Also, I didn't write most of OSBot 1 or 2, so I shouldn't get that much credit for it.

@@Dreamliner

I think I quick workaround you could just do in the meantime would be writing your own interacting method. Simply detecting whether the player is moving (to set the mouse speed higher or not) and clicking in a small rectangle (by grabbing the bounding box and creating a tiny rectangle inside of it) should fix any issues you're currently having.

I apologize for the inconvenience, but this has been a problem for quite some time.

I have no idea what your list looks like, but this needs to be fixed. There are quite a few of official scripters and sdn scripters who have replied to this thread. That can't be everyone who has been disrupted with this 'glitch' either.

Once this clicking issue is fixed, we will see a huge increase in efficiency from most bots. It also looks more human like, which could potentially reduce bans. Humans become more efficient as they learn what they are doing. Even though you don't do the math consciously, you're estimating where the object you're focusing on will end up by the estimated time it will take your mouse to get there. By the time OSBot has calculated this, the object has already moved and results in a misclick.

I may not have the respect from you because I don't bring in OSBot money, but I would greatly appreciate it if you could fix this problem for the benefit of the community as a whole.

I've gotten 1 PM about this bug (from a non-scripter/the OP). On the other hand, 5 messages from scripters about a different bug. Which one do you think I'm going to deal with first?

Well, I'm never going to release any of my scripts now from that logic.

I may be a non-scripter (rank), but I sure as hell have more knowledge of programming as a whole than most of the scripters on this site.

That was incredibly disheartening, I'm sorry.

Edited February 18, 201412 yr by dreamliner