ID 471873 - [FrameHold] Scripts saved in Nuke13 are not keeping value of FrameHold first frame knob when reopened in Nuke12

Problem summary
Scripts saved in Nuke13 are not keeping value of FrameHold first frame knob when reopened in Nuke12

Customer reported version
nuke.13.0v1

Customer reported platform

N/A

Steps to reproduce

1) Open Nuke 13.0v1

2) Create a FrameHold node

3) Set the first frame knob to 1234, using value, expressions or animation.

4) Save the Script

5) Open the script in Nuke 12.2v6, it will error saying:

FrameHold1.firstFrame: no such knobFrameHold1.1234: no such knob

7) Open the node properties, the knob labeled knob is set to 0, not 1234.

Or

1) Open the attached Nuke script in Nuke 12.2v6, it will error saying:

FrameHold1.firstFrame: no such knobFrameHold1.1234: no such knob

2) Open the node properties, the knob labeled knob is set to 0, not 1234.

Expected behaviour
For the FrameHold node to load correctly into different versions of nuke

Actual behaviour
Nuke 13.0v1 renamed the first_frame knob to firstFrame, without versioning the node

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:

Nuke 13.0v1 - Windows 10, Centos 7

Unable to reproduce bug in:

Nuke 12.2v6 - Windows 10, Centos 7
 

Earliest version tested
Nuke 12.2v6 - This issue doesn't appear in this version and has regressed