why you no use custom interact methods?

jk, .interact(null);

Wouldn't that throw an NPE? :p

 

My issue involves both clicking on the inventory item (which it doesn't do for some reason even though it will move the mouse over the item) and clicking on the object itself.

why you no use custom interact methods?

I'm not wasting my time making custom things for this shit bot anymore.

Wouldn't that throw an NPE?

 

My issue involves both clicking on the inventory item (which it doesn't do for some reason even though it will move the mouse over the item) and clicking on the object itself.

I'm not wasting my time making custom things for this shit bot anymore.

No NPE's here. Osbot has it built so if string is null it picks the first one. It's in their doc's somewhere

see http://osbot.org/osbot2_api/org/osbot/rs07/api/util/ItemContainer.html#interactWithNameThatContains(java.lang.String, java.lang.String...)

Edited June 7, 201411 yr by dreamliner

No NPE's here. Osbot has it built so if string is null it picks the first one. It's in their doc's somewhere

see http://osbot.org/osbot2_api/org/osbot/rs07/api/util/ItemContainer.html#interactWithNameThatContains(java.lang.String, java.lang.String...)

This was the first thing I tried when 2.14 came our and since 2.14 .interact(null) throws an NPE.

This was the first thing I tried when 2.14 came our and since 2.14 .interact(null) throws an NPE.

 

 

Why would they even change something like that? It still works fine for interacting with inventory items

Why would they even change something like that? It still works fine for interacting with inventory items

 

Yeah interacting with inventory items/ entities directly it will work, but when using an item on an entity it has a seizure.