Simple Graphical Tweaks: Limited support. I'm in favor of grass creeping over one-block ledges and connected (and more transparent) glass, but others like tree roots seem unnecessary.
Built-in texture packs: Some support. I'd think a bare-bones, flat, redstone-optimised pack and a 32x32 packk, plus a few minor shaders, would be enough.
Minor terrain gen changes:
Larger, more diverse trees: Mostly no support. I personally hate large oak trees as they are much harder to cut down in Survival (logs aren't in one vertical column).
- existing hoppers are unchanged: they still suck from above and output below
- my new hopper/pipe system is no more complex than the existing system, unless there are multiple input hoppers or nearby containers: you simply shift-place the hopper on the input container and add pipes connecting the hopper to the output container. Special care would only be needed if there are multiple hoppers or containers that you do not want to connect.
@Palin You bring up a good point with water; I did not consider that. I'd assume pipes would be balanced by being faster than water, but having a lower throughput, as well as being intuitive and more versatile.
I might post an alternative (and likely simpler) solution to the problem of hopper/pipe connection later; tell me if you're interested.
I would think one would want the option to have hoppers suck from the direction of your choice when not connected to anything, but perhaps that can be done by attaching them to a block and deleting the block?
Correct.
I don't think you'd want pipes to automatically connect to everything next to them, perhaps pipes should only have 2 ends and add crossings that connect to more? That could still be a problem if you want 2 crossings next to each other but not connected to each other
That could work, but it'd be harder to precisely control, and would add more blocks than necessary.
Given how many redstone systems would probably break if the existing hopper was altered, I think making this copper hopper a new block entirely would be a better idea.
It'd be completely backwards-compatible with existing systems: preexisting iron hoppers would be converted into new copper hoppers with input from above and output unchanged. Since hoppers count as containers, existing hopper chains do not transmit any faster.,
I'd think it would be possible to place the new hopper so it works just like the old one?
Yes, but the order is changed slightly. Instead of placing the hopper to connect to the output, you would place it to connect to the input.
I'd presume the outlet could be on any side other than the input.
The outlet(s) are to any adjacent containers or pipes; there can be multiple outlets to one hopper. If a hopper connects to a pipe or container that you don't want it to connect it to, simply left click with a bare hand on the faulty connection.
Though I'm not clear over how one would go about setting the input and output directions independently, perhaps just place a container and pipe first and then place the hopper between them?
Input container first, hopper second, then add the pipe.
Except how would the game know which end to connect to a hopper or container? Does it fill or empty?
Hoppers are placed with the input face pointed towards the container it is placed on, and output to all other connecting containers and pipes unless manually disconnected. Hoppers fill from the input face, and empty everywhere else.
And what do you do if you want a hopper next to a hopper or container but don't want them to be connected?
It's a good sounding idea but could get rather complicated.
You manually disconnect the hopper by left clicking with a bare hand.
If you want to transport items from A to B, you have to use hoppers. (You can also use chest minecarts, but they're too complicated for our purposes.) However, hoppers have a few problems:
They're expensive: 5 iron per block seems like a ripoff
They can't transport items upwards without the help of noisy droppers
They can only suck items from below
A row of hoppers looks inordinately ugly
They're slow (only 1 item per tick per block)
The Solution
I propose to fix the above problems by adding one new block, the Pipe, and significantly overhauling the Hopper. We'll deal with the latter first.
Hopper Changes
The crafting recipe for hoppers should be changed slightly: instead of requiring 5 iron and 1 chest, it takes 5 copper (see attachment 1).
Hoppers change visually. They are now copper instead of iron, reflecting their appearance, and the pipe now exits into the center of a block face.
Hopper placing is changed. Hoppers can now suck from any direction. Hopper placing rules are as follows:
If a hopper is placed on a container or any block while sneaking, it sucks from that container or block.
If a hopper is placed on any other block, it sucks from above.
Hoppers connect to all adjacent hoppers, pipes, and containers.
Pipes
Pipes are new blocks that can carry items much faster than current hopper chains. They are crafted from 3 copper, producing 4 pipes (see attachment 2). Pipes take input from hoppers and output to containers or the ground. Pipe placing rules are as follows:
By default, pipes connect to all adjacent hoppers, pipes, and containers.
If you left click on a pipe connection with a bare hand, it will disconnect the pipes, or reconnect them if disconnected. This allows closer spacing and tighter control of pipe flow.
At dead ends, if an air block is adjacent, pipes drop their contents. If no air blocks are adjacent, the pipes clog up; pipes can store 1 stack per block.
One additional suggestion relating to railways: Make them grow out from cities, but end abruptly after a hundred or so blocks. This gives the impression that they are there, but doesn't give free transportation from one to another.
You know, I've had a similar idea, under a different name (the Engineer). It would buy redstone (and probably now copper) and would sell simple redstone elements, like repeaters, lamps, pistons, iron doors, and dispensers. The engineer's house would contain various redstone elements in action, including a one-block piston hatch leading down to a secret basement with more circutry and a chest filled with (you guessed it) more redstone and stuff.
Support. I'd imagined naturally-generated cities to basically be larger villages; your post goes all in on the mechanics. One thing I'd suggest would be to make cities out of similar materials as villagers, but (in plains, for example) with more bricks, stone bricks, concrete, and possibly a new tar block for roads. I'd also suggest certain conditions on where they'd generate; it'd make sense for them to be situated on rivers (with generation taking them into account, building bridges over them), and possibly modifying city structure slightlyh for coastal cities.
If you don't mind me, can I include some of your concepts in my yet hypothetical modpack?
0
Simple Graphical Tweaks: Limited support. I'm in favor of grass creeping over one-block ledges and connected (and more transparent) glass, but others like tree roots seem unnecessary.
Built-in texture packs: Some support. I'd think a bare-bones, flat, redstone-optimised pack and a 32x32 packk, plus a few minor shaders, would be enough.
Minor terrain gen changes:
2
I see no problems with this!
Support
0
Support. However, I think that there should be only one glowing color.
0
Note that:
- existing hoppers are unchanged: they still suck from above and output below
- my new hopper/pipe system is no more complex than the existing system, unless there are multiple input hoppers or nearby containers: you simply shift-place the hopper on the input container and add pipes connecting the hopper to the output container. Special care would only be needed if there are multiple hoppers or containers that you do not want to connect.
@Palin You bring up a good point with water; I did not consider that. I'd assume pipes would be balanced by being faster than water, but having a lower throughput, as well as being intuitive and more versatile.
I might post an alternative (and likely simpler) solution to the problem of hopper/pipe connection later; tell me if you're interested.
0
Correct.
That could work, but it'd be harder to precisely control, and would add more blocks than necessary.
It'd be completely backwards-compatible with existing systems: preexisting iron hoppers would be converted into new copper hoppers with input from above and output unchanged. Since hoppers count as containers, existing hopper chains do not transmit any faster.,
Yes, but the order is changed slightly. Instead of placing the hopper to connect to the output, you would place it to connect to the input.
The outlet(s) are to any adjacent containers or pipes; there can be multiple outlets to one hopper. If a hopper connects to a pipe or container that you don't want it to connect it to, simply left click with a bare hand on the faulty connection.
Input container first, hopper second, then add the pipe.
Hoppers are placed with the input face pointed towards the container it is placed on, and output to all other connecting containers and pipes unless manually disconnected. Hoppers fill from the input face, and empty everywhere else.
You manually disconnect the hopper by left clicking with a bare hand.
0
M'est, i mi respondet ke.
0
The Problem
If you want to transport items from A to B, you have to use hoppers. (You can also use chest minecarts, but they're too complicated for our purposes.) However, hoppers have a few problems:
The Solution
I propose to fix the above problems by adding one new block, the Pipe, and significantly overhauling the Hopper. We'll deal with the latter first.
Hopper Changes
Pipes
Pipes are new blocks that can carry items much faster than current hopper chains. They are crafted from 3 copper, producing 4 pipes (see attachment 2). Pipes take input from hoppers and output to containers or the ground. Pipe placing rules are as follows:
0
One additional suggestion relating to railways: Make them grow out from cities, but end abruptly after a hundred or so blocks. This gives the impression that they are there, but doesn't give free transportation from one to another.
0
You know, I've had a similar idea, under a different name (the Engineer). It would buy redstone (and probably now copper) and would sell simple redstone elements, like repeaters, lamps, pistons, iron doors, and dispensers. The engineer's house would contain various redstone elements in action, including a one-block piston hatch leading down to a secret basement with more circutry and a chest filled with (you guessed it) more redstone and stuff.
0
My opinion: Instead of adding dedicated mechs, add new blocks to make it easier and smaller to make complex piston flying machines.
0
Support. I'd imagined naturally-generated cities to basically be larger villages; your post goes all in on the mechanics. One thing I'd suggest would be to make cities out of similar materials as villagers, but (in plains, for example) with more bricks, stone bricks, concrete, and possibly a new tar block for roads. I'd also suggest certain conditions on where they'd generate; it'd make sense for them to be situated on rivers (with generation taking them into account, building bridges over them), and possibly modifying city structure slightlyh for coastal cities.
If you don't mind me, can I include some of your concepts in my yet hypothetical modpack?
0
Nope.
Do there exist any odd perfect numbers?
:D:D:D
0
You get 414 jen.
I insert a glider from Conway's Game of Life.
0
Nope.
Have you ever watched YTPs?
0
Some dark demonic magic.