Found a Bug. I still don't like how the "find nearest" command works. It should be location based and remembered by the bot (like a global variable) until it is overridden with another "find nearest" command. Instead, it seems to go by each individual item's location. When the "problem" bot is in the right location, it will repeat "find nearest" and "pick up" until it's hands are full, however, it will not pick anything up. Another bot with the SAME EXACT CODE will work though. I have a theory of why this happens. When the problem bot finds nearest  item:X, it remembers the location of that same item. This happens even if it repeats with another "finds nearest" command and even when the bot is stopped and started again. What the bot could be finding is another stack of the same item in a different location that I intentionally did not want him to move to. The "find nearest" command is meant for a bot to move to that item, but what if the items are all in one stack? I propose a new line of code to be added. It should be "Pick up Item" and be given a master list of all items (or however it's programmed). This would solve the issue of having to repeat a find nearest command and waste time repeating unnecessary code. I am open to other suggestions/solutions so please msg me back if you find something.

EDIT: Read below for a better guesstimate on Find Nearest Mechanics

Maybe it's searching closest to the beacon, so I shouldn't use beacons? Just a thought.

WELP! that was it. Problem solved

I had to do a bit of testing. The find nearest command is very......weird. I may be wrong about how it functions (shocking), but this is my experience.

Move To (item): Same exact function as "Move To" command. The value is stored as an xy coordinate I presume.

Pick Up (item): This picks up an individual "item". The "item" is programmed by the find nearest command.

Here is where it goes down the rabbit hole.

Find Nearest (item): This command programs other commands below it in sequence. If you say to find nearest berry, move to mushroom, and pick up stick, it will move to berry and pick up berry. The sequence is very specific as well. If you have "find nearest" -  "Repeat (closed so it will skip to next line)" -  "Move To" - "Pick up" , it will move towards the ends of the earth and I do not know why. Flip the "Pick up" and "Move To" commands and now it will Pick up the specified item (not items plural unless repeatedly reprogrammed to find another item) and "Move To" where ever you specified the coordinate (i.e. not reliant on find nearest). To calrify, the "Move To" will retain its value unless programmed by "Find Nearest" while the "Pick Up" must be programmed to pick up anything. The location of "Pick up" to be programmed must at least be after "Find Nearest" in sequence while "Move to" must be directly after "Find Nearest" to be programmed. As to why the bot moves towards the edge of the map when a repeat (closed) is before a "Move To" is a mystery to me.

Denki, why did you make this so complicated :p

Edit: Also forgot to mention that "Find Nearest (item)" programs the "Move To (item)" based on the closest location of the "item" from the point of origin or where you told it to "Find Nearest". You can visibly see the point of origin as a red circle when you hover over the "Find Nearest" command. If you specified a beacon, it will find the closest item from the beacon and not the point of origin.

This is the last time I respond to you if you still do not understand gmrose9.  I'm giving you the benefit of the doubt that you did not understand me to begin with and that you are not trying to egg me on purposefully. Do a simple test for yourself. 

1. put a stack of any of the same items (that you are able to stack in hands) on the ground

2.put your bot in the same spot as those items

3.program bot to find-move-pickup item (in that same spot) until hands are full, then remove the "move to" command.

4. lo and behold, your bot can pick up items without the "move to" command.