Improved exception handling in several places. Some stack traces were unnecessarily wrapped, and when trying to report exceptions that occurred within the methods of event listeners, RuneMate itself would throw an error so it wouldn't properly get reported to the developer. Enabled logging to a file earlier in the startup process. Some debug information was only being written to the console and not the log file because it occurred before logging to the file was enabled. Added destruction of Feral vampyre fangs (some bots would endlessly try and drop them) Improved the debugging of bot manifest errors to encourage bot developers to fix them Fixed a glitch with WebPath's where getNext() could return the coordinate the player was standing on. It would then try to click the players location. Fixed a bug that allowed RuneMate to attach to an applet that was not yet active. Improved the text of a rare array-based exception in the bridge so that I can more easily patch the underlying issue. InterfaceComponent#getActions() will no longer contain any null actions. InterfaceComponent#getText() will now return null if it doesn't have any text (subject to change...) Cleaned up a bunch of toStrings so the dev kit will display things cleaner Made GroundItems.getLoaded() only return the ground items on the current plane (osrs only, I'm not sure if it is an issue on rs3)
I'm getting a trojan false positive during install of the 2.0.9 update. win32/fatale.B!plock is the alert which makes me think something changed in the updater code?
Yeah I figured it was a false-positive. Just wanted to give you devs a heads up. It was throwing the alert via windows defender on Win10 so i'm unsure how soon/if Microsoft will rectify the problem.
Windows Defender...? That's a new one. @Cloud just release a new build. Re-obfuscation will resolve it. It's likely some random pattern it's tripping. Shitty pattern detection is shitty.
I went ahead and took a stab at fixing the issues with the game running out of memory in a silent release, it appears to be a success but if anyone is still encountering the issue then please notify me.
