That isn't true at all. Full auto egg gathering has been written. And it's way more simple than you believe. It's been written for stealth dexers and mages. 100% automated. The problem is clicking the holes. You two aren't thinking outside the box. The holes can be found with finditem, but targeting them isn't possible. You have to come up with a solution to that. It's easier than you believe. There are a few situations where things don't work as intended, and other solutions are needed.

Eventually you'll get to a point where you never want to use other people's subs because it's annoying to read them and debug them. Using your own code is much simpler. Write some basic standard subs and start to learn the call function, and you'll be well on your way to writing your own library. I have a few files that have standard subs for literally everything, written to my standards. And I just use a military SOP type procedure to update the subs inside those files. When I find a better way, I update. Overall, your entire library will benefit and as you add more and more standard subs to the file, you'll require less and less time to create large scripts. Because most everything will already be written by you and callable from your called standard sub files.    Sorry, SOP stands for Standard Operating Procedure. That just means when you find a better way, you adopt it. It makes it easy to keep your scripts updated, because when you update one sub, you literally update every script you have in your library that calls that file.

He's setting the %SB_Engrave_Tool_Color to 1165, then trying to search for the COLOR of the item with a #finditem, on the #backpackid.  He's not understanding you can't search for a color with #findid, you need to set the %SB_Engrave_Tool_Color to the color of the tool you're searching for, like you did. 1165. Then search for the #itemTYPE or #itemID of the kind of tool you are looking for. Or just use one of their options above that works. Hope that explains why your code wasn't working. #findcol is populated AFTER you do a search for any tools that match the type or id of the tool you are searching for. If it does, you loop through the #findindex until you find a tool that #findcol matches 1165, and that's the tool you "use" with set #lobject #findid. And use that object...

set %SB_Engrave_Tool_color 1165

But but but.  I don't. Those snippets were given to me just to post here. I don't have those scripts.

My favorite part of this video is where he explains that the Ryzen 5 1600 is just an 1800x with cores turned off because they didn't pass quality control. Eventually someone will release a bios hack that will unlock those extra cores. See if maybe you get lucky and get an 1800x for 200$. 

Of course they released that. What else would they do when Intel just released a whole new line of chips after AMD's amazing Ryzen showing, that has 6/8/10/12/14/16, and 18 cores. And intels chips usually beat AMD with less cores. haha And AMD is like, WE SHOULD HAVE A 16 CORE OUT IN 6 MONTHS!  lol  Damnit AMD! THINK AHEAD. I'm just glad my new cpu is 65w on a 14nm process. That halves my power consumption. Any savings go right back into computer parts! It's all about scraping to buy the best parts you can afford! 

They can't let AMD have their moment in the sun for even a minute.  My 6 core cpu uses as much power as this 18 core does!  Crazy.  Also, I ran the same test against my Ryzen 1600, and it was 3x faster than my old cpu in the cpu scoring.  Crazy.

For the price, I can blow up 2 and half Ryzen 1600's overclocking them to be nearly a 1700.  I pulled the trigger and went with water cooling so I can overclock this one to hell. If I blow it up, I'm still in it for less than a 1700+.