RawTech

Assuming your proxifier targets are appropriately setup yes. Though it sounds like *.runescape.* may not valid here. Just launched the client on my machine and the official osrs client process looks to be called JagexLauncher.exe perhaps try targeting this instead? I would stick with the native proxy configuration on the osbot client here to simplify things.

Not hugely. Some form of X server is required to launch the client heedlessly it seems. I have changed the entry point to use debug mode to get around the tailing of the logs from the filesystem.

Proxifier will still send your *.runescape.* traffic to your proxy, just via nordvpn. You can verify this by creating a proxifier rule for a web browser and then visiting a site like http://ifconfig.so/ Try it twice with nordvpn enabled and disabled, to verify your results.

69.420 credit please

Grafana is a great visualisation tool, it supports mysql as a data source, and above all, is free and open source. If you know your way around SQL you can create some very data rich visualisations. Obviously you'll need to capture all of this data in a meaningful way.

No question.. Git is the best practice. If you're creating an entirely new script with no intention to merge the 2 together then make a new git repo. If you're creating a new version of an existing script, like a beta or alpha version, then make a new branch within the same repo. Googling git best practices you get a lot of branching strategies, commit tagging and naming conventions etc. But those are only really useful when you run a large software shop with multiple developers. If you're working alone, just find out what works for you. Github offer free private repos now and if you're looking to roll with your own selfhosted gitlab is really nice but potentially a bit overkill for a few repos.

I typically get one headless osbot client per GB of ram on linux systems. CPU is not really a bottleneck providing the clients have the lowcpu flag. Not using webwalking reduces the ram requirements by half, so 500MB per client. All from my own experience using custom scripts.

"Fixed trading not offering items in resizable mode." Nice one, cheers Patrick

In your module configuration within the project structure make sure that the scope for osbot is set to "provided". This will exclude it from the compiled jar.

Epic, thanks Patrick.

That's worked a treat. Thanks @Token

Hi, When running the client in resizable mode, is there any way to programmatically set the client dimensions, either through the script itself or the CLI arguments? I'm wanting to set the client viewport to 720p or 1080p automatically when I launch the client/script. Thanks

Thanks for all the hard work @Patrick !

Restarting the client doesn't seem to help. worlds.hop() is just returning false in the cases where it doesn't work. The client opens the world switcher tab but doesn't attempt to scroll to the desired world, if the desired world is in view, it will click on it.

For certain scripts you need to hop to a specific world. I guess this would be a workaround if you didn't need to do that. I just noticed this same issue when I got home from work today, hopefully its something the developers can resolve in good time. @Patrick edit: From my brief testing, it doesn't look like the problem specifically affects certain worlds, seems to be broken across the board.