🟢 How does GSE currently work
Encryption currently works on single exports not mass exporting

🟢 Describe the solution you'd like
Extend encryption to the Mass Export Patreon Version of GSE

🟢 Additional context
Thank you Tim!

What I am thinking with this is to perform a number of changes to Restricting Sequences:

Change Current Options:

• Set Read-Only
• Disable Editor
  to
• Lock Information - Lock Author, URL, Help Information.
• Disable Raw Edit
• Disable Export

There are a number of reasons for this.

• The need for users to be able to change things like [mods] and https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/wiki/KeyBinding#sky-riding-when-using-keybinds
• Transparency over what is actually happening
• Need to protect Creators work
• Moving storage to a host like WAGO.io would make sequences viewable anyway.
• Consistent experience irrespective of exporting as a collection or individually

That all sounds great Tim - thank you!

In light of wago.io allowing complete inline edits and forks putting these restrictions in are now meaningless. There has been no further feedback since announcing this on Discord so closing this out as complete.

They also have options for encryption if people want to use it when importing or they can even change it after importing

What I mean is once you have a string - I can’t enforce that the author or url aren’t changed in the wago editor after you import it to your own wago account.