New to Civ modding, where should I start?
- Thread starter V3N0M
- Start date
Asaf
Sleep Deprived
- Joined
- Mar 22, 2010
- Messages
- 1,326
That depends on your current skills (programming, art etc.)
It seems to be a consensus that this tutorial is a good place to start.
Basically there are 4 main components which you can mod in Civ4:
Art (which I know hardly nothing about) - everything from textures (images) to 3D meshes to animations (e.g. for units and leader heads). This is less of a gameplay modding component, I guess.
XML which is the file format in which most the data the game uses is held. This is a text format and you can easily edit it in any text editor (I recommend notepad++). By modifying these files you can change basically everything which is not behavioral in the game - which units are there, what their properties are (strength, cost etc.), which buildings are there, which civilizations/resources/terrain/improvements/ game speeds etc. etc.
The XML and art should be enough to make any mod which doesn't change the behavior and interface of the game.
In addition, you have two components which require some programming knowledge, but this can be learned:
Python is a scripting language, which means it is parsed at runtime - while the game is running. These scripts control many things - starting with the way the game looks (screens, interfaces) up until actually coding some of the logic of the game (e.g. Random events and their effects). See this tutorial for starting Python modding.
The DLL is the core of the game's logic, and Firaxis was kind enough to release its source code (you might sometimes see people refer to it as SDK). DLL stands for Dynamically Loaded Library, and is a file which is created by taking a lot of C++ source code files, and compiling them to machine language. If you want to change the basic way the game behaves, or add new features to the core logic of the game (e.g. how combat is done, victory conditions etc.) - this is the place.
If you don't already know C++ this can be a little more complicated than the previous components, but you can definitely learn this. You can check out my tutorial on compiling the DLL, and it has some links inside for actual C++ programming and Civ4 programming specifically.
A beginner's project?
Some people say you should start small - tweak a unit here, add a building there and see how it goes.
I say - if you want to start modding you probably already have ideas of your own, and you're not in it to "become a modder". Start with them, even if they are a bit complicated, and work your way through them using the help of other modders. You'll enjoy more and have higher motivation to continue. Ask questions, get stuck, read useful tutorials, read tutorials which have nothing to do with your problems (but you'll only find out after you've read them), experiment, and most importantly - have fun.
EDIT: Wow, I wrote a manifest...
It seems to be a consensus that this tutorial is a good place to start.
Basically there are 4 main components which you can mod in Civ4:
Art (which I know hardly nothing about) - everything from textures (images) to 3D meshes to animations (e.g. for units and leader heads). This is less of a gameplay modding component, I guess.
XML which is the file format in which most the data the game uses is held. This is a text format and you can easily edit it in any text editor (I recommend notepad++). By modifying these files you can change basically everything which is not behavioral in the game - which units are there, what their properties are (strength, cost etc.), which buildings are there, which civilizations/resources/terrain/improvements/ game speeds etc. etc.
The XML and art should be enough to make any mod which doesn't change the behavior and interface of the game.
In addition, you have two components which require some programming knowledge, but this can be learned:
Python is a scripting language, which means it is parsed at runtime - while the game is running. These scripts control many things - starting with the way the game looks (screens, interfaces) up until actually coding some of the logic of the game (e.g. Random events and their effects). See this tutorial for starting Python modding.
The DLL is the core of the game's logic, and Firaxis was kind enough to release its source code (you might sometimes see people refer to it as SDK). DLL stands for Dynamically Loaded Library, and is a file which is created by taking a lot of C++ source code files, and compiling them to machine language. If you want to change the basic way the game behaves, or add new features to the core logic of the game (e.g. how combat is done, victory conditions etc.) - this is the place.
If you don't already know C++ this can be a little more complicated than the previous components, but you can definitely learn this. You can check out my tutorial on compiling the DLL, and it has some links inside for actual C++ programming and Civ4 programming specifically.
A beginner's project?
Some people say you should start small - tweak a unit here, add a building there and see how it goes.
I say - if you want to start modding you probably already have ideas of your own, and you're not in it to "become a modder". Start with them, even if they are a bit complicated, and work your way through them using the help of other modders. You'll enjoy more and have higher motivation to continue. Ask questions, get stuck, read useful tutorials, read tutorials which have nothing to do with your problems (but you'll only find out after you've read them), experiment, and most importantly - have fun.
EDIT: Wow, I wrote a manifest...
I'd say toying around with the built-in World Builder would be a good start. The next logical step is to open up the World Builder Save file in a text editor and add to the previously saved scenario. Once you have the map and players/teams in order, you could try to add content to your scenario - making it a "mod". Like adding a new Civ or Leader, or a Unit or Building. You could try to tweak the existing ones first, though, making them more fitting for your actual scenario. This is basically XML modding - not that different from editing the WBS (above).
Adding new stuff means including new art and possibly even audio, apart from the new XML entries, of course. This should keep you busy for some time, if you really commit to learning each new aspect of modding. Programming, on the other hand, is necessary once you want to 1. change the game interface, 2. add new rules to the game or tweak the existing ones, or 3. script what happens in your scenario. Not all mods/scenarios require coding/scripting.
Adding new stuff means including new art and possibly even audio, apart from the new XML entries, of course. This should keep you busy for some time, if you really commit to learning each new aspect of modding. Programming, on the other hand, is necessary once you want to 1. change the game interface, 2. add new rules to the game or tweak the existing ones, or 3. script what happens in your scenario. Not all mods/scenarios require coding/scripting.
I have to agree. That's where I started. I'll give you some advice: Don't go too fast. Start with units and buildings, maybe Civs and Leaders.
Asaf
Sleep Deprived
- Joined
- Mar 22, 2010
- Messages
- 1,326
Told ya
Maybe it's because my goal at modding was different - I don't like creating content. Too much of a hassle for me. I prefer adding new features for others to use. I like the challenge of changing the way the game behaves, and to do so in a way that fits nicely into the game. So for me, tweaking units or adding some content is simply not what I'm after.
And maybe I misunderstood what you meant by "gameplay mods", and their way fits you better
Whatever works for you.
Told ya
Maybe it's because my goal at modding was different - I don't like creating content. Too much of a hassle for me. I prefer adding new features for others to use. I like the challenge of changing the way the game behaves, and to do so in a way that fits nicely into the game. So for me, tweaking units or adding some content is simply not what I'm after.
And maybe I misunderstood what you meant by "gameplay mods", and their way fits you better
Whatever works for you.
No, I meant changing the way the game behaves. Thanks for linking the python tut btw. I'll check it out.
Similar threads
