search

maruohon / autoverse

A Minecraft mod about simple automation
GNU General Public License v3.0
6 stars 4 forks source link

[solved]more videos,tutorials etc please #4

Open VeroGirl opened 6 years ago

VeroGirl commented 6 years ago

Can you consider making more content for youtube or curseforge? tutorials, etc. also... can you consider a receiver/provider pipe

VeroGirl commented 6 years ago

i want to add that i really like the all the details you put into JEI

maruohon commented 6 years ago

An overview video is something I want to do, but not sure when I'll get to it. As to tutorials, once you understand the programming and reset cycle, there isn't much else to it, the rest is up to user imagination and problem solving on how to use the machines/blocks together to achieve whatever you need.

What do you mean by a receiver/provider pipe? A request pipe type thing? That won't happen, as that goes against the design principle of the pipes - they do not form any kind of "smart pipe networks" like for example the Thermal Dynamics ducts do. Instead the Autoverse pipes all operate individually. They are basically just "one slot per input side inventories, that try to push stuff out". So there simply isn't any way for an "output pipe" to request anything from an "input pipe".

However, a filtered input pipe is something I've considered, but that too might be a bit out-of-place with the other things. It would then at least need to be item-programmable like everything else. At the moment, the "Filtered Inserter" from the Ender Utilities mod can be used as a filtered input pipe. It functions somewhat similar to the Autoverse pipes, and the Autoverse pipes are actually partially based on the Inserters from EnU (both design-wise and implementation-wise).

VeroGirl commented 6 years ago

logistic pipes had requester units and i've been hoping to find something similar. how are we supposed to know how to program it if you don't have instructions?

maruohon commented 6 years ago

The programming is simply feeding in items in a specific order. There are no hard-coded meanings for any items. Everything is defined during the programming phase. The specifics are of course machine-dependant, but the basic principle of programming is like this: [END_MARKER][RESET_SEQUENCE][(machine-specific sequences)]

The end marker can be used to terminate "variable-length sequences" before the maximum length has been used. An example is the reset sequence, which can be 1 to 4 items long. If the full length is used, then the end marker is not used after that sequence.

As a concrete example, you would program a basic Filter like this: Let's say that we want to use Soul Sand as the end marker item for the programming phase, and we want a two-items-long reset sequence of White Wool and Orange Wool, and we want to filter out Iron Ore and Gold Ore, and everything else passes straight through. The programming phase would then be: [Soul Sand (defining the end marker)] [White Wool] [Orange Wool] [Soul Sand (terminating the reset sequence before the max length of 4)] [Iron Ore] [Gold Ore] [Soul Sand (terminating the filter items sequence before the max length of 18 items (or was it 27?))]

After this the Filter is fully programmed and switches into "normal operation" mode. Any arriving Iron Ore and Gold Ore will be output to the secondary/filtered output side, all other items will be output to the front/main output side. When a White Wool immediately followed by an Orange Wool arrives, then the Filter would reset and first flush out the previous programming sequence, and then move to the programming phase waiting for a new programming sequence.

The same programming principle is used for all machines, some of them just have many more programmable properties or values. For example the Block Detector has values for maximum range, the delay between detection attempts, the maximum angle to detect in, the blocks to detect etc.

Bucky420 commented 5 years ago

kids who play minecraft don't like programing ... make a guide?