You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a way to autogenerate entries in iprp_feats.2da would be great; I might script this but easier if EOS did it.
The gist would be the standard CEP/PRC way where each feat.2da line + 100 goes into iprp_feats.2da
However a selective option would be nice per-feat (or a default on/off, and if default on it has a dropdown to default / enable / disable explicitly per entry) - the custom EOS field could even suggest which line ID it'd be.
The iprp_feat.2da lines would need to stay consistent since once they're item properties changing them later becomes a mess. 100 + feat.2da line is pretty standard so sensible to do it that way.
Wouldn't need custom iprp_feats.2da entries then at all either.
The text was updated successfully, but these errors were encountered:
Having a way to autogenerate entries in iprp_feats.2da would be great; I might script this but easier if EOS did it.
The gist would be the standard CEP/PRC way where each feat.2da line + 100 goes into iprp_feats.2da
However a selective option would be nice per-feat (or a default on/off, and if default on it has a dropdown to default / enable / disable explicitly per entry) - the custom EOS field could even suggest which line ID it'd be.
The iprp_feat.2da lines would need to stay consistent since once they're item properties changing them later becomes a mess. 100 + feat.2da line is pretty standard so sensible to do it that way.
Wouldn't need custom iprp_feats.2da entries then at all either.
The text was updated successfully, but these errors were encountered: