Working redstone and TNT plugin

It's easy to implement redstone. It's hard to implement redstone well. First of all you must have excellent knowledge in redstone mechanism. For example, look at this side view setup:

Code:

  X=_i
___BB

B stands for generic blocks, i is a power source, and _ stands for redstone wire. = means that there is a redstone wire plus another redstone wire into the screen. If X is a redstone lamp, it won't glow. What happens if X is a TNT?
The answer is that the = block will appear as a T-shaped intersection, and pointing towards the TNT, but it won't explode.
There are lots of marginal cases like this. You have to understand all the wiring mechanism very well and think of a lot of marginal cases. In addition, you have to think of how to optimize performance and minimize lag. According to my observation in the disassembly of the MCPE app, MCPE seems to handle stuff as "circuits"; I don't understand how this can be done though.

 

One has to know a lot to know how little he knows. I know much enough to understand that I know too little.

 

Because if you add redstone, you have to add all the things together, or it's a waste of time. You can't make a functional lever without expecting that the block behind would be charged, redstone wire to be charged strongly or weakly, etc. And then you have to think of many other possible thingsthat might charge a Redstone wire, and how redstone signal is transmitted, and much more to think.

The hard thing is to implement the redstone theory behind. The blocks like redstone, lever, etc. are just users of the redstone theory, and it's very easy to make them once the underlying redstone theory is implemented.

 

Many people do. But very few know well enough to make it work efficiently.

 

I never said so. I just said it's hard to do it well.

 

No thread bumping thanks. Locking.