Resolved java.lang.IllegalArgumentException: Negative position

Discussion in 'Client & Site Support' started by ad0n, Jan 10, 2015.

  1. I'm getting this error on every script bot I try to run. This happens right when the scripts bots start.

    java.lang.IllegalArgumentException: Negative position
    at sun.nio.ch.FileChannelImpl.read(Unknown Source)
    at a.DQA.try(rw:302)
    at a.DQA.try(rw:246)
    at a.hcA.try(rw:367)
    at a.DgA.try(hq:232)
    at a.DgA.try(hq:298)
    at a.SnA.try(otb:72)
    at a.AVA.try(bvb:38)
    at a.SnA.try(otb:223)
    at a.ZkA.try(ldb:97)
    at a.oeA.try(ct:268)
    at com.runemate.game.api.hybrid.entities.definitions.GameObjectDefinition.get(hr:332)
    at a.vXA.getDefinition(oic:113)
    at com.runemate.game.api.hybrid.region.GameObjects$6.accepts(yr:174)
    at com.runemate.game.api.hybrid.region.GameObjects$6.accepts(yr:21)
    at a.lrA$$Lambda$355/817385354.test(Unknown Source)
    at java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
    at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source)
    at java.util.stream.AbstractPipeline.copyInto(Unknown Source)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
    at java.util.stream.AbstractPipeline.evaluate(Unknown Source)
    at java.util.stream.ReferencePipeline.collect(Unknown Source)
    at a.lrA.try(dgc:81)
    at com.runemate.game.api.hybrid.region.GameObjects.getLoaded(yr:223)
    at com.runemate.game.api.hybrid.region.GameObjects.getLoaded(yr:440)
    at ChopNShaft.ChopNShaft.onLoop(ChopNShaft.java:71)
    at com.runemate.game.api.script bot.framework.LoopingScript.run(sf:38)
    at com.runemate.game.api.script bot.framework.AbstractScript.start(sj:116)
    at a.JlA.run(qv:217)

    Thanks.
     
  2. Let's see..

    CP Divination, CP Firemaker, CP Fisher, ChopNShaft, HaxAgility, MassFighter, MaxiFisher, MaxiWoodcutter.
     
  3. It's an error with handling incomplete caches, it'll be resolved for the next update.
     

Share This Page

Loading...