I don't know why but recently I've been getting this stacktrace error whenever I do myPlayer().getName() in the onStart method:

[INFO][Bot #1][02/01 08:59:16 PM]: Loaded 4 built-in random solvers!
[INFO][Bot #1][02/01 08:59:19 PM]: Started random solver : Auto Login
[INFO][Bot #1][02/01 08:59:26 PM]: Random solver exited : Auto Login
[INFO][Bot #1][02/01 08:59:30 PM]: Started random solver : Welcome Screen
[ERROR][02/01 08:59:31 PM]: Uncaught exception!
java.lang.AbstractMethodError: bc.getName()Ljava/lang/String;
	at org.osbot.rs07.api.model.Player.getName(bi:268)
	at core.ClayMiner.onStart(ClayMiner.java:38)
	at org.osbot.rs07.event.ScriptExecutor.iIIiIiiiIIIi(yn:153)
	at org.osbot.rs07.event.ScriptExecutor.start(yn:484)
	at org.osbot.GB.run(qf:8)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
[INFO][Bot #1][02/01 08:59:33 PM]: Random solver exited : Welcome Screen

I updated to 2.4.161 yesterday and it was fine, but today I'm getting this error. I've tried deleting the OSBot folder, downloading the client again but it still gives the same results.

Also, whenever a random event pops up I get the same error, so whenever it tries to call myPlayer().getName() it generates that. For now for my use case I'm using bot.getUsername() but it is still prone to crashing when a random event occurs. Any thoughts?

Can confirm this happens with Fruity Zulrah as well.

It's a problem with all bots currently, all local player methods (Including ones on other botting clients) are broken. There's no fix on our end, just need to wait for the next update.

25 minutes ago, blogans said:

It's a problem with all bots currently, all local player methods (Including ones on other botting clients) are broken. There's no fix on our end, just need to wait for the next update.

Not true in my experience. A few other methods I've tested work, like myPlayer.isUnderAttack(). Right now through running my scripts, the only issue I've had so far is with the myPlayer().getName() method.

Yeah just started getting this today as well with Perfect motherlode

Update: Getting an error when trying to access details of Item objects as well e.g. item.getName(), item.getId(), etc. Seems to be an issue with multiple classes.