安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
3 
举报此帖
Ammotype function label same in KK INS DOI Addon.
So when the two add-ons are running at the same time,
loading the ammunition of that weapon crashes. That is Empty ammo conflict.
If it is just an add-on with the same weapon,
there will not be a conflict if you use only one,
but conflicts with other add-ons may arise due to the problem of addon code structure.
I know That's point.
And the same weapon, but due to different factors, the two add-ons have a conflict factor.
melee attack function haven't in original CW2.0 function.
(The bayonet had in original CW2.0, but what I'm trying to say here is to do melee attacks right from the gun. Not imply a bayonet in a separate weapon.)
and Grenade capability is also compatible ammunition, but not compatible with guns.
(Grenade function means E + attack1 function in CW2.0 gun, not grenade weapon with icon in the inventory window.)
So far, this was the add-on conflict issue that I discovered.
And even if that is not the case, CW2.0 crashes can happen anywhere.
In my case, the crashing factor often disappeared when cleaning old CW2.0 add-ons.