Based on?
You don't spend 2.5bil to buy a community to kill it, and you don't earn 2.5bil being an idiot about business. I'm pretty sure Microsoft has an understanding that Minecraft has a large and diverse modding community. There's been a lot of issues; drama, legal misunderstandings, lack of api progress, and other things driving a rift between Mojang and a lot of the modding community as well. Pretending that its been some peachy happy party the whole way thus far is just rose coloured glasses. In the long run, the acquisition may prove beneficial, but I am certain it won't mean the death of the community.
-
- im3733
- Registered Member
-
Member for 13 years, 9 months, and 26 days
Last active Mon, Jan, 26 2015 13:11:13
- 0 Followers
- 34 Total Posts
- 4 Thanks
4
64 is six bits ("111111", actually 63, I'm assuming a zero-index), if notch is using a 2 byte data value (8 bits, 1 byte = 4 bit), that leaves 2 bits for some other data in the memory (like metadata, damage values, etc), what the remaining bits are actually used for, i'm not sure.
1
For creating the Microchip/Interated Cicuit itself it should be a (somewhat) expensive recipe, to help maintain balance.
So the chip would start out with crafting a wafer
Or
and it would give between 2 and 4 wafers (depending on the final recipe)
These wafers are essentially a silicon "base" for the final chip (using sand as it is a natural silison source IRL)
The second part of the chip would be the IC (integrated circuit) itself
and it would give 1-4 ICs, but the recipe and output will be changed to better match the final recipe and output for the wafer
Finally, the two items would be combined to make the final, programmable, placeable, chip
This recipe would yield 1 microchip.
My next thought was to use a "programmer" workbench that would use a GUI similar to the one in OP, this would allow you to "plug in" your newly crafted chip and supply the materials (redstone dust and sand/dirt) used to make the circuit.
Borrowing from TheEvilM in this thread, I decided the following.
The gui should provide Redstone wires, although, instead of what was suggested in the aforementioned thread, only have one wire option, but have the wire directionality be toggleable, AKA, right click on it to cycle through all the various connection options (straight, corners, three-way junctions, and four-way junctions, all rotateable), this would allow every space on the board to be used, without needing to make a bunch of extra buttons. These wires would be converted from Redstone dusts in a 1:1 ratio, and (ideally) can be converted back (whether they can be stored in inventory is up for debate, if so, they will NOT be placeable in the world , at least, not at first).
In order to facilitate logic gates, there has to be some form of Redstone torch, possibly called "pins" what these will look like is open to discussion, but they will function EXACTLY like normal Redstone torches, and will be converted from Redstone torches in a 1:1 ratio. In terms of converting back and inventory storage, it will be the same as the Redstone wires.
There would also be an block (possibly called an insulator, open to debate) crafted from sand/dirt (something cheap) which would be used to make various gates, I.E, placing a Redstone wire, then a block, then a "pin", it will function as a "not" gate, just like if you did it in the world. Again, the conversion back and inventory storage will be just like the "pins" and wires.
A debateable item would be a "replicator" bench, which would copy the design inside a chip into another chip. The design for this gui would be similar to that of the furnace, a set of spaces for raw materials (redstone dust, dirt/sand, and Redstone torches), a space for unprogrammed chips, a space for the "master" programmed chip, and an output slot. If this is implemented, unprogrammed chips might end up being stackable so that you can mass produce that adder chip you built for your 128-bit calculator.
I'm working on the GUIs for the programmer and replicator workbenches. I will post them here once they're done I have completed the GUI for the programmer bench. Replicator bench GUI soon to come.Bench GUIs are now completed and uploaded, you can view them below.
The recipe for the bench itself i'm not sure about yet, but i think it should include Redstone dust and possibly iron/gold (as these are excellent conductors IRL).
Possible restrictions/features:
Chips:
4 I/O "ports" on the four sides of the tile, labeled by (currently blue)dots, also labeled within the programming GUI.
cannot contain other chips, the (real life)resources it would take to recursively place chips inside each other so you can have a "computer" chip (no pun intended), is far too much for this to be viable
a chip is limited to 8x8x3 spaces, this will allow you to build some of the more complex circuits, but not all of them.
Chips cannot be stacked, but two chips placed next to each other (input to output) will work properly (tenatively, may require 1 Redstone dust in between, at least in early versions)
Chips will need to be collected with a pickaxe, or they may get "wiped" (open to debate)
unprogrammed chips can be stacked, but chips that have been programmed will only be stackable if they have been created by a replicator, similar to the rechargable batteries or energy crystals in IndustrialCraft.
Programmer Bench:
Chips can be reprogrammed, AKA, placed back on the board to be modified/finished. This way, if a user runs out of a material, they don't have to craft a whole new chip to finish it.
Users will be able to label their chips, otherwise, there will be no way to tell which chip is your 5 clock and which is your RS NOR Latch.
Replicator Bench:
It will require fuel of some kind, possibly pulsing redstone(?) or some other form of non-fossil (preferably electricity-based) fuel (AKA, the fuel used here can't also be used in the furnace).
Replication will stop as soon as any of the materials/fuel run out, however, a check is done before each chip is started to ensure that it doesn't run out mid-replication.
All replicated chips will have the same name/label as the master chip, which (may) allow them to be stacked.
As has been stated in several related posts, probably the single largest hurdle will be making the microchip function once programmed and placed. If I can conquer that, the rest will be easy.
Any and all feedback is appreciated.