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
Since the names and their formats are kind of all over the place right now, I guess this requires a standardized naming convention for the Static weapons. Ideally before we ship out a version in the FP Modpack.
To kick this off, I'd like to suggest the following for the russian weapons:
6P50-1 'KORD'
6P50-1 'KORD' (Raised)
And for the american weapons this:
M2HB
M2HB (Raised)
The '(Raised)' Attribute would indicate that the weapon is not a low positioned weapon, which is also in line with the Bohemia standard of labeling the Low and High variants of a static weapon.
The text was updated successfully, but these errors were encountered:
Your current suggestions seems good to me, what about the naming convention for the bags though?
Should we keep the FP prefix on the bags or not? And will we follow vanilla bag naming or should we keep it the way we currently do it?
I'd say Simply drop the FP Prefix. We don't have as many Backpacks in Arsenal, so it won't make things too unorganized compared to something like the Uniform category.
Reduced amount of bags by ~40%, but was required to have Seperate weapon bags for Lowered and Raised Static weapon variants (Vanilla is limited by the same issue)
Since the names and their formats are kind of all over the place right now, I guess this requires a standardized naming convention for the Static weapons. Ideally before we ship out a version in the FP Modpack.
@Cuel
@Kauwgompje
@Mallow234
@Tinter
Any Suggestions?
To kick this off, I'd like to suggest the following for the russian weapons:
And for the american weapons this:
The '(Raised)' Attribute would indicate that the weapon is not a low positioned weapon, which is also in line with the Bohemia standard of labeling the Low and High variants of a static weapon.
The text was updated successfully, but these errors were encountered: