[phasecoder]

http://pastebin.com/YHUbEgKb

what is that all; about?

 

[botmagic]

same here, looks like .interact() is not working :/ at least this is what causes the error in my script

edit: not just .interact(),almost everything...

 

[phasecoder]

starts off this

Exception in thread "Bot-Phase OS Fletcher" (12:13:16) java.lang.StackOverflowError
(12:13:16)     at sun.awt.Win32GraphicsConfig.getBounds(Native Method)
(12:13:16)     at sun.awt.Win32GraphicsConfig.getBounds(Unknown Source)
(12:13:16)     at com.runemate.game.api.hybrid.local.Screen.getPhysicalBounds(axb:116)

 

[aidden]

@Cloud

 

[cloud]

starts off this

Exception in thread "Bot-Phase OS Fletcher" (12:13:16) java.lang.StackOverflowError
(12:13:16)     at sun.awt.Win32GraphicsConfig.getBounds(Native Method)
(12:13:16)     at sun.awt.Win32GraphicsConfig.getBounds(Unknown Source)
(12:13:16)     at com.runemate.game.api.hybrid.local.Screen.getPhysicalBounds(axb:116)

wtf... that error is coming from within the jre itself.

 

[phasecoder]

So is this my end or yours?
I cant get a script to run in osrs.

 

[slashnhax]

Happens with me for RS3, haven't tried OSRS. It was working fine last night on Beta 75

 

[phasecoder]

Happens with me for RS3, haven't tried OSRS. It was working fine last night on Beta 75

Iv deleted all substance of runemate even the .jar and re downloaded no luck what so ever

 

[hitchthosecocks]

try reinstalling java?

 

[philosobyte]

try reinstalling java?

Hm, so only some people are having this problem? Because I'm getting it now, too.

 

[phasecoder]

the script was working fine before #76 update

 

[aidden]

So i've been running a script for maybe 5 hours today. Just reloaded the client and now i'm getting the same thing. Even though i was already on 76 :/

 

[botmagic]

solution:
remove -login argument

you're welcome

 

[aidden]

solution:
remove -login argument

you're welcome

Confirmed. Something is up with the autologin @Cloud
I left the arg there but when it asks me to re-enter my tfa i have no problem, when it autologs the error is back

 

[cloud]

Should be resolved as of beta 76.2