How do you design your big builds

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here

how do design your big builds


  • Total voters
    92

ThatOneSlowking

New Member
Jul 29, 2019
3,520
0
0
Not quite a necro, promise!

I am as close to the mythical 'end game' as I have ever been in my current 1.5.2 world, so thought I'd start setting out for my 1.6.* base. This will be a total loss on this map, I know, but I will have screenshots and will know if it 'works' (after having already planned it on paper first, it should do). First big build since the skybase, this one is going to need a few world anchors!

Provisional foundation shape laid out in pink wool for visibility, using landmarks/redstone torches for working lines on the ground.

That...looks...AWESOME
 

wildc4rd

Well-Known Member
Jan 29, 2013
185
36
53
Several hours later, foundations are down in quarried stone and the floor in construction foam (only suffocated myself once). The advantage of looking over the design even before 'setting it in stone, literally' showed I had derped on one of the walkways between what will be the domes (it was half a block out, would have thrown the roof out of position and been a nightmare). Checking and picking up that sort of thing before starting superstructure saves ages! (Edited to add the start of the roof, just need more quartz now!)



 
Last edited:

Yusunoha

New Member
Jul 29, 2019
6,440
-4
0
the shape reminds me of this :p

YsKwatT.png
 

rhn

Too Much Free Time
Nov 11, 2013
5,706
4,420
333
I personally plan builds out in my head perhaps for several days. Both when talking about large machine setups and architectural stuff.
Usually I then go get a large amount of cobblestone and dirt. For buildings Shovel of the earthmover, wand of equal trade, Wand of building. Then I start building the rough parts out in cobble/dirt. Once I settle on the proper layout I choose materials and start adding microblocks.
 

namiasdf

New Member
Jul 29, 2019
2,183
0
0
There are many considerations:

[1] Space: Space is the #1 most important key. Even if you're working in the outdoors (i.e. have unlimited space) your design will still take up space and the design should account for that. If your factory is too large, it might become to tedious to find errors/tweek your system. In my case, where I have limited room, space becomes an even bigger problem. It is more of an issue of trying to design a system that its space meets its purpose. If your system is needed to attach to other system, you may want to locate it in a central location such that it is easily accessible. Space includes (1) the efficiency in which it takes up space as per design (design it in a way that it isn't wasteful of space) and (2) is externally and internally accessible, such that you can access the innards should you need to make small changes and to allow for easy integration to outside systems.

Compact Design:
fJD8Rlx.jpg


Underground Base:
dB49hTX.jpg



[2] Cost: This should be obvious, but optimizing a design such that it would give the "best bang for buck" is more involved than you might think. Depending on how you acquire resources the value of a given resource may vary. Including the time-varied acquisition of the resource as per your strategy (quarry, turtles, etc.). Examples of such considerations would include whether you wish to integrate your AE system into the system you are considering. AE materials aren't excessively valuable, but require time to accumulate. Projects that utilize a high volume of iridium should be optimized such that they utilize the blocks using these resources to its maximum. This also means designing the system such that you can achieve such optimization through testing/tweeking. Synonym: Non-Wasteful.

Very Efficient Utilization of Lasers:
IGwFW39.png



[3] Integration: A very important aspect of a system is whether it can be successfully integrated into your base. This goes back to accessibility as well. If it is located in a poor location, getting resources to that system might be cumbersome/expensive. Having items floating in transport pipes should be minimized for any case, as to keep the load on your computer as low as possible. If your system doesn't really provide much to enhance other parts of your base, its existence would need to be justified that much more. Usually I build my systems to synergize with one another. Synonym: Versatile/Purposeful.


[4] Scaling: A system should be able to grow as your needs grow. Whether it be increasing your energy production or your item processing, your systems should be designed in such a way that it can be expanded. This means leaving extra space or incorporating the ability to change your system such that it is more efficient. The best way to achieve this is to modulate your system. Every time you wish to expand your system you build another module. You know exactly the resources required to build each module and exactly its output. This is extremely useful in the process of design. Synonym: Upgradable.

Version 1.0 Lava Gen Module: (40 Combustion Engine -> 4 Magma Crucible)
nwgFvkI.jpg

(These are side-by-side modules of the first picture, two layers)

Version 2.0 Lava Gen Module: (4 - 36HP Boiler -> 72 Industrial Steam Engines -> 20 Magma Crucible)

8boiler
J4TTjT3.jpg


12boiler
9kHyEli.png


sideview
O2574NP.png


crucible1
9QjByU6.png


crucible2
HyD2FoW.jpg


thermalgenerators
SND4GWH.jpg



These are a few of the things I might consider when building a system. Main key points are its accessibility, upgrade-ability and its cost. Space is more of an issue for me because my base is inside of a mountain.
 

Saice

New Member
Jul 29, 2019
4,020
0
1
Space and/or size can almost be huge factor on servers where you might have a limit on chunk loaders. This also comes with the idea of Chunk alignment of complex systems another important thing in many cases.
 
  • Like
Reactions: rhn

ThePixie35

New Member
Jul 29, 2019
157
0
1
There are many considerations:

[1] Space: Space is the #1 most important key. Even if you're working in the outdoors (i.e. have unlimited space) your design will still take up space and the design should account for that. If your factory is too large, it might become to tedious to find errors/tweek your system. In my case, where I have limited room, space becomes an even bigger problem. It is more of an issue of trying to design a system that its space meets its purpose. If your system is needed to attach to other system, you may want to locate it in a central location such that it is easily accessible. Space includes (1) the efficiency in which it takes up space as per design (design it in a way that it isn't wasteful of space) and (2) is externally and internally accessible, such that you can access the innards should you need to make small changes and to allow for easy integration to outside systems.

Compact Design:
fJD8Rlx.jpg


Underground Base:
dB49hTX.jpg



[2] Cost: This should be obvious, but optimizing a design such that it would give the "best bang for buck" is more involved than you might think. Depending on how you acquire resources the value of a given resource may vary. Including the time-varied acquisition of the resource as per your strategy (quarry, turtles, etc.). Examples of such considerations would include whether you wish to integrate your AE system into the system you are considering. AE materials aren't excessively valuable, but require time to accumulate. Projects that utilize a high volume of iridium should be optimized such that they utilize the blocks using these resources to its maximum. This also means designing the system such that you can achieve such optimization through testing/tweeking. Synonym: Non-Wasteful.

Very Efficient Utilization of Lasers:
IGwFW39.png



[3] Integration: A very important aspect of a system is whether it can be successfully integrated into your base. This goes back to accessibility as well. If it is located in a poor location, getting resources to that system might be cumbersome/expensive. Having items floating in transport pipes should be minimized for any case, as to keep the load on your computer as low as possible. If your system doesn't really provide much to enhance other parts of your base, its existence would need to be justified that much more. Usually I build my systems to synergize with one another. Synonym: Versatile/Purposeful.


[4] Scaling: A system should be able to grow as your needs grow. Whether it be increasing your energy production or your item processing, your systems should be designed in such a way that it can be expanded. This means leaving extra space or incorporating the ability to change your system such that it is more efficient. The best way to achieve this is to modulate your system. Every time you wish to expand your system you build another module. You know exactly the resources required to build each module and exactly its output. This is extremely useful in the process of design. Synonym: Upgradable.

Version 1.0 Lava Gen Module: (40 Combustion Engine -> 4 Magma Crucible)
nwgFvkI.jpg

(These are side-by-side modules of the first picture, two layers)

Version 2.0 Lava Gen Module: (4 - 36HP Boiler -> 72 Industrial Steam Engines -> 20 Magma Crucible)

8boiler
J4TTjT3.jpg


12boiler
9kHyEli.png


sideview
O2574NP.png


crucible1
9QjByU6.png


crucible2
HyD2FoW.jpg


thermalgenerators
SND4GWH.jpg



These are a few of the things I might consider when building a system. Main key points are its accessibility, upgrade-ability and its cost. Space is more of an issue for me because my base is inside of a mountain.

Are you just using the same pictures everywhere? Third time I've seen these photos :p

OT: I take a lot of time on picking my area, then I go from there. Plans go in small steps. I'm currently at the "plan what to actually build" stage, I've got the location and theme I want and even a small back story for it. What to build though... still a blank.
 

namiasdf

New Member
Jul 29, 2019
2,183
0
0
I took the specifically so that I could exemplify the techniques I used to build them, mostly described by the textual post that accompanied them in this thread.