Redacted

cridgitcridgit Posts: 1,757

​Redacted

Post edited by cridgit on

Comments

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    That's the problem with encrypted scripts...they are more or less tied to the version they are encrypted in.

    One option, I guess, would be to go the full, compiled plug in route, since I doubt you would go with unencrypted scripts that get compiled at runtime, by the current running version...

  • ReDaveReDave Posts: 815
    edited December 1969

    Simple solution is to encrypt them in the oldest version of DS you have. You can safely ignore any errors the script IDE of said old DS version throws at you, of course, as long as the script works in whichever version it is supposed to work..

  • cridgitcridgit Posts: 1,757
    edited May 2022

    ​Redacted

    Post edited by cridgit on
  • Richard HaseltineRichard Haseltine Posts: 100,711
    edited December 1969

    Yes, the binary formats (.dsb and .dse) are version-tagged and DS won't even try to open a file from a newer version. It would be hard to have older versions know how new a file they could safely open, I suppose, but it is generally an annoyance rather than a help.

Sign In or Register to comment.