-
Notifications
You must be signed in to change notification settings - Fork 741
Compat WS - Change realisticname wording for Stripe camos #10592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
RF C-More already has a camouflage version called "Desert/Woodland" (originally Wood). so WS "Stripes" should will be the same. If "Stripes" were to be called the "Camo", it would be confusing because there is already a "Camo" for three. |
|
Even if this is technically correct, we should use the same suffix as the CDLC and only change the name of the sight/weapon itself. Is that the case here? |
|
Umh, I'm not really sure what he's say correctly (Sorry I'm not native as English), but anyway, this doesn't change the prefixes, it just changes the names given to the color/camo variants to make them more distinguishable. For example, in XMS, these names were originally as follows: XMS 5.56mm //Colored as Black However, in the current RealisticName, they are as follows: XMS There is no problem with changing "Stripes" to Camo, since there is no other "camouflaged" XMS currently. So this may be fine as it is. but it's nonsence. However, C-More (ACO) is different. ACO is as follows in Vanilla: ACO (Green) //Vanilla, Colored as Black There are three types of camouflage specifications as above. But Currently in Realistic Name: C-More Railway (Green) "Stripes" will be worsened to not clear what camo it is. BTW: There are also similar name problems in vanilla and GM6. |
|
Hey @Psycool3695 It's been a while. 줄무늬 is ok? |
it's difficult to simply translate it as "줄무늬" because that texture is a bit different from the stripes commonly referred to in Korea. |
|
After discussing with Psycool (Korean Translator) on Twitter(X), the Korean translation was completed without any problems, so there is no problem with merging. |
When merged this pull request will:
IMPORTANT
Component - Add|Fix|Improve|Change|Make|Remove {changes}.