Hey, just restarted the client and received the error 'An error has occured while loading hooks'. Here's the log:

Quote

[DEBUG][Bot #1][03/02 12:50:00 AM]: Initializing mirror client bot...
[ERROR][Bot #1][03/02 12:50:09 AM]: typeb
java.lang.NoClassDefFoundError: org/osbot/rs07/accessor/XRS2Buffer
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(Unknown Source)
    at java.lang.ClassLoader.defineClass(Unknown Source)
    at org.osbot.zB.loadClass(sr:44)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at client.pOH.bind(Unknown Source)
    at client.nat.stream.Stream.m13(Native Method)
    at client.PYmK.xd(Unknown Source)
    at client.emu.ty.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.osbot.rs07.accessor.XRS2Buffer
    at java.lang.ClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at org.osbot.zB.loadClass(sr:277)
    ... 10 more
[ERROR][Bot #1][03/02 12:50:09 AM]: hmrapi
java.lang.RuntimeException: Could not find field class
    at client.nat.stream.Stream.m13(Native Method)
    at client.PYmK.xd(Unknown Source)
    at client.emu.ty.run(Unknown Source)
 

 

Same here

Same

Its only with mirror mode, hooks are broken.

same mirror mode only

Same..

I think it has been fixed now

Nope still broken...

1 hour ago, Dark798 said:

Nope still broken...

Are you sure? If you look in the logger, which hooks are being loaded for your client revision? I think the broken ones were revision 136. I'm since I posted my latest reply loading hooks for client revision 137, which is working for me now..

26 minutes ago, Reveance said:

Are you sure? If you look in the logger, which hooks are being loaded for your client revision? I think the broken ones were revision 136. I'm since I posted my latest reply loading hooks for client revision 137, which is working for me now..

Hmm, must have just fixed it.

It's working now :^)

 

It always gets fixed sooner or later the devs of this site are btter than the rest