PMC websites shut down November 13th 2025 unless web hosting fees are paid. See up to date status from PMC Website Hosting and Domain Registration Fee Status forum topic. Please Support PMC to help keep these websites online.

Enjoyed or found this pages content useful, please Support PMC to help me keep this web page online beyond November 13th 2025 when web hosting fees are due.

PMC Editing Wiki

User Tools

Site Tools

Trace:
arma:config:common_errors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
arma:config:common_errors [2009/04/26 15:40] – Header levels now H1->H2 killswitcharma:config:common_errors [2024/08/01 07:37] (current) – links added. snakeman
Line 1: Line 1:
-====== Common Errors ======+====== ArmA 1 Common Errors ======
  
-ArmA common errors in configs which you should and need to avoid at all cost.+[[https://www.pmctactical.org/forum/viewforum.php?f=42|ArmA 1 Forum]], [[:arma|ArmA 1 Home]], [[arma:config|ArmA 1 Config]], [[arma:tools|ArmA 1 Tools]], [[arma:file_formats|ArmA 1 File Formats]], [[arma:missions|ArmA 1 Missions]], [[arma:modeling|ArmA 1 3D Modeling]], [[arma:terrain|ArmA 1 Terrain]], [[arma:texturing|ArmA 1 Texturing]], [[arma:scripting|ArmA 1 Scripting]]
  
-===== Changing the inheritance of existing classes =====+**ArmA 1** aka Armed Assault (ArmA)
  
-For example on many many addons (even in BIS material) you'll see this [[arma:arma.rpt|arma.rpt]] error:+ArmA 1 common errors in configs which you should and need to avoid at all cost. 
 + 
 +===== Changing The Inheritance Of Existing Classes ===== 
 + 
 +For example on many many addons (even in bis material) you'll see this [[arma:arma.rpt|arma.rpt]] error:
 <code> <code>
 Updating base class ->MGunCore, by ca\weapons\config.bin/cfgWeapons/MGun/ Updating base class ->MGunCore, by ca\weapons\config.bin/cfgWeapons/MGun/
 </code> </code>
 This happens because an addon changes the inheritance of a class that has already been defined. In the example above, This happens because an addon changes the inheritance of a class that has already been defined. In the example above,
-BIS themselves does this in the ''Addons\weapons.pbo'' addon, where the basic class ''MGun'' is altered from+bis themselves does this in the ''Addons\weapons.pbo'' addon, where the basic class ''MGun'' is altered from
 having no parent class to having the class ''MGunCore'' as the parent. having no parent class to having the class ''MGunCore'' as the parent.
  
Line 24: Line 28:
  
  
-===== Altering existing classes ===== +===== Altering Existing Classes ===== 
-Sometimes you see addons that not only alters the inheritance of existing BIS classes, but then proceeds to make changes to the classes themselves.+Sometimes you see addons that not only alters the inheritance of existing bis classes, but then proceeds to make changes to the classes themselves.
 An example of this can be seen below: An example of this can be seen below:
  
Line 36: Line 40:
 }; };
 </code> </code>
-That's just bad form. What you should do instead is create your own machine gun class and let it inherit from the existing BIS class.+That's just bad form. What you should do instead is create your own machine gun class and let it inherit from the existing bis class.
  
 Good config: Good config:
Line 47: Line 51:
 </code> </code>
  
-===== Other common errors =====+===== Other Common Errors =====
 <code> <code>
 Updating base class ->Default, by ca\anims\characters\config.bin/CfgMovesBasic/DefaultDie/ Updating base class ->Default, by ca\anims\characters\config.bin/CfgMovesBasic/DefaultDie/
Line 61: Line 65:
 </code> </code>
 All can be avoided by not touching these base classes, just inheriting from them into your own new classes. All can be avoided by not touching these base classes, just inheriting from them into your own new classes.
 +
arma/config/common_errors.1240760413.txt.gz · Last modified: 2009/04/26 15:40 (external edit)