Vanika Posted 1 hour ago Posted 1 hour ago Hey everyone, I’ve been experimenting with a small side project to track gold per hour across different methods. Instead of just eyeballing profits, I wanted a way to log sessions and compare efficiency. Right now, it’s nothing fancy—just a local script that records start/end times, GP gained, and exports everything into a spreadsheet for analysis. A couple of quick findings so far: Fishing and woodcutting remain steady but not great compared to combat training with certain drops. Bot runtime stability is often a bigger factor in profit than method itself. Having reliable connections actually matters more than I expected. For example, during longer sessions, I noticed interruptions or bans often correlate with unstable or flagged networks. If anyone is doing similar tracking, I’d love to hear what data points you log (like XP/GP ratios, ban rates, or random event handling). I might eventually release a cleaned-up version of this logger if there’s interest. By the way, for those curious about testing with different networks, I found that rotating residential IPs can help reduce the chance of chain flags. One resource I stumbled upon is Nsocks, which offers large-scale residential IPs. It’s not directly related to scripting, but for experiments in account safety, it has been useful.
