It used to provide Mesecons last year (2024). The redstone was mesecon under the hood which enabled many many mods on ContentDB to just work with this game. Then they changed it into mcl_redstone and removed the entire API. This broke all my mods and hundreds from other people and when asked about this they think that's fine. I recommend playing VoxeLibre instead which is the original, this project forked from. (I do not have any affiliation with either project. This is an honest review.) All these things still work perfectly fine there.
And the bow also doesn't behave correctly with immortal entities provided by mods. That also works perfectly fine with the VoxeLibre bow.
The download number is inflated compared to VoxeLibre because Mineclonia pushes updates more often. So don't be influenced by that. Look at the statistics tab.
You can simply install mesecons with mcla and it will actually work with mesecons mods because "mcl/redstone-mesecons" is only partly compatible with mesecons.
Which is one of the main reasons we removed it. Your client should automatically install mesecons from contentdb if some mods depends on it!?
What do you mean by MCLA? Mineclonia? No that actually does not work. I've tried. Redstone does not connect to my mesecon receptor. The redstone contraptions like pistons won't work with MVPS breaks fucking everything too.
In VoxeLibre all that works perfectly. A vanilla redstone piston in the game can push a node and entity and the entity and node will do all their mesecons mvps stuff.
It seems you can get mesecons to work but it involves a lot of manual fiddling. By default it only enables the hard dependencies and not the optional mesecons depenedencies like mesecons_mvps and you can't enable the entire modpack by itself because not all is compatible with Mineclonia. Mesecons Extra Wires can be enabled but crashes the game. Really poor idea of compatibility and user friendlyness.
Further you have to use separate mesecon wires and nothing works with each other. So it's entirely pointless.
And even with all that the Mineclonia bow does not work with my Target node because it has weird behavior different from VoxeLibre bow and all other weapon mods and won't run the on_punch of my immortal entity.
Well yeah but you can use it with the normal mesecons things. Just a heads up though VL is planning to eventually do this as well.
See the codeberg discussion for more details as to why; tl;dr the compatibility used to be very rudimentary (while using the same namespace) and hence caused many problems.
As mentioned on codeberg i'll look into the bow thing though
For me the only mesecons mod that didn't work with mcla (yes mineclonia) is mesecons_doors but that is simply due to the fact that it depends on mtg doors...
The mesecons API is designed around the fact that circuits are digital and not analog. That makes it very difficult to rework while keeping things compatible. The reason Mineclonia is still beta and we have not yet released 1.0.0 is because a few breaking changes are still to be expected. As cora said VoxeLibre is working on replacing mesecons with their own implementation (vl_redstone) as we speak. I would not be surprised if they also break compatibility when they are finished with it.
Edit 2025-01-28: It appears like VoxeLibre will try to keep compatibility in their rewrite.
Our priority is to reproduce Minecraft. Backward compatibility is a nicety but if it gets in the way, you may expect it to be dispensed with. By contrast, playing VoxeLibre entails sacrificing this fidelity to Minecraft for their creative vision--the choice is yours.
Your complaint is valid, but replacing it was a fantastic decision, the mesecons redstone doesn't work like Minecraft's at all.
Mineclonia's replacement has pretty accurate and intuitive redstone, whereas Voxelibre's redstone is weird and wonky, when your expectation is Minecraft's redstone.
It used to provide Mesecons last year (2024). The redstone was mesecon under the hood which enabled many many mods on ContentDB to just work with this game. Then they changed it into mcl_redstone and removed the entire API. This broke all my mods and hundreds from other people and when asked about this they think that's fine. I recommend playing VoxeLibre instead which is the original, this project forked from. (I do not have any affiliation with either project. This is an honest review.) All these things still work perfectly fine there.
And the bow also doesn't behave correctly with immortal entities provided by mods. That also works perfectly fine with the VoxeLibre bow.
The download number is inflated compared to VoxeLibre because Mineclonia pushes updates more often. So don't be influenced by that. Look at the statistics tab.
You can simply install mesecons with mcla and it will actually work with mesecons mods because "mcl/redstone-mesecons" is only partly compatible with mesecons.
Which is one of the main reasons we removed it. Your client should automatically install mesecons from contentdb if some mods depends on it!?
What do you mean by MCLA? Mineclonia? No that actually does not work. I've tried. Redstone does not connect to my mesecon receptor. The redstone contraptions like pistons won't work with MVPS breaks fucking everything too. In VoxeLibre all that works perfectly. A vanilla redstone piston in the game can push a node and entity and the entity and node will do all their mesecons mvps stuff.
It seems you can get mesecons to work but it involves a lot of manual fiddling. By default it only enables the hard dependencies and not the optional mesecons depenedencies like mesecons_mvps and you can't enable the entire modpack by itself because not all is compatible with Mineclonia. Mesecons Extra Wires can be enabled but crashes the game. Really poor idea of compatibility and user friendlyness. Further you have to use separate mesecon wires and nothing works with each other. So it's entirely pointless.
And even with all that the Mineclonia bow does not work with my Target node because it has weird behavior different from VoxeLibre bow and all other weapon mods and won't run the on_punch of my immortal entity.
Well yeah but you can use it with the normal mesecons things. Just a heads up though VL is planning to eventually do this as well.
See the codeberg discussion for more details as to why; tl;dr the compatibility used to be very rudimentary (while using the same namespace) and hence caused many problems.
As mentioned on codeberg i'll look into the bow thing though
For me the only mesecons mod that didn't work with mcla (yes mineclonia) is mesecons_doors but that is simply due to the fact that it depends on mtg doors...
The mesecons API is designed around the fact that circuits are digital and not analog. That makes it very difficult to rework while keeping things compatible. The reason Mineclonia is still beta and we have not yet released 1.0.0 is because a few breaking changes are still to be expected. As cora said VoxeLibre is working on replacing mesecons with their own implementation (vl_redstone) as we speak. I would not be surprised if they also break compatibility when they are finished with it.
Edit 2025-01-28: It appears like VoxeLibre will try to keep compatibility in their rewrite.
Our priority is to reproduce Minecraft. Backward compatibility is a nicety but if it gets in the way, you may expect it to be dispensed with. By contrast, playing VoxeLibre entails sacrificing this fidelity to Minecraft for their creative vision--the choice is yours.
Your complaint is valid, but replacing it was a fantastic decision, the mesecons redstone doesn't work like Minecraft's at all. Mineclonia's replacement has pretty accurate and intuitive redstone, whereas Voxelibre's redstone is weird and wonky, when your expectation is Minecraft's redstone.
But that is not enough to put a hand down.