The End of C.O.F.F.E.E.

On 03/11/2017 at 08:26, xxxxxxxx wrote:

Dear Community,

With upcoming internal changes, all support for the C.O.F.F.E.E. programming language will be removed with the next major release of Cinema 4D. No more C.O.F.F.E.E. plug-ins and no C.O.F.F.E.E. scripting within scenes (C.O.F.F.E.E. Scripting Tag, XPresso C.O.F.F.E.E. Scripting Node, MoGraph C.O.F.F.E.E. Effector, Interaction Tag) will be supported. For all these, a Python alternative will be available. Plug-ins or scripts written in C.O.F.F.E.E. will need to be ported to either Python or C++ in order to make further use of them.

We are aware that this decision may be quite irritating for some. It wasn't an easy decision to make. Sometimes you need to break with the past in order to approach a bright future.
Rest assured, we (MAXON's SDK Team) will do our best to help you use Cinema's Python and C++ SDKs. We will release a small plug-in at MAXON Labs in the not too distant future, which can be used to inspect scenes and detect any use of C.O.F.F.E.E. Future versions of Cinema 4D will also warn the user when a scene containing C.O.F.F.E.E. is loaded. In such cases (at the minimum) the next version of Cinema 4D will still show the C.O.F.F.E.E. source code in C.O.F.F.E.E. Scripting Tag, XPresso C.O.F.F.E.E. Scripting Node, MoGraph C.O.F.F.E.E. Effector and Interaction Tag but the code will not be executed anymore. This way it is still possible to port the code, even though C.O.F.F.E.E. was already removed.


On 05/11/2017 at 12:36, xxxxxxxx wrote:

shocked slightly!