1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Resolved NullPointerException at a.Vn.getProjectedPolygons(cxb:82)

Discussion in 'Client & Site Support' started by Ozzy, Dec 26, 2014.

  1. Ozzy

    Joined:
    Nov 5, 2014
    Messages:
    505
    Likes Received:
    162
    I've never personally encountered this and I run my script bot extensively, but it is showing up in my log.
    I think this has been reported before but I can't find it:

    @Cloud

    Code (Text):
    1. java.lang.NullPointerException
    2.  at a.Vn.getProjectedPolygons(cxb:82)
    3.  at com.runemate.game.api.hybrid.local.hud.CompositeModel.getProjectedPolygons(zub:224)
    4.  at com.runemate.game.api.hybrid.local.hud.Model.contains(ydb:166)
    5.  at a.bL.contains(fqb:12)
    6.  at a.vl.move(sqb:239)
    7.  at com.runemate.game.api.hybrid.input.Mouse.move(ep:234)
    8.  at a.bL.interact(fqb:232)
    9.  at a.bL.interact(fqb:52)
    10.  at scripts.MassFighter.Tasks.CombatHandler.pickupLoot(CombatHandler.java:129)
    11.  at scripts.MassFighter.Tasks.CombatHandler.execute(CombatHandler.java:77)
    12.  at com.runemate.game.api.script.framework.task.TaskScript.onLoop(ebb:148)
    13.  at com.runemate.game.api.script.framework.LoopingScript.run(yhb:89)
    14.  at com.runemate.game.api.script.framework.AbstractScript.start(plb:197)
    15.  at a.sJ.run(clb:102)


     
  2. Best Answer:
    Post #3 by Cloud, Dec 26, 2014
  3. stx21

    Joined:
    Dec 14, 2014
    Messages:
    2
    Likes Received:
    0
    pickupLoot returned null either before or after the script bot attempted to do something with it. ie. click, interact
    check line 129 in CombatHandler that is where the exception was thrown.
     
  4. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    patched in the next release.
     
  5. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    If you follow the stack you can see that the error occurred internally.
     

Share This Page

Loading...