Resolved Keep getting error no matter what bot i run

Discussion in 'Client & Site Support' started by freddy, Dec 30, 2014.

  1. java.lang.IllegalArgumentException: The cache file must exist.
    at a.Mf.<init>(plb:124)
    at a.vj.<init>(bgb:192)
    at a.vJ.<init>(ki:16)
    at a.vJ.<init>(ki:228)
    at a.vJ.<init>(ki:112)
    at a.yL.enum(tvb:201)
    at com.runemate.game.api.hybrid.entities.definitions.GameObjectDefinition.get(yeb:150)
    at a.pn.getDefinition(yxb:258)
    at com.runemate.game.api.hybrid.region.GameObjects$5.accepts(cnb:100)
    at com.runemate.game.api.hybrid.region.GameObjects$5.accepts(cnb:223)
    at com.runemate.game.api.hybrid.region.Banks$3.accepts(frb:64)
    at com.runemate.game.api.hybrid.region.Banks$3.accepts(frb:146)
    at a.gN$$Lambda$353/8538983.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.gN.enum(ggb:241)
    at com.runemate.game.api.hybrid.region.GameObjects.getLoaded(cnb:115)
    at com.runemate.game.api.hybrid.region.Banks.getLoadedBankBooths(frb:26)
    at com.runemate.game.api.hybrid.region.Banks.getLoaded(frb:65)
    at com.runemate.game.api.hybrid.region.Banks.getLoaded(frb:192)
    at com.runemate.game.api.hybrid.local.hud.interfaces.Bank.open(vwb:228)
    at com.runemate.api.tasks.Banker.execute(Banker.java:126)
    at com.runemate.game.api.script bot.framework.task.TaskScript.onLoop(njb:16)
    at com.runemate.game.api.script bot.framework.LoopingScript.run(tjb:225)
    at com.runemate.game.api.script bot.framework.AbstractScript.start(yfb:13)
    at a.GK.run(yhb:130)
    I keep getting this error can anyone help me?
     
  2. I believe this is fixed in the next release.
     

Share This Page

Loading...