[Major] v34.30 introduced a new editor validation error and when fixed it results in a cook validation error

General Issues and Bug Reporting
, , ,
5

I just want to make sure I’m understanding your example correctly, as it seems you have the following:

  • Default Map: vz_anomaly_1
  • Map Data:
    • Map[0]: vz_anomaly_1
      • Base Map: level_a_after_3430
      • Base Map: level_b_after_3430
    • Map[1]: level_a_after_3430
      • Base Map: level_b_after_3430
    • Map[2]: level_b_after_3430

The way the validation works is the “Default Map” and any “Map” entries in the “Map Data” array are considered “primary” maps for validation, and these are the maps we start to count from, including any specified base maps in their counts.

The validation is getting confused here because “level_a_after_3430” and “level_b_after_3430” are declared as both a “primary” map and a base map. If you deleted entries 1 and 2 from the “Map Data” array then the validation should pass.

Is there a reason you have it configured like this?

1 Like