Mirror client version: 
Mirror version: 2.5
OSBot version: 2.5.8

Console output / terminal output:
java.lang.ArrayIndexOutOfBoundsException: -5177
    at org.osbot.rs07.api.NPCS.getLocalNPC(fe:1)
    at org.osbot.rs07.api.Mouse.getEntitiesOnCursor(hi:416)

Crash report if a crash occurred

Script that you ran:
FrostBarrows

Hooks that failed:
Probably XClient#getOnCursorUids

JVM/Browser bit version (32 / 64):
32

someone help this poor man already!

This has a big impact on the GP/hr using FrostBarrows with mirror mode

Can we get an ETA on this? 

Is getting fixed, fix will be in the next release

Thank you!! 

Was this fixed? 

I keep getting this:

[INFO][Bot #1][12/10 03:34:43 PM]: DEBUG: Targeting enemy
[ERROR][Bot #1][12/10 03:34:44 PM]: Error in script executor!
java.lang.ArrayIndexOutOfBoundsException: -8253
    at org.osbot.rs07.api.NPCS.getLocalNPC(dn:178)
    at org.osbot.rs07.api.Mouse.getEntitiesOnCursor(tj:401)
    at frostbarrow.b.Prn.e(cc:465)
    at frostbarrow.e.Com3.D(dc:625)
    at frostbarrow.e.Com3.M(dc:122)
    at frostbarrow.FrostBarrow.onLoop(td:139)
    at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(bp:22)
    at java.lang.Thread.run(Unknown Source)

4 hours ago, CSGOslave said:

Was this fixed? 

I keep getting this:

[INFO][Bot #1][12/10 03:34:43 PM]: DEBUG: Targeting enemy
[ERROR][Bot #1][12/10 03:34:44 PM]: Error in script executor!
java.lang.ArrayIndexOutOfBoundsException: -8253
    at org.osbot.rs07.api.NPCS.getLocalNPC(dn:178)
    at org.osbot.rs07.api.Mouse.getEntitiesOnCursor(tj:401)
    at frostbarrow.b.Prn.e(cc:465)
    at frostbarrow.e.Com3.D(dc:625)
    at frostbarrow.e.Com3.M(dc:122)
    at frostbarrow.FrostBarrow.onLoop(td:139)
    at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(bp:22)
    at java.lang.Thread.run(Unknown Source)

Seems this bug is back. I added something to the API that hopefully resolves this. Next release will have it

1 hour ago, Patrick said:

Seems this bug is back. I added something to the API that hopefully resolves this. Next release will have it

Thank you so much Patrick!

15 hours ago, Patrick said:

Seems this bug is back. I added something to the API that hopefully resolves this. Next release will have it

My Man! ?

This is still not fixed...

I'll have another look into it

49 minutes ago, Patrick said:

I'll have another look into it

Thank you man