Hello, The problem with RedStone is that you cant compact your circuitry as the RedStone continues to link together. Simple circuits have to be separated by a block or you have to use repeaters thus delaying your signals. The solution is to bring in BlueStone. My proposal is to allow players to use Lapis Lazuli as the source of BlueStone. BlueStone operates the same as RedStone. BlueStone connects power to the same items as redstone, including redstone torches, pistons and doors... etc. The difference is BlueStone is a separate wire. Allowing the player to lay BlueStone directly alongside RedStone without connecting to it. Also a intersection block would be nice allowing the player the cross-over a RedStone wire without connecting to it. To increase functionality a connecting block, like a repeater would be required. A connecting block would allow BlueStone to connect to RedStone. Suggesting some like: x R x B G B x R x x - nothing B - BlueStone R - RedStone G - Gold Ingot Required blocks: - Same as RedStone except blue.... - Crossover block. - Where BlueStone intersects RedStone but does not join. - Connectors - Connecting RedStone and BlueStone Thanks Bring on EVEN smaller computers! Oh and maybe need a blue flower for dyes??? Meh...
read the stickies, plugins cannot add custom blocks. Lapis Lazuli is a item, and cannot be placed. Either call it a client mod or suggest using different blocks. I don't want to be mean, but the forum gets messy when there are more requests that cannot be fulfilled than those that can.
Sorry to be mean.... but read the title. "Spout required mod". Spout has the capability to create new blocks. As can be seen here: http://forums.bukkit.org/threads/ad...s-v1-4-add-custom-blocks-through-spout.40253/ Also there is a new (and already slightly outdated post) [READ FIRST] What can plugins actually do (using Spout)?
So I Shouldn't post ideas that are possible in the next release of Spout? Devs are already working with Spout block addition. [WIP] [FUN/GEN/TP/MECH/WGEN/RPG/MISC] Serenity - Pushing Spout custom items to the next level!
It is now possible to create new blocks with dev builds of Spout (a friend of mine made a marble texture that looks quite nice in game). Giving the block behaviors, such as transmitting power, it a bit further down the line.
Good to know, now I have evil plans on making very evil blocks on my server > my that was typed as > : ) became > EDIT by Moderator: merged posts, please use the edit button instead of double posting.
If anybody's interested, I'm making this a client mod as we speak. (although it will be Greenstone, so not to be confused with Lapis) Won't be done for a while though because as I get further into this, I see how complex it will actually be. Having this info, I can almost guarantee you will never be able to do this with Spout. Too many things to add/change.
Tedious? Try impossible. (I'm assuming so) There's too many files redstone goes through to do this. Heck, I'm having trouble doing it with a client mod! (although I've never actually made a client mod before) I've managed to make a green type of redstone, however it makes redstone AND greenstone green. Making it keep redstone red, but greenstone green is really kicking my butt. I know I have to add my method renderBlockGreenstoneWire() somewhere in this mess, but I don't understand this code: PHP: public boolean renderBlockByRenderType(Block block, int i, int j, int k) { int l = block.getRenderType(); block.setBlockBoundsBasedOnState(blockAccess, i, j, k); return l != 0 ? l != 4 ? l != 13 ? l != 1 ? l != 19 ? l != 6 ? l != 2 ? l != 3 ? l != 5 ? l != 8 ? l != 7 ? l != 9 ? l != 10 ? l != 11 ? l != 12 ? l != 14 ? l != 15 ? l != 16 ? l != 17 ? l != 18 ? l != 20 ? l != 21 ? ModLoader.RenderWorldBlock(this, blockAccess, i, j, k, block, l) : func_35923_a((BlockFenceGate)block, i, j, k) : func_35929_i(block, i, j, k) : func_35922_a((BlockPane)block, i, j, k) : renderPistonExtension(block, i, j, k, true) : renderPistonBase(block, i, j, k, false) : renderBlockRepeater(block, i, j, k) : renderBlockBed(block, i, j, k) : renderBlockLever(block, i, j, k) : func_35925_a((BlockFence)block, i, j, k) : renderBlockStairs(block, i, j, k) : renderBlockMinecartTrack((BlockRail)block, i, j, k) : renderBlockDoor(block, i, j, k) : renderBlockLadder(block, i, j, k) : renderBlockRedstoneWire(block, i, j, k) : renderBlockFire(block, i, j, k) : renderBlockTorch(block, i, j, k) : func_35930_l(block, i, j, k) : renderBlockCrops(block, i, j, k) : renderBlockReed(block, i, j, k) : renderBlockCactus(block, i, j, k) : renderBlockFluids(block, i, j, k) : renderStandardBlock(block, i, j, k); } I know that if I replace renderBlockRedstoneWire() with my method renderBlockGreenstoneWire(), everything will turn green. But somehow I need it to turn BlockRedstoneWire RED and BlockGreenstoneWire GREEN. Notice in this image how GREENSTONE (on the right) is still red. You can tell it is greenstone because of the green particle effects. renderBlockRedstoneWire() turns them both red. (Redstone is on the left, Greenstone is on the right. Greenstone isn't support to be red. At this time, Greenstone still connects to Redstone.)
@DrAgonmoray Well you would have to thoroughly duplicate every Redstone class/method/object. I'm not quite sure how redstone works in vanilla MC though.
That's essentially what I'm doing, although the effects like particles and color isn't like that. Edit: Nevermind. I had/have like 10 minutes before I go to school, and while I was brushing my teeth, the answer occured to me. So I got on the computer real quick and fixed it: Now, I'm off to school.
I find your lack of faith... disturbing. Yes, rendering of a redstone lookalike will require code on the client, but Spout will be launching our Spoutcraft SP API in mere weeks.
Oh, excuse me. I completely forgot about the client API. My apologies for the lack of thinking on my part :|
@Afforess You give me great hope! @DrAgonmoray Congrats on the Greenstone glow. Hope you consider using spout eventually...
Interested parties can go here to read a bit about Spoutcraft's SP API: https://github.com/SpoutDev/SpoutcraftAPI/blob/master/README.md
Lol thanks. Now Greenstone Torches are giving me issues with the texture in hand not displaying correctly. >.> Excellent! Can't wait! EDIT by Moderator: merged posts, please use the edit button instead of double posting.
Quick question, why are you adding Greenstone torches? Why not power them from redstone torches? The true use of another type of colour wire is the ability to shrink our circuits. Just curious.
Well if greenstone is separate from redstone, I don't see why redstone torches shouldn't be separate too. Although now that I think about it, there are several cases when you would NEED 1 torch to power both.. Hmm. You have a point. Bai bai greenstone torch I suppose now the next order of business is to make the two types of wires not connect. I can't find the class(es) that control it though :|
Hope this gets a chance of being a reality, I can see MANY uses of this... it will fix a lot of problems i'm guessing. The idea reminds me of this mod... http://www.minecraftforum.net/topic...ed-redstone-now-redpower-logic-redstone-pipe/ Scroll down to redpower wiring
I guarantee you will be able to do this with spout, you'd just need to implement your own redstone calculations.
I actually got very far into the client mod, but the calculations were the problem. They confuzzled me, and I really didn't see how they were done
I get that @DrAgonmoray is making this but I think I will start on a Spout version after I am done with the current plugins that I am developing (one of which I am at a stand still on the last thing). I should be able to start this in, at the most, a week.
???????????????????????? I can't start on this right away because Spout doesn't like me. I am going to have to wait until the client for 1.0.0 comes out before I start. It keeps giving me the Spout "white screen of death" no matter what I do. @Lock add me on Skype to go over the fine details of this: Jogy341 EDIT by Moderator: merged posts, please use the edit button instead of double posting.
