Resolved Nullpointer

Discussion in 'Client & Site Support' started by Defeat3d, Jan 12, 2015.

  1. Code (Text):
    1. java.lang.NullPointerException
    2.  at a.Vn.int(tkb:264)
    3.  at a.Vn.int(tkb:68)
    4.  at a.Vn.int(tkb:263)
    5.  at a.iL.int(oob:235)
    6.  at a.iL.int(oob:30)
    7.  at com.runemate.game.api.hybrid.Projection.coordinateToMinimap(rnb:118)
    8.  at com.runemate.game.api.hybrid.location.Coordinate$MinimapCoordinate.isVisible(bqb:1050)
    9.  at com.runemate.game.api.hybrid.location.navigation.basic.BresenhamPath.getNext(dvb:201)
    10.  at com.runemate.game.api.hybrid.location.navigation.basic.BresenhamPath.step(dvb:92)
    11.  at com.runemate.game.api.hybrid.location.navigation.Path.step(owb:70)
    12.  at productions.coconut.divination.tasks.ConvertXp.execute(ConvertXp.java:22)
    13.  at productions.coconut.api.framework.DTaskScript$$Lambda$368/157242455.accept(Unknown Source)
    14.  at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown Source)
    15.  at java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
    16.  at java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
    17.  at java.util.stream.AbstractPipeline.copyInto(Unknown Source)
    18.  at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
    19.  at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)
    20.  at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown Source)
    21.  at java.util.stream.AbstractPipeline.evaluate(Unknown Source)
    22.  at java.util.stream.ReferencePipeline.forEach(Unknown Source)
    23.  at productions.coconut.api.framework.DTaskScript.onLoop(DTaskScript.java:63)
    24.  at com.runemate.game.api.script.framework.LoopingScript.run(mqb:88)
    25.  at com.runemate.game.api.script.framework.AbstractScript.start(zvb:230)
    26.  at a.rJ.run(fcb:191)
     
  2. @Cloud please fix. I needs it. <3
     
  3. I ran the script bot for about an hour yesterday and was unable to reproduce this issue. Perhaps it was fixed by a prior change. Please confirm the resolution of this issue.
     
  4. Still happening on multiple of my bots.
     
  5. Confirmed.
     
  6. resolved.
     
  7. will a new version be released with the influx of recent problems?
     
  8. Hey, this is the thing that you said wasn't on your end. Perhaps I should have only put the Caused-by.
     
  9. Minor builds have been released.
    It was caused by a broken hook, so a server issue not a client one.
     

Share This Page

Loading...