Rules.ini: Difference between revisions
Line 48: | Line 48: | ||
# need to modify the rules.ini if there are any error reports during reading it by module configparser | # need to modify the rules.ini if there are any error reports during reading it by module configparser | ||
rules_dir=r"C:\Users\August\Documents\rulesmo_mod.ini" | rules_dir=r"C:\Users\August\Documents\rulesmo_mod.ini" | ||
# rules_dir=r"/storage/emulated/0/1/ | # rules_dir=r"/storage/emulated/0/1/rulesmo_mod.ini" | ||
# set the output file directory | # set the output file directory | ||
ofdir=r"C:\Users\August\Documents\UnitCodes.txt" | ofdir=r"C:\Users\August\Documents\UnitCodes.txt" |
Revision as of 05:23, 14 February 2024
The rules.ini (naming variations for expansions) is the core file of C&C modding. As indicated by the name, it contains the "rules" of the game – the properties of every object, weapon, warhead, etc. in the game. For any C&C game from Red Alert to Yuri's Revenge, this is the main modification file. For Generals and everything else based on the SAGE engine, the INI-system is more complex and wide-spread.
Disregarding the side functions of the other various INI files (like ai.ini or art.ini), there is no way to make any changes to the game other than what the rules.ini allows for1. Not everything in the game is customizable. Features that cannot be modified are called "hardcoded" features.
File Locations
Game | Location | Notes |
---|---|---|
Red Alert | redalert.mix → local.mix | |
Tiberian Sun | tibsun.mix → local.mix | The patches add a new rules.ini to patch.mix |
Firestorm | expand01.mix | rules-equivalent is called firestrm.ini, the mix also contains a new rules.ini for regular TS. |
Red Alert 2 | ra2.mix → local.mix | |
Yuri's Revenge | expandmd01.mix | Called rulesmd.ini, for mission disk. |
Mental Omega | expandmo99.mix | Called rulesmo.ini, for Mental Omega. |
Script to Read UnitsIdCode in Rules.ini
Python 3
This script will read the rules.ini and list the UnitType, SequenceNum, UnitIdCode, UnitUIName, UnitInternalName and Armor, and store these informations into a txt file.
To get the CSF.ini that required in this script, please go to page CSF File Format.
- ReadRulesCode.py
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 |
# set the directory of rules.ini here # need to modify the rules.ini if there are any error reports during reading it by module configparser rules_dir=r"C:\Users\August\Documents\rulesmo_mod.ini" # rules_dir=r"/storage/emulated/0/1/rulesmo_mod.ini" # set the output file directory ofdir=r"C:\Users\August\Documents\UnitCodes.txt" # ofdir=r"/storage/emulated/0/1/UnitCodes.txt" # set the directory of CSF.ini that decoded by ReadCsf.py csf_ini_dir=r"C:\Users\August\Documents\CSF.ini" # csf_ini_dir=r"/storage/emulated/0/1/CSF.ini" |
Footnotes
1 ↑ An exception to this would be pd's RockPatch.
See Also
- Art.ini
- Sound.ini
- CSF
- Hardcoded features
- Rules(md).ini Sections
- Rules(md).ini Flags
- Lists of Applicable INI Flags