Mesecons & Pipeworks vs. Basic_machines & hoppers

[BBmine]

Okay, so I am currently setting up a LAN server that will usually have 2 players concurrently, but may sometimes have up to 5. I kinda like mesecons and pipeworks (Resource intensive), but I also like basic_machines and hoppers (Less resource intensive). From a gameplay standpoint, I'm leaning towards mesecons and pipeworks, but from a playability standpoint (Lag), I'm leaning towards basic_machines and hoppers.

I have two computers that I could use. The first is my home server, which runs 24/7. Here is its CPU:

Code: Select all

Intel Pentium N3700 (4) @ 2.400GHz

NOTE: 2.4GHz is the max speed. Average speed is 1.6GHz.

The second is my desktop, which runs ~16 hours a day. Its CPU:

Code: Select all

Intel i7-7700 (8) @ 4.200GHz

3.6GHz base speed.

[hajo]

From a gameplay standpoint, I'm leaning towards mesecons and pipeworks,
but from a playability standpoint (Lag), I'm leaning towards basic_machines and hoppers.

What do hoppers do, aside from storing and moving stuff ?

That part could be done just by movers & chests (or basic_robots).
Or do you mean the cost of building those parts ?

[v-rob]

Hoppers, all the way. Hoppers are extremely lightweight and can do almost anything you want them to do. If you use FaceDeer's version, then you can have sorters and chutes as well. Since it's transported in an inventory, you don't have to worry about anything happening to your stuff. The only problems I can think of with hoppers is that they can't transport upwards, but using the API in FaceDeer's, it probably wouldn't be hard to code hoppers that transport up.

As compared to pipeworks: Pipeworks has a lot of stuff, but all that stuff is required just for pipeworks to work properly without your setup failing. Aside from deployers/node placers/node diggers/liquid transport, there isn't much advantage to it. It's more stuff for little extra gain.

[BBmine]

Does hoppers and/or pipeworks have the ability to share "data" lines?

Code: Select all

Source 1----\               /----Dest 1
Source 2-----|----------|-----Dest 2
Source 3----/               \----Dest 3

Where Source 1 transports items to Dest 1, Source 2 to Dest 2, etc.

[v-rob]

Does hoppers and/or pipeworks have the ability to share "data" lines?

Code: Select all

Source 1----\               /----Dest 1
Source 2-----|----------|-----Dest 2
Source 3----/               \----Dest 3

Where Source 1 transports items to Dest 1, Source 2 to Dest 2, etc.

There are two ways to get separate sources to separate destinations:

1) Make 3 separate transport lines:

Code: Select all

Source 1--------------------Dest 1
Source 2--------------------Dest 2
Source 3--------------------Dest 3

2) Place them all on the same transport line, but have a sorters before the destinations:

Code: Select all

                                /---Dest 2
Source 1----\            Sorter/----Dest 2
Source 2-----|----------Sorter|-----Dest 3
Source 3----/

But neither pipeworks nor hoppers will sort it for you without you making the sorters yourself.

[BBmine]

@v-rob Yeah, option one is probably the one I want because I was thinking of a mail system to go into an apartment building.

[joe7575]

Does hoppers and/or pipeworks have the ability to share "data" lines?

Code: Select all

Source 1----\               /----Dest 1
Source 2-----|----------|-----Dest 2
Source 3----/               \----Dest 3

Where Source 1 transports items to Dest 1, Source 2 to Dest 2, etc.

I don't know, but TechPack (Tubelib) has the ability to share "data" lines:

Code: Select all

Source 1--[P]----\            /---Dest 1
Source 2--[P]---[D]----------[D]--Dest 2
Source 3--[P]----/            \---Dest 3

[P] is a Pusher
[D] is a Distributor

And with its extensions, it is able to do much more...