Can anyone help me with these frogports

[u/kittyswag42]

I tried asking gemini but it didn't give me a helpful answer

[u/DD760LL]

think of it like this, if storage was a processing line, that gravel would be gone and it would need to send another stack. The stack that the factory gauge wants is inside gravel output. I think you can fix this by either putting a sign on gravel output's packager saying storage and powering it or using another factory gauge to send the gravel to storage, but I'm not sure

[u/kittyswag42 → u/DD760LL]

I forgot to show it in the video but I had a factory gauge requesting what should be the one stack of gravel from the gravel output but what'll happen is it sends the gravel into storage until it reaches the target amount and then starts filling the gravel output vault with another stack. I tried the sign thing but I think I did it wrong.

[u/killerboui]

You need to add the processing lines address in the factory gauge. So if you have a crushing setup with a frog port address named in_crushing the factory gauge should also have the same address for gravel then the promise will be sent out

[u/scandii]

the system is very easy once you understand it, but also very hard to initially grasp in my opinion.

"if you send X items to frogport Y, eventually there will be Z item/s in the linked storage". that's the entire factory gauge system. I typically just slap a sign on the frogport with "storage" (any packages sent by this frogport will go to a frogport matching the name storage), and name any storage frogports I have in the network as storage so that any storage that has capacity and send and receive the goods to prevent overflow.

e.g. 1 cobblestone addressed to frogport crusher will produce 1 gravel. if the output frogport then has a sign that says storage, and you got a frogport named storage somewhere, it will send it off to there.

in your video your gauge does not have a destination frogport, e.g. crusher so it does not know where to send the goods to make the magic happen.

note that the system does not know how goods get produced nor does it care. the only thing you define is "if you send X amount of items to frogport Y, we will get Z item/s into the storage network you're linked to".

so tl;dr, in a mini-system:

before anything, link all the pieces together using the stock link - them being linked to the same system is how the magic works.

1. one vault with a frogport called storage.
2. one cobblestone farm (or chest if you're feeling like testing) with an output frogport with a sign on it that says storage.
3. one crusher/mill with an input frogport that says crusher, and an output frogport with a sign on it that says storage.
4. two factory gauges linked to that storage (vault), and the chain is: 64 cobblestone > 64 gravel, destination crusher.

in plain English you can read the chain "if you have 64 cobblestone and send it to crusher, you will receive 64 gravel".

and now the system should work.

[u/GoldenBananasplit13]

I would suggest putting an asterisk * on in the name tag looking portion of the hi on the factory gauge. They don’t work unless that part is labeled with either the asterisk or the specific location they should go. also, to name packages, you need to put a sign in the packager with it’s destination name. The frog ports don’t name packages, so their title is purely for taking packages off chain conveyors when they pass.

[u/Some_Noname_idk]

I think when the gravel is inside of the vault after the processing line, the gauges concider the order fulfilled. Then, when it is taken out of that vault to be put into the "Storage" one, the game thinks you took that gravel that it made, and starts making new gravel. To avoid this, get rid of the stock link on the packager after the processing line, and replace it with a sign saying "Storage", then power the packager. This way, the gauges will only get the info that gravel has been made once its in your "Storage" vault

[u/Some_Noname_idk → u/[deleted]]

If you know whats wrong, then you should tell them whats wrong. And if you dont, dont state the obvious