Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.