This idea makes having to craft a sticky piston through the crafting interface irrelevant and expands the usefulness of the slime ball.
Slime Balls
Allow the slime ball to be a surface treatment to ANY side of a solid block (not gravel, sand, dirt, leaves, etc.) (like red stone is typically a surface treatment to the tops of blocks), and can be reclaimed like red stone.
This Creates a 'glue' that when placed between 2 blocks, allows the second block to be pulled in the direction of the first block. (You can apply it to the surface of a normal piston plate to make a sticky piston rather than going through the crafting interface).
Pro: it can effectively extend the range/reach of a push/pull piston operation (up to 13 blocks)
Note: Slime Balls will remain with the block/surface originally adhered to if the adhesion is broken. slime balls do not offer lateral support, a push/pull sideways across the surface of adhesion will break the bond.
Spikes
(Recipe: 1 bar of iron in Bottom Right and Bottom Left corner makes 6 spikes).
Crafted with an iron bars for a set of spikes. similarly applied as a surface treatment to block faces. Can be used to create a surface that does damage to creatures that move over or into them.(as cactus). when placed between blocks, creates lateral (or sideways) support, but no push/pull support. (pulling a block away will break the spike bond between blocks).
Note: Spikes will remain with the block face that they were initially applied to in the event block contact is broken by a push/pull action.
Red Stone spikes
(Recipe: Spike and red stone dust).
Like Spikes (above), but retractable if red stone power is applied.
Red Stone Rod
(Recipe: Blaze Rod and Red Stone dust), creates a rod that can transmit red stone power (like red stone) 'through' blocks. the rod is inserted in any direction into a block and creates to contact points on opposite sides of the same block, can intersect rods in the same block along different faces if branching or a direction change is needed. Rods can be removed as red stone, and connects easily to normal red stone and other res stone rods
Pro: Can run separate lines of red stone power close to each other without cross signal contamination (tighter bundles)
Pro: Can embed wiring inside blocks so it is less obvious, easier to hide
Pro: Can go in vertical directions both ways very efficiently
Con: more expensive to make
Con: more difficult to construct embedded and harder to troubleshoot because you can't easily see it in operation.
Limitations would be the same for push/pull (13 blocks), but instead of having all 13 in a straight line out from a piston, the piston could (for example) push a block that is the center of a 3x3 flat square (1 square thick) with spikes in between the blocks, and move it all as one unit (like a platform going up/down or a wall moving in/out)
----------------
Additionally, I'd like it if any surface treatments (red stone, torches, repeaters, buttons, levers, pressure plates, etc.) would move with any blocks (unless scraped off by sliding that side against another block), as it is right now, if a block that has something like this attached, it pops off when the block is moved.
(Yes, I would like to be able to use pistons to move around red stone connections).
(Recipe: Blaze Rod and Red Stone dust), creates a rod that can transmit red stone power (like red stone) 'through' blocks. the rod is inserted in any direction into a block and creates to contact points on opposite sides of the same block, can intersect rods in the same block along different faces if branching or a direction change is needed. Rods can be removed as red stone, and connects easily to normal red stone and other res stone rods
Basically just put a repeater facing a block and give it power and power transfer through the whole block on all sides so this one is useless
Basically just put a repeater facing a block and give it power and power transfer through the whole block on all sides so this one is useless
You missed the point of this. Or are otherwise not seeing it...
I could have 13 blocks in a row, all with redstone rods (like inside wiring) running through all of them, with redstone circuitry all around the blocks on the sides and top/bottom that do not get contaminated, but redstone power would run through the core of those 13 blocks providing endpoint to endpoint power, and it is hidden 'in the wall, and it goes up or down easily, and it can change corners when 2/3 rods are used in the same block space.
It's like creating an insulated cable inside (and using) the current block architecture as the insulator.
This you cannot do with your repeater example.
Edit: In addition to a cross tie interface with multiple rods, it could use a placement strategy to transmit between adjacent sides instead of opposite sides by placing at angles (this would allow carrying a redstone current around a corner without cross tying multiple rods in the same block space)
Advantage, less visible sings around corners (aesthetics / won't see a glowing red dot on the exposed ends), less material to go around a corner.
I have to reconsider this idea some more.... I've stumbled upon some issues with incorporating much of this idea into the current game mechanics programatically....
Here is the problem:
Most surface treatments in the game are actually separate blocks. (Redstone Dust, Minecart Rails, snow, carpet (from Java v.1.7), Paintings, Item Frames, signs, etc.) technically, none of these occupies the 'same' space as the blocks they are applied to, but they rather occupy the block space next to (or above) the block they are attached to (and you cannot place another 'block' in that same space). {The exception being 2 slabs of the same type, the game gets around this by replacing each individual slab with a separate block ID 2-slab block of the same type, and you cannot mix/match different types.}
This logical representing everything 'as blocks that occupy space' would cause an issue when trying to place adhesive and spikes 'between' blocks, which would ultimately require tracking this with meta-data associated with those blocks... and according to a wiki resource I've recently read, pistons cannot push/pull blocks that have meta data associated with them (nor extended pistons). This meta-data issue is gotten around in the case of the sticky piston by making it a completely different block than the piston (thus not requiring meta data). But if meta-data is used to track stuff like paint on walls/floors/ceiling (as was suggested in: http://www.minecraft.../1897037-paint/), or spikes and slime adhesives as described above, then this rule would have to be overlooked in some circumstances in order for this idea to work overall.
Plus there would need to be a way to attribute meta data to a block that doesn't normally carry meta-data.
I think it is still doable, but at the same time, it has become slightly more complex than I had first envisioned based on current game design.
You missed the point of this. Or are otherwise not seeing it...
I could have 13 blocks in a row, all with redstone rods (like inside wiring) running through all of them, with redstone circuitry all around the blocks on the sides and top/bottom that do not get contaminated, but redstone power would run through the core of those 13 blocks providing endpoint to endpoint power, and it is hidden 'in the wall, and it goes up or down easily, and it can change corners when 2/3 rods are used in the same block space.
It's like creating an insulated cable inside (and using) the current block architecture as the insulator.
This you cannot do with your repeater example.
Edit: In addition to a cross tie interface with multiple rods, it could use a placement strategy to transmit between adjacent sides instead of opposite sides by placing at angles (this would allow carrying a redstone current around a corner without cross tying multiple rods in the same block space)
Advantage, less visible sings around corners (aesthetics / won't see a glowing red dot on the exposed ends), less material to go around a corner.
Well.. What if when you put one inside a block, it has a thing that goes onto the block with something that has a similar look to say... a plug-in on one of your walls in your house? (in real life).. But it doesn't take up any space outside the block (similar to a torch, or any item really) and just gave the block a "skin" of that look (so it doesn't take up and extra block of space) But does the power transfer also through that block in the way you intended?
PSN:
Junokaii (although I'd recommend not adding me because I'm on literally like... once every month or two)
Member Details
Just because it sounds like there is issues with, trying to distinguish... But.. I guess the point is to NOT have visible parts... So my bad I missed that part.
Uhh... I guess it's really just all up to the player to memorize which parts they put those rods in.
Well.. What if when you put one inside a block, it has a thing that goes onto the block with something that has a similar look to say... a plug-in on one of your walls in your house? (in real life).. But it doesn't take up any space outside the block (similar to a torch, or any item really) and just gave the block a "skin" of that look (so it doesn't take up and extra block of space) But does the power transfer also through that block in the way you intended?
I was thinking that the 'endpoints' where the 'rod' goes through would look similar to a spot of redstone dust that was either dark (inactive) or illuminated red (active). (but not visible from the other 4 sides (unless a cross-tie rod was also used to connect between 2 other sides)
Just because it sounds like there is issues with, trying to distinguish... But.. I guess the point is to NOT have visible parts... So my bad I missed that part.
Uhh... I guess it's really just all up to the player to memorize which parts they put those rods in.
Only partially to help conceal the redstone, but also to help prevent cross-talk issues by insulating the lines on the other sides from each other as well as to make a more efficient system to go vertically (up/down)
PSN:
Junokaii (although I'd recommend not adding me because I'm on literally like... once every month or two)
Member Details
If it's made right.. I don't see why Redstone dust can't just have the ability to be put on walls equally as good as on the ground. I mean.. when you have a piece of redstone go down a block to another level.. instead of it being diagonal like rail, one it just goes strait.. then up and down vertically then strait again. If it can be down with a piece of redstone like that.. why not just make it have the ability to go up and down anyway?
If it's done right.. it could actually look pretty nice.
If it's made right.. I don't see why Redstone dust can't just have the ability to be put on walls equally as good as on the ground. I mean.. when you have a piece of redstone go down a block to another level.. instead of it being diagonal like rail, one it just goes strait.. then up and down vertically then strait again. If it can be down with a piece of redstone like that.. why not just make it have the ability to go up and down anyway?
If it's done right.. it could actually look pretty nice.
Technically... I don't see why this couldn't be done (+1 support)
Technically... I don't see why this couldn't be done (+1 support)
Thanks. yeah. I don't see why not. In fact.. I wondered this for a very long time.
also same.. with in correlation with a thread I made about being able to lay down glowstone dust like redstone.. I proposed having it be layed down in the same manner as redstone dust.. and have it actually give off a nice glow too. Not as much as a glowstone block... But a nice little faint glow.
Slime Balls
Allow the slime ball to be a surface treatment to ANY side of a solid block (not gravel, sand, dirt, leaves, etc.) (like red stone is typically a surface treatment to the tops of blocks), and can be reclaimed like red stone.
This Creates a 'glue' that when placed between 2 blocks, allows the second block to be pulled in the direction of the first block. (You can apply it to the surface of a normal piston plate to make a sticky piston rather than going through the crafting interface).
Pro: it can effectively extend the range/reach of a push/pull piston operation (up to 13 blocks)
Note: Slime Balls will remain with the block/surface originally adhered to if the adhesion is broken. slime balls do not offer lateral support, a push/pull sideways across the surface of adhesion will break the bond.
Spikes
(Recipe: 1 bar of iron in Bottom Right and Bottom Left corner makes 6 spikes).
Crafted with an iron bars for a set of spikes. similarly applied as a surface treatment to block faces. Can be used to create a surface that does damage to creatures that move over or into them.(as cactus). when placed between blocks, creates lateral (or sideways) support, but no push/pull support. (pulling a block away will break the spike bond between blocks).
Note: Spikes will remain with the block face that they were initially applied to in the event block contact is broken by a push/pull action.
Red Stone spikes
(Recipe: Spike and red stone dust).
Like Spikes (above), but retractable if red stone power is applied.
Red Stone Rod
(Recipe: Blaze Rod and Red Stone dust), creates a rod that can transmit red stone power (like red stone) 'through' blocks. the rod is inserted in any direction into a block and creates to contact points on opposite sides of the same block, can intersect rods in the same block along different faces if branching or a direction change is needed. Rods can be removed as red stone, and connects easily to normal red stone and other res stone rods
Pro: Can run separate lines of red stone power close to each other without cross signal contamination (tighter bundles)
Pro: Can embed wiring inside blocks so it is less obvious, easier to hide
Pro: Can go in vertical directions both ways very efficiently
Con: more expensive to make
Con: more difficult to construct embedded and harder to troubleshoot because you can't easily see it in operation.
Traps, yes, but red stone mechanisms in general.
Limitations would be the same for push/pull (13 blocks), but instead of having all 13 in a straight line out from a piston, the piston could (for example) push a block that is the center of a 3x3 flat square (1 square thick) with spikes in between the blocks, and move it all as one unit (like a platform going up/down or a wall moving in/out)
----------------
Additionally, I'd like it if any surface treatments (red stone, torches, repeaters, buttons, levers, pressure plates, etc.) would move with any blocks (unless scraped off by sliding that side against another block), as it is right now, if a block that has something like this attached, it pops off when the block is moved.
(Yes, I would like to be able to use pistons to move around red stone connections).
(slime ball applied to normal spikes) Offers adhesion in all directions, have to break the block in order to separate.
Basically just put a repeater facing a block and give it power and power transfer through the whole block on all sides so this one is useless
You missed the point of this. Or are otherwise not seeing it...
I could have 13 blocks in a row, all with redstone rods (like inside wiring) running through all of them, with redstone circuitry all around the blocks on the sides and top/bottom that do not get contaminated, but redstone power would run through the core of those 13 blocks providing endpoint to endpoint power, and it is hidden 'in the wall, and it goes up or down easily, and it can change corners when 2/3 rods are used in the same block space.
It's like creating an insulated cable inside (and using) the current block architecture as the insulator.
This you cannot do with your repeater example.
Edit: In addition to a cross tie interface with multiple rods, it could use a placement strategy to transmit between adjacent sides instead of opposite sides by placing at angles (this would allow carrying a redstone current around a corner without cross tying multiple rods in the same block space)
Advantage, less visible sings around corners (aesthetics / won't see a glowing red dot on the exposed ends), less material to go around a corner.
Here is the problem:
Most surface treatments in the game are actually separate blocks. (Redstone Dust, Minecart Rails, snow, carpet (from Java v.1.7), Paintings, Item Frames, signs, etc.) technically, none of these occupies the 'same' space as the blocks they are applied to, but they rather occupy the block space next to (or above) the block they are attached to (and you cannot place another 'block' in that same space). {The exception being 2 slabs of the same type, the game gets around this by replacing each individual slab with a separate block ID 2-slab block of the same type, and you cannot mix/match different types.}
This logical representing everything 'as blocks that occupy space' would cause an issue when trying to place adhesive and spikes 'between' blocks, which would ultimately require tracking this with meta-data associated with those blocks... and according to a wiki resource I've recently read, pistons cannot push/pull blocks that have meta data associated with them (nor extended pistons). This meta-data issue is gotten around in the case of the sticky piston by making it a completely different block than the piston (thus not requiring meta data). But if meta-data is used to track stuff like paint on walls/floors/ceiling (as was suggested in: http://www.minecraft.../1897037-paint/), or spikes and slime adhesives as described above, then this rule would have to be overlooked in some circumstances in order for this idea to work overall.
Plus there would need to be a way to attribute meta data to a block that doesn't normally carry meta-data.
I think it is still doable, but at the same time, it has become slightly more complex than I had first envisioned based on current game design.
Well.. What if when you put one inside a block, it has a thing that goes onto the block with something that has a similar look to say... a plug-in on one of your walls in your house? (in real life).. But it doesn't take up any space outside the block (similar to a torch, or any item really) and just gave the block a "skin" of that look (so it doesn't take up and extra block of space) But does the power transfer also through that block in the way you intended?
Uhh... I guess it's really just all up to the player to memorize which parts they put those rods in.
I was thinking that the 'endpoints' where the 'rod' goes through would look similar to a spot of redstone dust that was either dark (inactive) or illuminated red (active). (but not visible from the other 4 sides (unless a cross-tie rod was also used to connect between 2 other sides)
Only partially to help conceal the redstone, but also to help prevent cross-talk issues by insulating the lines on the other sides from each other as well as to make a more efficient system to go vertically (up/down)
If it's done right.. it could actually look pretty nice.
Technically... I don't see why this couldn't be done (+1 support)
Thanks. yeah. I don't see why not. In fact.. I wondered this for a very long time.
also same.. with in correlation with a thread I made about being able to lay down glowstone dust like redstone.. I proposed having it be layed down in the same manner as redstone dust.. and have it actually give off a nice glow too. Not as much as a glowstone block... But a nice little faint glow.
http://www.minecraftforum.net/topic/1878998-being-able-to-place-glowstone-dust-to-light-up-places/