Missing Rifles Problem - Revision history

Lou Montana: Some wiki formatting

2026-01-11T16:55:08Z

Some wiki formatting

← Older revision		Revision as of 18:55, 11 January 2026
Line 1:		Line 1:
	The "missing rifles problem" or "missing rifles bug" was introduced in ~~Armed Assault~~ version 1.08 due to a slight config change made by the developers. The bug is triggered by certain addons that contain references to some old weapon classes, causing all rifles in the game to become invisible and infantry to shoot from their chest.		The "missing rifles problem" or "missing rifles bug" was introduced in {{arma1}} version 1.08 due to a slight config change made by the developers.
			The bug is triggered by certain addons that contain references to some old weapon classes, causing all rifles in the game to become invisible and infantry to shoot from their chest.


	== Fixing the bug ==		== Fixing the bug ==
Line 11:		Line 13:
	=== Step 2: Create mod folders ===		=== Step 2: Create mod folders ===

	It is not advisable to have unofficial addons in the standard addon folder. If you have not done so already, create a new folder called ''@NewAddons'' inside your Armed Assault installation folder (i.e.: ''C:\Program Files\Armed Assault''). Inside this ''@NewAddons'' folder, create another folder called ''Addons''. This will be the future location for your third party addons. See the article on ~~[[ArmA~~:~~_Startup_Parameters~~\|~~ArmA~~ startup parameters]] for more information on how to use mod folders. You will need to add ''-mod=@NewAddons'' to your ~~ArmA~~ desktop link.		It is not advisable to have unofficial addons in the standard addon folder.
			If you have not done so already, create a new folder called ''@NewAddons'' inside your Armed Assault installation folder (i.e.: ''C:\Program Files\Armed Assault'').
			Inside this ''@NewAddons'' folder, create another folder called ''Addons''. This will be the future location for your third party addons.
			See the article on {{Link\|Armed Assault: Startup Parameters\|{{Name\|arma1\|short}} startup parameters}} for more information on how to use mod folders.
			You will need to add ''-mod=@NewAddons'' to your {{arma1}} desktop link.

	=== Step 3: Identify the culprits ===		=== Step 3: Identify the culprits ===

	The most straightforward way to identify the addon(s) that are causing the bug, is to put them into your third party addons one by one, and start the game after each addon is replaced. If you experience the no rifles bug after starting the game, the most recently replaced addon will be the cause. The addon in question will need to be removed. Make sure to follow this procedure for all third party addons, to ensure that all culprits are identified.		The most straightforward way to identify the addon(s) that are causing the bug, is to put them into your third party addons one by one, and start the game after each addon is replaced.
			If you experience the no rifles bug after starting the game, the most recently replaced addon will be the cause.
			The addon in question will need to be removed. Make sure to follow this procedure for all third party addons, to ensure that all culprits are identified.

	=== Step 4: Download new addon versions ===		=== Step 4: Download new addon versions ===
Line 24:		Line 32:
	== Technical Aspects ==		== Technical Aspects ==

	The problem comes forth out of the fact that BIS changed the Rifle class from Rifle: Mgun to Rifle: Riflecore (and more of those changes)		The problem comes forth out of the fact that BIS changed the Rifle class from <syntaxhighlight lang="cpp" inline>class Rifle : Mgun</syntaxhighlight> to <syntaxhighlight lang="cpp" inline>class Rifle : Riflecore</syntaxhighlight> (and more of those changes)

	You can resolve the matter in addons by searching for: class Rifle: Mgun {};		You can resolve the matter in addons by searching for: <syntaxhighlight lang="cpp" inline>class Rifle : Mgun {};</syntaxhighlight>

	in the Addon config.cpp and replace it with: class Rifle;		in the Addon config.cpp and replace it with: <syntaxhighlight lang="cpp" inline>class Rifle;</syntaxhighlight>

	The new ~~ArmA~~ inheritance system allows to simply supply the classname and a ; at the end to inherit classes from other addons		The new {{arma1}} inheritance system allows to simply supply the classname and a {{hl\|;}} at the end to inherit classes from other addons

	(You should actually use this new method for all your class inheritances!)		(You should actually use this new method for all your class inheritances!)


	{{GameCategory\|arma1\|Troubleshooting}}		{{GameCategory\|arma1\|Troubleshooting}}

Lou Montana: Text replacement - "y[ _]\|[ _](arma[0-9]+)[ _]*\|[ _]+" to "y|$1|"

2021-06-22T12:10:04Z

Text replacement - "y[ _]*\|[ _]*(arma[0-9]+)[ _]*\|[ _]+" to "y|$1|"

← Older revision		Revision as of 14:10, 22 June 2021
Line 34:		Line 34:
	(You should actually use this new method for all your class inheritances!)		(You should actually use this new method for all your class inheritances!)

	{{GameCategory\|arma1\| Troubleshooting}}		{{GameCategory\|arma1\|Troubleshooting}}

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "

2021-01-31T17:57:27Z

Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

← Older revision		Revision as of 19:57, 31 January 2021
Line 1:		Line 1:
	The "missing rifles problem" or "missing rifles bug" was introduced in Armed Assault version 1.08 due to a slight config change made by the developers. The bug is triggered by certain addons that contain references to some old weapon classes, causing all rifles in the game to become invisible and infantry to shoot from their chest.		The "missing rifles problem" or "missing rifles bug" was introduced in Armed Assault version 1.08 due to a slight config change made by the developers. The bug is triggered by certain addons that contain references to some old weapon classes, causing all rifles in the game to become invisible and infantry to shoot from their chest.

	==Fixing the bug==		== Fixing the bug ==

	The bug can easily be fixed by removing those addons from the game that are causing the problem. These addons will most likely contain custom rifles. If you are unable to immediately identify the addons in question, try following the steps below.		The bug can easily be fixed by removing those addons from the game that are causing the problem. These addons will most likely contain custom rifles. If you are unable to immediately identify the addons in question, try following the steps below.

	===Step 1: Remove all third party addons===		=== Step 1: Remove all third party addons ===

	First, make sure you remove all unofficial addons from the Addons folder. Do not delete them, unless you are absolutely sure which ones are from third parties and which are from the original game. If this does not immediately solve the problem, make sure you are not using any mod folders. Once all unofficial addons and mods have been removed, the problem should be resolved.		First, make sure you remove all unofficial addons from the Addons folder. Do not delete them, unless you are absolutely sure which ones are from third parties and which are from the original game. If this does not immediately solve the problem, make sure you are not using any mod folders. Once all unofficial addons and mods have been removed, the problem should be resolved.

	===Step 2: Create mod folders===		=== Step 2: Create mod folders ===

	It is not advisable to have unofficial addons in the standard addon folder. If you have not done so already, create a new folder called ''@NewAddons'' inside your Armed Assault installation folder (i.e.: ''C:\Program Files\Armed Assault''). Inside this ''@NewAddons'' folder, create another folder called ''Addons''. This will be the future location for your third party addons. See the article on [[ArmA:_Startup_Parameters\|ArmA startup parameters]] for more information on how to use mod folders. You will need to add ''-mod=@NewAddons'' to your ArmA desktop link.		It is not advisable to have unofficial addons in the standard addon folder. If you have not done so already, create a new folder called ''@NewAddons'' inside your Armed Assault installation folder (i.e.: ''C:\Program Files\Armed Assault''). Inside this ''@NewAddons'' folder, create another folder called ''Addons''. This will be the future location for your third party addons. See the article on [[ArmA:_Startup_Parameters\|ArmA startup parameters]] for more information on how to use mod folders. You will need to add ''-mod=@NewAddons'' to your ArmA desktop link.

	===Step 3: Identify the culprits===		=== Step 3: Identify the culprits ===

	The most straightforward way to identify the addon(s) that are causing the bug, is to put them into your third party addons one by one, and start the game after each addon is replaced. If you experience the no rifles bug after starting the game, the most recently replaced addon will be the cause. The addon in question will need to be removed. Make sure to follow this procedure for all third party addons, to ensure that all culprits are identified.		The most straightforward way to identify the addon(s) that are causing the bug, is to put them into your third party addons one by one, and start the game after each addon is replaced. If you experience the no rifles bug after starting the game, the most recently replaced addon will be the cause. The addon in question will need to be removed. Make sure to follow this procedure for all third party addons, to ensure that all culprits are identified.

	===Step 4: Download new addon versions===		=== Step 4: Download new addon versions ===

	Most addon makers have acknowledged the problem since the release of patch 1.08 and have released updated versions of their addons. Make sure to download the latest version of these addons to ensure full compatibility with ArmA version 1.08 and above.		Most addon makers have acknowledged the problem since the release of patch 1.08 and have released updated versions of their addons. Make sure to download the latest version of these addons to ensure full compatibility with ArmA version 1.08 and above.

R3vo: Text replacement - "haven't" to "have not"

2021-01-18T08:14:40Z

Text replacement - "haven't" to "have not"

← Older revision		Revision as of 10:14, 18 January 2021
Line 11:		Line 11:
	===Step 2: Create mod folders===		===Step 2: Create mod folders===

	It is not advisable to have unofficial addons in the standard addon folder. If you ~~haven't~~ done so already, create a new folder called ''@NewAddons'' inside your Armed Assault installation folder (i.e.: ''C:\Program Files\Armed Assault''). Inside this ''@NewAddons'' folder, create another folder called ''Addons''. This will be the future location for your third party addons. See the article on [[ArmA:_Startup_Parameters\|ArmA startup parameters]] for more information on how to use mod folders. You will need to add ''-mod=@NewAddons'' to your ArmA desktop link.		It is not advisable to have unofficial addons in the standard addon folder. If you have not done so already, create a new folder called ''@NewAddons'' inside your Armed Assault installation folder (i.e.: ''C:\Program Files\Armed Assault''). Inside this ''@NewAddons'' folder, create another folder called ''Addons''. This will be the future location for your third party addons. See the article on [[ArmA:_Startup_Parameters\|ArmA startup parameters]] for more information on how to use mod folders. You will need to add ''-mod=@NewAddons'' to your ArmA desktop link.

	===Step 3: Identify the culprits===		===Step 3: Identify the culprits===

R3vo: Text replacement - "aren't" to "are not"

2021-01-18T00:44:56Z

Text replacement - "aren't" to "are not"

← Older revision		Revision as of 02:44, 18 January 2021
Line 7:		Line 7:
	===Step 1: Remove all third party addons===		===Step 1: Remove all third party addons===

	First, make sure you remove all unofficial addons from the Addons folder. Do not delete them, unless you are absolutely sure which ones are from third parties and which are from the original game. If this does not immediately solve the problem, make sure you ~~aren't~~ using any mod folders. Once all unofficial addons and mods have been removed, the problem should be resolved.		First, make sure you remove all unofficial addons from the Addons folder. Do not delete them, unless you are absolutely sure which ones are from third parties and which are from the original game. If this does not immediately solve the problem, make sure you are not using any mod folders. Once all unofficial addons and mods have been removed, the problem should be resolved.

	===Step 2: Create mod folders===		===Step 2: Create mod folders===

Lou Montana: Text replacement - "\[\[[Cc]ategory:ArmA:[ _]?([^|]+)\]\]" to "{{GameCategory|arma1|$1}}"

2021-01-06T13:43:52Z

Text replacement - "\[\[[Cc]ategory:ArmA:[ _]?([^|]+)\]\]" to "{{GameCategory|arma1|$1}}"

← Older revision		Revision as of 15:43, 6 January 2021
Line 34:		Line 34:
	(You should actually use this new method for all your class inheritances!)		(You should actually use this new method for all your class inheritances!)

	~~[[Category:ArmA:~~ Troubleshooting]]		{{GameCategory\|arma1\| Troubleshooting}}

Lou Montana: Add :Category:ArmA: Troubleshooting

2020-08-15T16:12:09Z

Add Category:ArmA: Troubleshooting

← Older revision		Revision as of 18:12, 15 August 2020
Line 33:		Line 33:

	(You should actually use this new method for all your class inheritances!)		(You should actually use this new method for all your class inheritances!)

			[[Category:ArmA: Troubleshooting]]

Sickboy: /* Technical Aspects */

2007-06-21T12:59:04Z

Technical Aspects

← Older revision		Revision as of 14:59, 21 June 2007
Line 25:		Line 25:

	The problem comes forth out of the fact that BIS changed the Rifle class from Rifle: Mgun to Rifle: Riflecore (and more of those changes)		The problem comes forth out of the fact that BIS changed the Rifle class from Rifle: Mgun to Rifle: Riflecore (and more of those changes)

	You can resolve the matter in addons by searching for: class Rifle: Mgun {};		You can resolve the matter in addons by searching for: class Rifle: Mgun {};

	in the Addon config.cpp and replace it with: class Rifle;		in the Addon config.cpp and replace it with: class Rifle;

	The new ArmA inheritance system allows to simply supply the classname and a ; at the end to inherit classes from other addons		The new ArmA inheritance system allows to simply supply the classname and a ; at the end to inherit classes from other addons

	(You should actually use this new method for all your class inheritances!)		(You should actually use this new method for all your class inheritances!)

Sickboy: /* Technical Aspects */

2007-06-21T12:58:34Z

Technical Aspects

← Older revision		Revision as of 14:58, 21 June 2007
Line 24:		Line 24:
	== Technical Aspects ==		== Technical Aspects ==

	The problem comes forth out of the fact that BIS changed the Rifle class from Rifle: Mgun to Rifle: Riflecore		The problem comes forth out of the fact that BIS changed the Rifle class from Rifle: Mgun to Rifle: Riflecore (and more of those changes)
	You can resolve the matter in ~~your own~~ addons by searching for: class Rifle: Mgun {};		You can resolve the matter in addons by searching for: class Rifle: Mgun {};
	in the Addon config.cpp and replace it with: class Rifle;		in the Addon config.cpp and replace it with: class Rifle;
			The new ArmA inheritance system allows to simply supply the classname and a ; at the end to inherit classes from other addons
	The new ArmA inheritance system allows ~~for~~ simply supply the classname and a ; at the end to inherit classes from other addons		(You should actually use this new method for all your class inheritances!)

Sickboy: /* Technical Aspects */

2007-06-21T12:23:56Z

Technical Aspects

← Older revision		Revision as of 14:23, 21 June 2007
Line 24:		Line 24:
	== Technical Aspects ==		== Technical Aspects ==

			The problem comes forth out of the fact that BIS changed the Rifle class from Rifle: Mgun to Rifle: Riflecore
	You can resolve the matter in your own addons by searching for: class Rifle: Mgun {};		You can resolve the matter in your own addons by searching for: class Rifle: Mgun {};
	in the Addon config.cpp and replace it with: class Rifle;		in the Addon config.cpp and replace it with: class Rifle;

	The new ArmA inheritance system allows for simply supply the classname and a ; at the end to inherit classes from other addons		The new ArmA inheritance system allows for simply supply the classname and a ; at the end to inherit classes from other addons

Missing Rifles Problem - Revision history

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "y[ _]*\|[ _]*(arma[0-9]+)[ _]*\|[ _]+" to "y|$1|"

Lou Montana: Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

R3vo: Text replacement - "haven't" to "have not"

R3vo: Text replacement - "aren't" to "are not"

Lou Montana: Text replacement - "\[\[[Cc]ategory:ArmA:[ _]?([^|]+)\]\]" to "{{GameCategory|arma1|$1}}"

Lou Montana: Add :Category:ArmA: Troubleshooting

Sickboy: /* Technical Aspects */

Sickboy: /* Technical Aspects */

Sickboy: /* Technical Aspects */

Lou Montana: Text replacement - "y[ _]\|[ _](arma[0-9]+)[ _]*\|[ _]+" to "y|$1|"

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "