Resolved ArrayIndexOutOfBounds

@Cloud possibly a client bug.
(09:18:19) java.lang.ArrayIndexOutOfBoundsException
(09:18:19) at java.lang.reflect.Array.get(Native Method)
(09:18:19) at a.al.byte(ywb:131)
(09:18:19) at a.Gl.getComponent(whb:64)
(09:18:19) at com.runemate.game.api.hybrid.local.hud.interfaces.Interfaces.getAt(dwb:52)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.interfaceNext(RaysNatRunner.java:364)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.repairNPC(RaysNatRunner.java:343)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.repairNPC(RaysNatRunner.java:328)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.repairNPC(RaysNatRunner.java:328)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.repairNPC(RaysNatRunner.java:313)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.checkPouches(RaysNatRunner.java:197)
(09:18:19) at com.raymondbl.runemate.natRunner.RaysNatRunner.onLoop(RaysNatRunner.java:124)
(09:18:19) at com.runemate.game.api.script bot.framework.LoopingScript.run(yhb:89)
(09:18:19) at com.runemate.game.api.script bot.framework.AbstractScript.start(plb:197)
(09:18:19) at a.sJ.run(clb:102)

Lines 362 - 373 of my code:

Code (Text):

1.  
2.     public boolean interfaceNext(int i, int k, int m)
3.     {
4.         if(Interfaces.getAt(i, k, m) != null)         //error occuring here
5.         {
6.             if(Interfaces.getAt(i, k, m) != null)
7.             {
8.                 return Interfaces.getAt(i, k, m).click();
9.             }
10.             else return true;
11.         }
12.         else return false;
13.     }
14.  

Line 343, which calls the method above:

Code (Text):

1. interfaceNext(88, 6, 14);

I double-checked. The Development Toolkit indeed lists the Dark Mage InterfaceComponent from the lunar spell Contact NPC as [88, 6, 14].

edit: I also tried [88, 5, 14], which came out with the same error.

 

RS3.

 

Weird. I take it that means that the adjustment, while preventing an exception, will not allow the script bot to obtain the interfaceComponent I'm looking for because my index isn't valid. We'll see when the update rolls out.

 

Thanks. I originally started used specific indices because the yellow button in character dialogue doesn't have text. I now realize the Texture ID stays the same for EOC and Legacy Mode and thus, can be used in a dynamic query's filter.

 

I don't get it.