@Cloud
I thought I would make a new thread to keep these all in one place.
java.util.ServiceConfigurationError: com.sun.tools.attach.spi.AttachProvider: Provider sun.tools.attach.WindowsAttachProvider could not be instantiated
javafx.fxml.LoadException:
/Users/John/RuneMate/temp/764414809.res...
On os x:
java.util.ServiceConfigurationError: com.sun.tools.attach.spi.AttachProvider: Provider sun.tools.attach.WindowsAttachProvider could not be instantiated
java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/darwin/libjnidispatch.jnilib) not found in resource path...
This looks like the same issue that was happening in the old client with the flickering canvas. I think it was printing the same message, I just assumed you guys knew about it.
Using os x, the Reviews section flickers a crap ton and is printing this exception:
Exception in thread "JavaFX Application Thread" netscape.javascript.JSException: TypeError: null is not an object (evaluating 'document.getElementById('root').offsetHeight')
at...
As far as I know, that goes through OSBuddy, and I'm not sure the communication method that that uses to get/send info to the client is the same. But I would guess it is somewhat similar.
Oh Fuck, the alpha has started. :)
Since Spectre has not been released yet, how could he be using it? You do realize that the new version uses a completely different method to interact with RS.
There is no real metric for detectability. That being said, spectre uses the official RuneScape client so there is nothing for them to detect without scanning all of your running processes to find the additional (and separate) JVM.
Try lowering your mouse multiplier in the client settings.
I have an open issue about this. I might fix it manually, or just wait till spectre comes out since the whole web walker is getting an update.
In other news, just pushed an invisible update to fix the most common exceptions in my log...