Since I've been testing my script I'd notice alot of client bugs and instead of bitching to myself I'd rather post them down here

 

• Position.interact() will sometimes not click, OR some will click then clicks on the spot on the minimap
• Object.interact() will sometimes not click
• Drill Demon random(Or whatever is called) did not call when I was sent to that random
• Run away of combat is buggy at times, this occurred however when in Warrior's guild killing animated armour, would run away all the way outside the guild and not come back
• client.getInventory().interact("Item", "Interaction") will sometimes CLICK the item instead of right click, in my scenario it forced to equip gear when not intended to. This however is relatively rare but still occurs
• I don't know if I should post it as a bug but there are quite a few objects that aren't correctly modeled thus causing the client to sometimes miss-click it
• Will attack monster when it's @ 0 health, this is still occurring in .86

That's all I got so far, thanks

hope its fixed soon:)

Will attack monster when it's @ 0 health, this is still occurring in .86

Do you know which method/scripts this happens in?

 

Run away of combat is buggy at times, this occurred however when in Warrior's guild killing animated armour, would run away all the way outside the guild and not come back

Is there something special about this place that could cause it?

Do you know which method/scripts this happens in?

 

 

Is there something special about this place that could cause it?

 

Interacting with an NPC, NPC.interact("Attack"). Unless I've been doing it wrong all this time

 

Also regarding warrior guild is probably the amount of doors in such a small area, the rooms are very small however they're only doors and running far away is doable, better safe than sorry. Issue would be that it wouldn't run back

 

Interacting with an NPC, NPC.interact("Attack"). Unless I've been doing it wrong all this time

What method was used to generate the list of NPCs? Because I don't think interact() checks if it's attackable.

Also regarding warrior guild is probably the amount of doors in such a small area, the rooms are very small however they're only doors and running far away is doable, better safe than sorry. Issue would be that it wouldn't run back

So, it gets stuck because of doors being closed or what o.o?

What method was used to generate the list of NPCs? Because I don't think interact() checks if it's attackable.

So, it gets stuck because of doors being closed or what o.o?

closestNPCListForName(String... names)

 

I used this, and I have the problem of Interacting while dying/0hp.

What method was used to generate the list of NPCs? Because I don't think interact() checks if it's attackable.

So, it gets stuck because of doors being closed or what o.o?

 

RS2Object org.osbot.script.MethodProvider.closestObjectForName(String... arg0)

 

And I'm not sure, it might be as the door automatically closes once you go through it but it wouldn't even display on the log that the script would attempt to run back

closestNPCListForName(String... names)

 

I used this, and I have the problem of Interacting while dying/0hp.

Well, that's not really a bug since the NPC still exists, so it should be found by closestNPCListForName().

Well, that's not really a bug since the NPC still exists, so it should be found by closestNPCListForName().

 

Ah alright, thanks for clearing that up Zach

Well, that's not really a bug since the NPC still exists, so it should be found by closestNPCListForName().

Is it possible to prevent clicking dying NPCs though? #interact clicks occasionally while the NPC dies which gets a little annoying. Although I've fixed that issue.

Is it possible to prevent clicking dying NPCs though? #interact clicks occasionally while the NPC dies which gets a little annoying. Although I've fixed that issue.

I don't see why preventing you from using interact("Attack") would solve anything when it should be the script that decides when you can interact. If the script tells the bot client to click attack on the NPC, then the bot should click attack on the NPC. It's the KISS principle at work, if you really want to make a ton of exceptions, you can, but that leads to complex behavior that could have been avoided by a one line check by the script.

In short, no it's not going to be changed. If the script tells the bot to do something, the bot is not going to pretend it didn't receive the order and do nothing.

Is it possible to prevent clicking dying NPCs though? #interact clicks occasionally while the NPC dies which gets a little annoying. Although I've fixed that issue.

 

Wait, that's the issue I was addressing. Is it cause I'm using the wrong method or not? It's easy to fix but just thought I'd mention the bug

Well, I'm thoroughly confused now, so, what's the actual bug o.O

I don't see why preventing you from using interact("Attack") would solve anything when it should be the script that decides when you can interact. If the script tells the bot client to click attack on the NPC, then the bot should click attack on the NPC. It's the KISS principle at work, if you really want to make a ton of exceptions, you can, but that leads to complex behavior that could have been avoided by a one line check by the script.

In short, no it's not going to be changed. If the script tells the bot to do something, the bot is not going to pretend it didn't receive the order and do nothing.

 

Looking at it from that point of view you're very much right as the solution to it is very simple so why complicate things. Thanks

Why don't you guys just use closestAttackableNPCForName()....

 

Works fine for me

Edited March 2, 201412 yr by Swizzbeat