Ace99

As many mentioned above you were right on the following: My while loop condition was met and was logging that it was met but the loop continued - mirror mode thread issue i guess The Area loop itself was an issue as well because when the code is in the foreach loop it does not hit the return on the onLoop() until the whole Area loop is done - allowing the false return on a boolean inside the Area loop to continue the code rather than loop back through until it is true I have resorted to the list of if statements - will let you know if the outcome is better after I get the correct logic on all this restructuring.

@Nbacon That is a cool idea - but being honest with myself that is out of my ability right now. Crazy but good that your 6000 if statements don't effect performance lol

I am using a home teleport and nexus/wall mounted things. I get a false return when the nexus, for example, is not in the screen view so it has to rotate the camera. Then after that else catch it moves onto the false return and I am stuck somewhere like that. Maybe I can adjust that 'if' functionality specially... thanks for the feedback I am going to look into the list of if statements after I try @BravoTaco idea to add a counter in the while loop to catch endless loops. So far I have not had a mirror mode issue either. Never say never I definitely do and will use the count method above as a fail-safe. These areas are pretty much staples so I do not foresee this as an issue but who knows. I will keep tabs on the updates they make to the game for sure.

Discussion: I think I have read from time to time that having a while loop in the main loop is a bad idea/bad practice. Can someone explain why this is? Loops are nested in loops all the time (small applications), what is the issue here that makes it different? Issue: I loop though the keyset of a hashmap and run a set of tasks for each key, once complete I set the key value to true and move on. Part of my task is to get to a specific area. If I use this: // initial bank for items for(Area in Areas){ if(!Area.contains(myPlayer){ walkTo(Area); // This is a boolean only returning true when Area.contains(myPlayer) } // Do actions at area } Sometimes the bot will not be at the Area and all the sudden move to // Do action at area. I assume the walkTo(Area) hit a false return. So instead I can do: // initial bank for items for(Area in Areas){ while(!Area.contains(myPlayer){ walkTo(Area); // This is a boolean only returning true when Area.contains(myPlayer) } // Do actions at area } And when a false is hit on walkTo(Area) it will try it again and move the screen and find to door/portal is is not finding currently. Is there anything wrong with this or a better yet, a cleaner way to accomplish this?

Awesome thanks for the feedback! People can feel free to post, that would be cool. Not sure on that one - out of my realm. Make sure OSBot is up to date and refresh Notified of a bug with the GP/hr in the GUI - URL changed for the GE, update has been made and should be available in 24-48 hours. Loading seems slower with this change... I will hopefully figure out how to optimize that better. Thanks again to @TheRealWhistles for the heads up.

Take a look around the SDN for any holes you see. Getting creative is the best strat. Free script can be rather simple too.

My best go-to's are to comment everything new and then uncomment it piece by piece so you know what works well, and then just log everything and track the log to see what is being logged during a period of lag/freezing. You could be calling something an unreal amount of times and not know it, creating an object over and over, not caching info efficiently, or not creating optimal methods/loops in general. Do you have multiple threads running, external API calls, web interfacing? Address things like that.

This is not related to your actual question, just a suggestion: Try using a Filter<Item> to grab all the energy pots at various doses, if you haven't already

+1 to Explv as it is what I started on

Most everywhere I read/see has said what I said. Seems to be a lot of entry level personnel that is easily replaceable which makes it hard to stay somewhere and get years of exp under the belt. I like your point on school curriculum being behind, that makes sense. Yeah I would follow a pretty standard approach to getting all certs and then take my shot. I understand I would have to deal with some help desk/network admin stuff for a bit but would not want to stay permanent. DevOps is something I had not looked into so I will start to do so. Having my degrees not related to this is a pretty big kick in the nuts, but that is why I was leaning towards getting all the certs to get into the industry of Sec or work up some portfolio magic and prove I can be a good Dev to a company.

Anyone in these fields able to speak to how they like it or expectations vs reality? More specifically Red Team InfoSec or a Full Stack Dev. At a fork in my career and want to pursuer one or the other. Have two degrees but not in an IT or Computer Science field. From my research here is a brief summary of what I see: CyberSec Make more money early on Easier entry level job opportunity May get stuck in Help Desk Hell Certifications lead to interview WebDev Saturated market makes it hard to get entry job Layoffs are prominent as a junior Projects may take 10 turns in 10 different directions before finished Remote work is popular Need a personal portfolio for interview Looking for actual experience. PM me if necessary. Thanks!

I did not know that. Go for it then for sure

If things are a bit too much for free but you want on the SDN for free, they would most likely go into VIP+ section. Not certain but the AIO magic scrips and AIO construction scripts may cover the lunar and oak larder scripts. I'd focus on the self sufficient super-heat script as well as the mass pure ess running. Those are unique

If you really know python, its just a matter of syntax and declarations that would change. You'd waste time on a python color clicking bot (for instance) vs just learning OSBOT like it is meant to be.

RIP... but it is runescape, you'll be back