CBMicroblocks recently added support for custom microblock materials via Inter Mod Messages.

It is possible to use a .cfg to manually include all the blocks from Chisel, but it would be much nicer if Chisel had native support for CBMicroblocks. It would also mean that if and when blocks are added or change name, you wouldn't have to go back and edit the .cfg.

Documentation is in the CBMultipart wiki.

I'm not sure what Chisel's stance is on mod compatibility, but this would be a nice thing to have, as Chisel and CBMicroblocks go quite well together.

As a workaround, i made a custom-micromaterials.cfg file: https://gist.github.com/rafern/9ab3fb58696bdfd7b347045e2f0331bf.

If you wanna make your own, using some linux commands:

1. clone the chisel repository (git clone https://github.com/Chisel-Team/Chisel)
2. cd into base/src/generated/resources/assets/chisel/blockstates
3. run find . > temp.txt
4. open temp.txt in the current directory
5. remove the line containing a single dot
6. remove the line containing auto_chisel.json
7. replace all ./ occurrences with chisel:
8. remove all lines that match the regex ^chisel:(?!.*\.json).*$. if you're using sublime text, ctrl+f, paste the regex, click find all and double backspace
9. replace all .json occurrences with nothing
10. replace all diabase occurrences with basalt (i think this will break in the future)
11. put the contents of temp.txt into custom-micromaterials.cfg

I may be missing a step or two

It would be nice to know how well microblocks works with chisel. Does it support CTM properly?

It sadly doesn't work with CTM, but apart from that it works like you'd expect it. And by doesn't work I mean that it uses the texture for a single block, so while it doesn't look glitchy or anything, it doesn't connect the textures. Apart from that I've personally not had any issues with Chisel and Microblocks in the past.