r/technicalminecraft • u/bringemichum • Mar 10 '26
Java Showcase Zombie wih looting spear killing chamber
Rework my witch farm today. I know someone has done this already. But It looks very fun.
r/technicalminecraft • u/bringemichum • Mar 10 '26
Rework my witch farm today. I know someone has done this already. But It looks very fun.
r/technicalminecraft • u/CrafterAurora • Apr 09 '25
https://www.youtube.com/watch?v=ZUUn1Cy2eo0
^– More full showcase
r/technicalminecraft • u/Superkennethias • Dec 10 '23
r/technicalminecraft
•
u/Quiet-Cup-1501
•
Jul 20 '26
Sugarcane needs an adjacent water source, so max-density layout is a coverage problem: each water tile hydrates up to 4 neighbors, capping theoretical density at 80% regardless of arrangement.
I modeled it as an integer program (CP-SAT / OR-Tools) to solve for the provably optimal water placement on a given plot:
Standard community pattern: 66.7% density
Optimal: 75.3% (94% of the theoretical ceiling)
On open/unconstrained terrain the solution converges to a hexagonal-ish tiling and hits the full 80%
The honest trade-off: this optimizes purely for space/density, not for automation. The irregular water placement breaks observer-based harvesting since you lose the clean rows and water-transport paths. I think it's still automatable with slime flying machines, but I haven't tested that in practice.
Where it actually shines is irregular plots or obstacle-heavy terrain, where there's no established pattern to copy and manual intuition falls apart.
Code, more grid sizes, and obstacle-terrain examples: https://github.com/Serranegra/optifarm
Curious if anyone here has cracked automating a non-uniform cane layout (that's the open problem this leaves)
r/technicalminecraft • u/_amongstreality • Jul 07 '26
Cushions are insane
r/technicalminecraft • u/mattbatwings2 • Aug 29 '21
r/technicalminecraft
•
u/PlainOats
•
Mar 08 '26
Not sure if this has been shown before, but as long as their target stays loaded, skulker bullets navigate to their coordinates even if they are in the wrong dimension. You can use this to manipulate shulker bullet movement by moving the target entity. If the target dies or is unloaded (including the player logging out), the bullets drop to the ground immediately (this seems to be the result of their Target value being deleted), even if you reload the entity before they hit the ground.
My gut tells me something useful is possible with this but mentally I'm drawing a blank on it. Hope this is of some use to you all!
r/technicalminecraft • u/derex_smp • Mar 31 '26
i can't even
r/technicalminecraft • u/Reasonable-Fact-2434 • Oct 08 '26
why don't we build sugarcane farms like this
especially for flying machines farms
thanks to u/JumpingPufferfish31 because he explained why its bad and for u/UPOTATO8 because he built and comparing it
the better one is optifarm or you can call it 1 to 4/1:4
r/technicalminecraft
•
u/ProposalFlaky7237
•
Mar 03 '26
Edited: not the first, sorry for the confusion.
After an unreasonable amount of time, I've built a functional CPU in Minecraft that operates entirely on 0-tick mechanics — meaning all logical operations complete within a single redstone tick.
Architecture Overview
The CPU is built exclusively from redstone dust and pistons. No repeaters, no comparators, no torches — components that typically introduce delay or state complexity are entirely absent. Also no command blocks or mods. All timing behavior is derived from 0-tick piston glitches, which allow state transitions to propagate and resolve within one tick.
The design follows a strict 1-cycle principle: there are no internal subcycles. An operation initiated on a rising clock edge produces its result before the cycle closes. This required careful signal path analysis to ensure no intermediate states persist across cycle boundaries.
ALU
The ALU supports five operations: AND, OR, XOR, Add, Subtract. Scope was intentionally limited to demonstrate architectural viability rather than operational completeness.
XOR gates present a known hazard in 0-tick contexts: if two inputs transition from 0,0 to 1,1 but arrive at different times, an intermediate 1,0 state produces a spurious output pulse that breaks downstream circuits. To address this, the ALU sits behind a synchronization gateway. The gate is held closed until a dedicated presence signal arrives. This signal is routed to guarantee it arrives only after all data inputs have fully settled — eliminating the hazard window.
Registers
The CPU has 4 registers. Each register is implemented as two cascaded D flip-flops to guarantee read-cycle integrity. The first DFF updates on write. The second DFF holds the previous value and updates only on the falling clock edge. This allows a register to be both source and destination in the same instruction — the read value remains stable throughout the cycle regardless of the write operation occurring in parallel.
Decay Sequencing
Clock shutdown follows a strict ordered sequence to prevent state corruption:
Register input gate closes — prevents a decaying ALU result from being latched.
Presence signal deactivates — closes the ALU synchronization gate, protecting XOR inputs from asynchronous fade (the 1,1 → 0,0 intermediate state problem, symmetric to the setup hazard).
Register output safely transitions to the new value.
Clock receives a feedback signal confirming the cycle has fully terminated and the next cycle may begin.
Clock Rate
The 0-tick mechanism requires a mechanical reset period of approximately 1 second. Effective clock rate is ~1 Hz.
What's Missing
There are no memory operations. The CPU has no load/store instructions and no addressable memory. This is a proof-of-concept for the 0-tick single-cycle execution model — implementing memory would require a substantial piston array that is disproportionate to the demonstrative value of the project at this stage. The architecture supports future memory integration in principle.
Performance
Surprisingly, the performance is not awful. It was all built on an old laptop and can perform one operation per second without serious lag.
Summary
This demonstrates that a functional single-cycle CPU architecture is achievable within 0-tick constraints using only redstone and pistons. The primary contributions are the synchronization gateway pattern for XOR hazard elimination, the dual-DFF register design for same-register read/write integrity, and the decay sequence for clean cycle termination.
PS. there's a prototype development ground on coordinates (0, 0) where you can inspect each part separately. The fully assembled CPU is on (0, -300).
You can download the world on my GitHub: https://github.com/HironTez/0-tick-cpu-minecraft
r/technicalminecraft • u/GNamimates18 • Aug 18 '21
r/technicalminecraft • u/Lazy_Profession_8803 • Sep 03 '24
r/technicalminecraft • u/Empoleon_Master • Feb 05 '21
r/technicalminecraft • u/DEEGOBOOSTER • Aug 02 '21
r/technicalminecraft • u/Out_of_Ideas12 • Aug 30 '26
r/technicalminecraft • u/DanzenPlays • Mar 18 '26
Java 1.21.11
Messing around and discovered this. Works with a disabled hopper. Seems like some kind of update suppression? Is this known?
Edit: Just to summarise some additional findings. Only hoppers seem to work, other redstone components do not react the same way. The hopper can be place on any side of the water source, even under. In fact, the hopper does not even need to be adjacent to the water source. Anything that updates the non-source water block immediately after the hopper such as adding or removing blocks (including the hopper itself) causes the stream to dissipate. Lava streams can be similarly cut off. Lastly, it is not a ghost block since it remains even after logging off and back on.
r/technicalminecraft • u/TheOPWarrior208 • Feb 11 '21
r/technicalminecraft • u/Coolguy1802 • Sep 13 '25
After watching RedLogic’s new video on mob pathfinding, I was inspired to create this cheat sheet.
r/technicalminecraft • u/nathan19512009 • Dec 17 '23
r/technicalminecraft • u/mattbatwings2 • Aug 07 '21