- Joined
- Sep 17, 2020
- Messages
- 5
- Thread Author
- #1
Hello,
I have scripted on most of the clients out there for a couple of years and runemate is sure one of the most unique out of the bunch.
Runemate interests me due to it using the official client by instrumentation. and that gets rid (mostly) of the locking problem all other clients suffer from.
I've been looking at the api and have downloaded Runemate to view what it has to offer and so far so pleased. But ive been thinking.. How does RuneMate send the objects it grabs via reflection to the GUI/Java 8 application as i think most of the objects are unserializable. Do you guys keep the object in the bridge in some sort of structure with a key to be grabbed at a later date?
my question is because if my assumption is correct, runemate eats a lot of memory and the objects even those that arent needed anymore will stay in the structure (scortched earth) and will need to be removed manually.
Thank you
I have scripted on most of the clients out there for a couple of years and runemate is sure one of the most unique out of the bunch.
Runemate interests me due to it using the official client by instrumentation. and that gets rid (mostly) of the locking problem all other clients suffer from.
I've been looking at the api and have downloaded Runemate to view what it has to offer and so far so pleased. But ive been thinking.. How does RuneMate send the objects it grabs via reflection to the GUI/Java 8 application as i think most of the objects are unserializable. Do you guys keep the object in the bridge in some sort of structure with a key to be grabbed at a later date?
my question is because if my assumption is correct, runemate eats a lot of memory and the objects even those that arent needed anymore will stay in the structure (scortched earth) and will need to be removed manually.
Thank you