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 don't judge people by how much money they make or bring in. I'm short on time (I've got the least available time of all the devs), so naturally, I'm also the most picky on what I spend my time on. That usually means I only look critical bugs or difficult to fix bugs (per the request of the other devs).

 

 

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.

 

That logic wasn't directed at you and for that, I apologize. I normally could care less about ranks, which is why I actually read your PM. But when it comes down to it, I'm compeled to support scripters before anyone else. Is it ideal? No, but that's just reality when you've got a lot of PMs and have to prioritize.

I don't judge people by how much money they make or bring in. I'm short on time (I've got the least available time of all the devs), so naturally, I'm also the most picky on what I spend my time on. That usually means I only look critical bugs or difficult to fix bugs (per the request of the other devs).

That is 100% fine, but your job is also to relay the message onto someone who has time to fix it.

Edited February 18, 201412 yr by dreamliner

That is 100% fine, but your job is also to relay the message onto someone who has time to fix it.

 

I was under the impression Maxi already knew about it o.o

I was under the impression Maxi already knew about it o.o

The only dev I know that knows about it is you, lol. Could you make sure this problem doesn't get lost in the suffle?

The only dev I know that knows about it is you, lol. Could you make sure this problem doesn't get lost in the suffle?

 

I'll send them a message about it. It'll be up to them to deal with it at that point unless I magically get free time opened up. Tbh, this is why a bug tracker was implemented a long time ago, so that things wouldn't get lost. But it got used like half the time and just died out. If the others used it properly, I'm sure we can implement it again.

 

Edit:

I'm moving this to API Suggestions because that's the only forum where these things don't get lost (as frequently anyways, and that's mainly because thread creation is more restricted, so it doesn't get the usual spam).

Very interesting, I'm surprised this wasn't addressed earlier. Hopefully this will be a priority in OSBot 2.