Sorry, was a misinformation, that is only the case with VeterancyLevels+ created PRE-patch13, post-patch13 created ones work correctly
Currently it is not possible to fully/partial remove levels (indexes) from "Veterancy Levels +"-Array
if you simply remove the entries of the entry - they are regenerated and bugged (just indexes, nothing else available)
this happens if you remove one or more levels of the veterancylevels+
picture of the bug :
even changing the array value to (in RawData) " :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: " (without quotes) which should empty the array (taken from a new created VeterancyBehavior) will still have the indexes
Sorry, was a misinformation, that is only the case with VeterancyLevels+ created PRE-patch13, post-patch13 created ones work correctly
Currently it is not possible to fully/partial remove levels (indexes) from "Veterancy Levels +"-Array
if you simply remove the entries of the entry - they are regenerated and bugged (just indexes, nothing else available)
this happens if you remove one or more levels of the veterancylevels+
picture of the bug :
even changing the array value to (in RawData) " :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: "
(without quotes) which should empty the array (taken from a new created VeterancyBehavior) will still have the indexes