What I suspect is happening here is not everyone being familiar with how Git submodules work? The example project is directly referencing a couple of plugins, and you can see the references pointing at specific SHAs here:
A submodule is like a sub-project, a way for a Git project to directly reference and use another Git repo. Unfortunately they aren’t super straight forward to work with…
Some info here, but basically after syncing down my example project you need to initialize and then pull the referenced submodules with Git:
https://git-scm.com/book/en/v2/Git-Tools-Submodules
I believe Koderz’s latest version of PMC has proper support for collisions. I’ll try to get my code updated to his latest plugin soon ™.
Well… kinda 
I haven’t implemented actual L-system parsing logic here, but it’s something I’m planning on do when I find some free time