Welcome!

Please message me on discord.

It's usually related to running the 64bit build and then switching to the 32bit build. Is the 64bit build not working for you? Did you delete the RuneMate folder in your user folder after uninstalling the 64bit build and before installing the 32bit build?

I have been requesting additional information to fix the issue. To help me resolve it, please contact me on discord and give me the requested information (screenshots, files, error details, and more that will be discussed during the conversation). All issues that have been brought to me this way...

A new version of the installation software was You need to provide logs indicating the issue and if you have a client alert error than please post a screenshot of that as well.

We're online!

Yes, I'm interested. It could be useful for detecting infinite loops programmatically.

Alright for that edge case npc it's likely similar to the mage of zamorak where they change the data at runtime. I'm not going to address that right now because it would require intercepting a packet.

I suggest you just explain the process flow instead of asking if anyone is interested because at some point someone will most likely be interested.

But wait, on the other hand @CuppaJava queries are supposed to search the entities local state as well. Are you saying that when you used a name on an NpcQuery it didn't find it in the local state?

Are you sure you didn't need to look in a local state definition for the name?

It frequently still is but some solutions are being experimented with.

Do you have the official java client installed for osrs? It may not be locating the cache directory properly if that's not been created by running it. It could also be a file permission issue of some sort but I haven't seen that happen before.

RuneMate has an API method for this. @RobinPC are you using our API for it or your own? I tested that our API method worked in quite a few different scenarios.

We're not dead. @anka please delete all your log files and then run RuneMate and attempt to attach to OSRS again. It should show the same message. Get the new log files that were generated after shutting down RuneMate and the game and please attach them here (I don't check my private messages...

To my knowledge they changed some security settings in macOS Big Sir and we've yet to work around them. Additionally, macOS users (temporarily) have to do a few additional steps to get the client working due to an update that Jagex made to the OSRS macOS installer a while back. I'm going to be...

All isRS3() is doing is checking if you're on osrs or rs3 and delegating to a different method depending on the case. Could you please record a video of the behavior?

Just so anyone who is wondering about this still is aware, the distance between each step was greatly increased a month or so back.

RuneMate has been updated to v2.110.0. Interfaces now have their positions calculated correctly after switching between Fixed and Resizable game client layouts (also known as the canvas mode). This fixed a long standing bug that was greatly impacting the startup experiences of many users...

This was discussed and addressed in the development channel on slack.