[slashnhax]

Exception in thread "Alpha Agility - redacted" java.lang.NullPointerException 
 at nul.iIIiiIiIiIii.<init>(shb:9) 
 at nul.iIIiiIiIiIii.<init>(shb:177) 
 at nul.IiIIiIiiiiII.run(bbc:102) 
Exception in thread "Alpha Dev Kit - redacted" java.lang.NullPointerException 
 at nul.iIIiiIiIiIii.<init>(shb:9) 
 at nul.iIIiiIiIiIii.<init>(shb:177) 
 at nul.IiIIiIiiiiII.run(bbc:102) 
Exception in thread "Alpha Fighter - redacted" java.lang.NullPointerException 
 at nul.iIIiiIiIiIii.<init>(shb:9) 
 at nul.iIIiiIiIiIii.<init>(shb:177) 
 at nul.IiIIiIiiiiII.run(bbc:102) 
Exception in thread "Example Powerchopper - redacted" java.lang.NullPointerException 
 at nul.iIIiiIiIiIii.<init>(shb:9) 
 at nul.iIIiiIiIiIii.<init>(shb:177) 
 at nul.IiIIiIiiiiII.run(bbc:102) 
Exception in thread "Flag Checker - redacted" java.lang.NullPointerException 
 at nul.iIIiiIiIiIii.<init>(shb:9) 
 at nul.iIIiiIiIiIii.<init>(shb:177) 
 at nul.IiIIiIiiiiII.run(bbc:102) 
Exception in thread "Viewer's Bounds Editor - redacted" java.lang.NullPointerException 
 at nul.iIIiiIiIiIii.<init>(shb:9) 
 at nul.iIIiiIiIiIii.<init>(shb:177) 
 at nul.IiIIiIiiiiII.run(bbc:102)

Spectre was run with sudo java -jar spectre.jar -sdk
All bots except for Viewer's Bounds Editor are local.
 
The exact same error occurs for me on Windows as well.
 
Seems to be a nullpointer related to setting an EmbeddableUI with a property with a null value.

 

[savior]

@Arbiter I find it somewhat insecure that our RS usernames get displayed in every exception.

@SlashnHax if it is related to a null value in the bot interface ObjectProperty, you might aswell just unimplement EmbeddableUI, or alternatively pass new Text("") to represent an empty node.

 

[slashnhax]

@Arbiter I find it somewhat insecure that our RS usernames get displayed in every exception.

@SlashnHax if it is related to a null value in the bot interface ObjectProperty, you might aswell just unimplement EmbeddableUI, or alternatively pass new Text("") to represent an empty node.

I passed in new VBox() to represent the empty node xD
 
I fixed it on Windows by initializing the objectproperty with a new VBox(), the error still occurs on Linux though.

 

[arbiter]

I passed in new VBox() to represent the empty node xD
 
I fixed it on Windows by initializing the objectproperty with a new VBox(), the error still occurs on Linux though.

Please confirm that this problem still persists in the next (unreleased) version, 1.11. I am not sure my latest commit has made it live yet.

@Arbiter I find it somewhat insecure that our RS usernames get displayed in every exception.

@SlashnHax if it is related to a null value in the bot interface ObjectProperty, you might aswell just unimplement EmbeddableUI, or alternatively pass new Text("") to represent an empty node.

I agree that exceptions shouldn't have the RS account, especially considering it'll be sent to the server. @Cloud

 

[cloud]

Please confirm that this problem still persists in the next (unreleased) version, 1.11. I am not sure my latest commit has made it live yet.

I agree that exceptions shouldn't have the RS account, especially considering it'll be sent to the server. @Cloud

The exceptions don't have anything related to the rs account included, the problem is the thread naming is done based on the rs-account name to make debugging purposes either when working on machines running multiple clients at once.

 

[slashnhax]

The exceptions don't have anything related to the rs account included, the problem is the thread naming is done based on the rs-account name to make debugging purposes either when working on machines running multiple clients at once.

Would it be possible to generate some sort of instance id and use that instead? Or could you use the PID for this?

 

[cloud]

Would it be possible to generate some sort of instance id and use that instead? Or could you use the PID for this?

I suppose I can change it to pid - bot name instead of bot name - account name

 

[slashnhax]

Fixed by loading darkscape and then loading rs3 again.
Seems there's an issue with my codebases where it detects my rs3 as darkscape, but since I hadn't run darkscape, it didn't like stuff.

 

[arbiter]

Fixed by loading darkscape and then loading rs3 again.
Seems there's an issue with my codebases where it detects my rs3 as darkscape, but since I hadn't run darkscape, it didn't like stuff.

So what's the resolution on the original issue @SlashnHax @Cloud?

 

[cloud]

The original stack trace has been determined to be fixed when https://www.runemate.com/community/threads/incorrect-game-type-detection.5657 is resolved, so I'm marking this as solved.