matrix property variable naming convention insconsistent thus leads

Naming a property node inside shader forge automatically adds an underscore at the beginning of the variable on the code side. That is good! Unfortunately and unexpectedly the matrix property is an exception to this convention as it will not receive the underscore. The result of this was a bug failing a c#-script to link to the matrix property of the SF shader. This was explicitly hard to track down as it was also followed up by another bug with matrix multiply that always disconnects channel A in the muliply matrix node. The first bug can be worked around simply via manually adding the underscore to the matrix node name inside the editor. Unfortunately the bug with the disconnecting "channel A" in matrix multiply persists.