[superbotter]

java.lang.NullPointerException
 at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
 at nul.iiIiIIiiiiiI.enum(dqb:153)
 at nul.iiIiIIiiiiiI.byte(dqb:139)
 at com.runemate.game.api.hybrid.Environment.getGameType(vpb:92)
 at com.runemate.game.api.hybrid.Environment.isRS3(vpb:231)
 at com.runemate.game.api.hybrid.RuneScape.isLoggedIn(crb:31)
 at nul.iiiIiIiiIIII.run(frb:130)
RuneMate v2.4.0.2 - SuperFisher v0.2.1 - RS3 5FCEC9 - Windows 7 - Java8u92 x86 (Oracle Corporation)

I've been getting the above error message in my exception logs since RuneMate v2.4.0 iirc (I'm almost certain that none of these came before v2.4.0), and as I'm working on my bots again, I decided to report it here. Is this error due to something on my end (my SuperFisher/SuperMiner code I mean), or is it a RuneMate bug? I can't tell from the error message.

 

[awesome123man]

java.lang.NullPointerException
 at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
 at nul.iiIiIIiiiiiI.enum(dqb:153)
 at nul.iiIiIIiiiiiI.byte(dqb:139)
 at com.runemate.game.api.hybrid.Environment.getGameType(vpb:92)
 at com.runemate.game.api.hybrid.Environment.isRS3(vpb:231)
 at com.runemate.game.api.hybrid.RuneScape.isLoggedIn(crb:31)
 at nul.iiiIiIiiIIII.run(frb:130)
RuneMate v2.4.0.2 - SuperFisher v0.2.1 - RS3 5FCEC9 - Windows 7 - Java8u92 x86 (Oracle Corporation)

I've been getting the above error message in my exception logs since RuneMate v2.4.0 iirc (I'm almost certain that none of these came before v2.4.0), and as I'm working on my bots again, I decided to report it here. Is this error due to something on my end (my SuperFisher/SuperMiner code I mean), or is it a RuneMate bug? I can't tell from the error message.

@SlashnHax says it will be fixed in next runemate update. it's a client bug.

 

[superbotter]

@SlashnHax says it will be fixed in next runemate update. it's a client bug.

Thanks for telling me this

 

[slashnhax]

To clarify, it's an error that has replaced the "You cannot call for client information on a non-bot thread" exception because of a change that I made. It will be fixed in the next update, and the proper error will be thrown instead

 

[savior]

To clarify, it's an error that has replaced the "You cannot call for client information on a non-bot thread" exception because of a change that I made. It will be fixed in the next update, and the proper error will be thrown instead

So non-game-accessing methods like Environment.getBot() will be allowed on concurrent threads?

 

[slashnhax]

So non-game-accessing methods like Environment.getBot() will be allowed on concurrent threads?

If they're on a thread associated with the bot, then they will be allowed. Environment.getBot() will still not be allowed on a System thread such as the JavaFX Platform thread due to that thread not being associated with the bot.