Redstone Circuit Board

This section introduces basic usages, from creating a scheme, to deploy your circuit board. Everything would be just decent.
1 Create Scheme
2 Design Circuit
3 Deploy Circuit

The idea of pin comes from the chip. A chip use its pin to receive or emit signal with other components on circuit board.

In our plugin, the pin transfer redstone signal with its neighbouring blocks or circuit boards.


To place a pin, use stone button (not redstone lamp, sorry for bewildering) at the map, so it will be place at where you point at.

There're two types of pin in general:

• Input Pin (Yellow): receive signal from its neighbouring board or block.
• Output Pin (Gray): emit signal to neighbouring board or block.

The pin should be placed at the border of the circuit board, otherwise it won't be able to work.
The word neighbouring means those who are adjacent to the block where the circuit board occupied.
(In the first picture, the redstone lamp is neighbouring to the right circuit board, and the left and right circuit board are adjacent.)

Please notice that the pin doesn't work well when communicating with other redstone components. The APIs of different Minecraft version have incoherence. So some function works well in some version doesn't guarantee working in other version.

The word 'Overclocking' means to raise the clock rate of a CPU when it comes to computer circuits.

In your plugin, overclocking means to raise the refresh frequency of our circuit. By default, our circuit will refresh once per server tick. But you are allowed to set this refresh rate to more than once.

To overclock, you just need to set the internalTick in the config.yml to more than 1, and then reload the server. Then the circuit board will run at the frequency you want.

Overclocking will consume more CPU resources, obviously. So the TPS of your server may descend when overclocking.
And setting the internal tick too large may even cause your server side application to stop running. So use at your own risk.
It's fair to set the internal tick to less than 20, which will bring you the profit of overclocking without affecting your server side performance violently.

Hello folks. This update brings us the command block into the circuit board. The most terrifying function of Minecraft.

You should use a command block item to place the command block. You should have mcb.cmdblock permission before you do anything future with command block.


By right-clicking on the the command block, the detailed information of this command block is shown, including who has just edited the command block, the command you set, the last output of this command block, and whether this command block is emiting power. (I'm sorry that it is confirmed impossible for a plugin to open a command block GUI, it's completely a client side action ).


To set the command of the command block, you should use the command /mppctl cmdblock update <new command>. In this picture, I use /testfor @a to test whether there's anyone online.


A command block need power to activate (execute its inner command if set), and emit its power if adjacent to a comparator.

To demonstrate how it works, I even add a clock circuit to activate, and two more command block for output. Then I deploy the circuit.


Firstly I left the game. Then the upper command is activated, its output is 'no' as I set its command to '/me no'.


Then I join back to my server. The command block detects my join, and activate the lower command block, outputing 'yes' as I set its command to '/me yes'.


Finally I have to warn you that this function is so powerful, that it is possible to summon such 'ender crystal drill' in a few seconds by using /summon EnderCrystal ... Do whatever you like, but use it at your own risk.