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
There's currently not a great tag to use for mods that are associated with playing from IVA mode. Right now most of them use "crewed" but there are lots of crewed parts that don't have IVAs and some things related to IVAs that have nothing to do with crew (probecontrolroom etc).
Suggestion
We should standardize a new tag. After discussion with HebaruSan, first-person seems to be the best choice. IVA was considered but is less desirable because it requires familiarity with the acronym.
See if the tag can be auto-detected by the mod analyzer (look for Spaces or Props folders, INTERNAL or PROP in configs, etc) - Analyze first-person tag NetKAN-Infra#324
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
(Rearranged the checkboxes slightly to reflect the ordering that I think would work best.)
Updating the existing netkans would be easy enough to do in a big pull request. Do you want to start that? I know GitHub's web UI doesn't make it trivial to update multiple files, so I can assist with that piece.
... added a list of existing netkans to get the brainstorming started.
Problem
There's currently not a great tag to use for mods that are associated with playing from IVA mode. Right now most of them use "crewed" but there are lots of crewed parts that don't have IVAs and some things related to IVAs that have nothing to do with crew (probecontrolroom etc).
Suggestion
We should standardize a new tag. After discussion with HebaruSan,
first-person
seems to be the best choice.IVA
was considered but is less desirable because it requires familiarity with the acronym.There are 3 parts to this task:
https://github.com/KSP-CKAN/CKAN/wiki/Suggested-Tags
ALCORIVAPatch(frozen)Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: