It amazes me that so many wonderful new things can be added and enhanced in each ZBrush release… and yet there are sneaky little documented and reported bugs that seem to survive like roaches through many generations of ZBrush code.
My personal pet peeve:
Many years back I ZScripted a neat little material manager (called ZMats) that permitted the user to easily save and retrieve Z-materials. This was back before MatCap even. When a material was saved, the lighting and the color setup was also saved so you could guarantee the reloaded material would look exactly like it did when you saved it. It all worked and it was simple and very useful providing a way to organize and manage a library of up to 2000 materials and 400 separate lighting setups.
With the release of 3.0, a bug was introduced, a strange little bug that would instantly crash ZBrush when a light setup was saved IF THE Light menu was NOT MANUALLY/PHYSICALLY OPENED FIRST. Huh?
Anyway, the work-around (suggested by Pixologic at the time) was to simply include the ZScript Show command to momentarily open the Light menu the first time a Light was saved during any ZBrush session. It was a “temporary solution” but it worked and the ZMats 3 plugin was released.
Then, with the release of 3.1, the work-around stopped working. I think it was because the Show command and several other related ZScript commands originally intended to be used during interactive tutorials inside ZBrush were modified or disabled completely. At the same time, the strange little Light menu bug that crashed ZBrush still remained.
And ever since, that little bug survived, intact, through releases 3.2 and 3.5, so I simply disabled the ability to save light setups from the plugin.
I am frustrated to report that the bug STILL SURVIVES in the 4.0 release of ZBrush (and I’d be willing to bet it could have been fixed by changing one or two lines of ZBrush source code, three releases ago.)
I know it seems a little thing, but it’s not. ZBrush 4.0 can instantly and reliably be made to crash with one unfortunate script command (IPress, Light:Save before the Light menu has been physically opened) and that is simply unacceptable, especially since the bug has been reported through several betas.
I doubt it will ever be fixed. If there is to be an updated version of ZMats for 4.0, it will be without the ability to save lighting setups… unfortunate - because with the new Best Preview Render and the enhanced options for materials, lighting setups become VERY relevant again.
Sven
Darukin: ZScripted control of the Timeline was a dream I had entertained too. Maybe in 5.0. 
Digits: I sure do wish you were able to release 4.0 updates for all those wonderful scripts of yours. Nice to see your name here again, btw!