Updating enum used as key in persistable map variable causes backwards compat issue

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Publishing

Summary

See Persistable error when trying to publish
Created an enum for my project. Used that enum as a key in a [enum]float map variable inside a save data class. Updating that enum with new entries (regardless of placement within the enum) leads to backwards compatibility issue when trying to publish.

Steps to Reproduce

  1. Create an enum with any number of entries.
  2. Create a save data class that uses that enum as key in a map (MyMapVar : [enum]float = map{})
  3. Publish.
  4. Add an entry to the enum you created.
  5. Publish

Expected Result

No backwards compatibility issues arise as a result of changing the enum (but not changing the save data).

Observed Result

Backwards compatibility issue arises as a result of changing the enum, even without changing the save data.

Platform(s)

PC

Island Code

9356-8963-7602

Additional Notes

It doesn’t appear that the save data can be changed to accommodate a new entry in the enum in any meaningful way. Even if I stopped using the previous variable and create a new one with a different format, the backwards compat issue will still be there. I can’t rollback to a previous version since the save data was there from first publish. If an enum marked as persistable is meant to be a valid persistable type, then updating it shouldn’t be an issue.