Install Steam						
					
				
				
									login
											 | 
						language
						
																																					简体中文 (Simplified Chinese)
																													繁體中文 (Traditional Chinese)
																													日本語 (Japanese)
																													한국어 (Korean)
																													ไทย (Thai)
																													Български (Bulgarian)
																													Čeština (Czech)
																													Dansk (Danish)
																													Deutsch (German)
																																							Español - España (Spanish - Spain)
																													Español - Latinoamérica (Spanish - Latin America)
																													Ελληνικά (Greek)
																													Français (French)
																													Italiano (Italian)
																													Bahasa Indonesia (Indonesian)
																													Magyar (Hungarian)
																													Nederlands (Dutch)
																													Norsk (Norwegian)
																													Polski (Polish)
																													Português (Portuguese - Portugal)
																													Português - Brasil (Portuguese - Brazil)
																													Română (Romanian)
																													Русский (Russian)
																													Suomi (Finnish)
																													Svenska (Swedish)
																													Türkçe (Turkish)
																													Tiếng Việt (Vietnamese)
																													Українська (Ukrainian)
																									Report a translation problem
							
						
 
											 
													

 10
 10								 This topic has been pinned, so it's probably important
  This topic has been pinned, so it's probably important	 
					




 Report this post
 Report this post


So - you are looking to chain beacons (and associated network routing) to avoid the need to dig / route relays around, am I understanding correctly?
I suppose the question is - since everything is transmitted on-demand, what would you gain by having separate networks? Logistically, would it not be more optimal to have it all together? If some new branch of your network requires x or y - it's available.
In my world I have one unified network for organics, cutter heads, intermediates, some bars, resin, etc - everything ends up where it's needed. If any particular section of the relays is consistently at 100% utilization, I upgrade it for more throughput. I don't know why I'd want to separate them?
If you are just using relays as smart matter movers (e.g. unloading lifts to furnaces) - by all means, there's no need to link them to the network at large.
Is there a use case that I'm not quite grasping?
That way I could make a drop-off hopper where I put parts that I don't need and they automatically get distributed to outputs. If some of these parts aren't needed anywhere, I could have another "garbage output" that macerates those.
For example if I'd drop some wires, bars and rock into a hopper connected to an adapter. It'll automatically use the wires and bars when they're asked for and send the rock to the garbage output.
Right now this could be approximated by using a garbage filter on an output, but that won't extract the non-garbage parts that aren't needed anyway.
For example, I manufacture PSBs and put them on the network. My 'grocery store' pickup point siphons some off to put into a hopper for player use. Despite the fact that it sits unused for 30 minutes, or even hours at a time, those items are definitely not garbage. They are used as intermediates, as well as for players.
I'd be open to suggestions if there were a straightforward way to implement it. It may be simplest to set up a few advanced filters set to the items you don't want hanging around and feed it as appropriate (macerator / smelter / PTG / etc)
its also possible im looking at this wrong, but i was planning on having a teleport network feed into the mass storage and another one to feed the machines, that way i can have multiple. Yes tehnically i can put the output of the network outside the room and feed the mass storage through the wall but it easier to be able to select which network the addapters and outputs are connected to if there are multiple netowrks in a room.
also with out seperate networks and having input and output to a massstorage system in a room creates an endless loop of items going in and out which also wastes power.
falcors -> hoppers -> this mod -> mass storage IO (filter set to all items) -> output from storage to machines. the filter to set all items into the mass storage causes the loop but then i cant get the items back out via the same network since the mass storage is supplying its self with the items it has in it, hence endless loop.
One thing that was added in the second version of the mod was the ability to directly connect inputs/outputs to relays. With that - if an input/output is either touching a relay directly, or the target of it's beam it does not need/use a beacon. The original intent was for end-of-line stations where the extra power drain of a beacon was not warranted - but it might do what you want as well. You could have an input and an output connected to the MS I/O - but each directly via individual relay lines (no beacon). Then you could keep the networks separate. (as long as the respective relay lines are separate)
I'll consider adding a network tagging option to create logical subnetworks the next time I have opportunity to work on the mod. I suspect it would be a bit more involved as it'd require UI work as well (windows, controls, network commands, etc).
One other consideration: Having items available to be teleported anywhere somewhat mitigates the need for a 'central storage' - I don't really use one any longer, myself. E.G. lithium coils arent stored centrally - they are in hoppers right by my lithium plant (and pulled out on demand). Removes the need for stocking ports and the like as well.