[C4:AC] Brainstorming for the Design Document – The Question Thread
While someone has already pointed out that our design document is essentially SMAC as we know it, as we’re going to have to compromise to some extent. Lets try and decide now what makes the cut and what will be worth our effort.
Reading through the threads, two posts that have got me considering the issue have been lists of questions (or implied questions) by Darsnan and Illu. Here they are. I’ve taken the liberty of editing them.
Not short, but then this project was never going to be for the tl;dr of the internet. In this thread lets try and post as many questions as possible about what goes into C4:AC or our methods. At the end I’ll gather them all up, sort them into catagories and we can answer them. By comparing answers and debating points I’m hoping we’ll find the design document.
This is strictly a no answer zone. We shall seek enlightenment and resolution elsewhere after a period of time. Your posts may only contain full stops (periods) in a paragraph finishing with a question mark.
Ok, go.
While someone has already pointed out that our design document is essentially SMAC as we know it, as we’re going to have to compromise to some extent. Lets try and decide now what makes the cut and what will be worth our effort.
Reading through the threads, two posts that have got me considering the issue have been lists of questions (or implied questions) by Darsnan and Illu. Here they are. I’ve taken the liberty of editing them.
2. Decide if we are willing to run parallel to any possible Firaxis efforts for SMAC2
3. Decide if we want to fix bugs already existing in SMAC.
5. Should we develop an accompanying manual, or just ensure everything is covered by the Datalinks?
7. Mod being built for Windows platform only?
1. 3-D graphics for leaders? If so, how construct, and using what graphics generator?
2. Document all interactive keystrokes via Datalinks, or in seperate notepad file?
3. Document all necessary functions in SMAC(X) to see what matches up against existing C4 functions.
4. Document the process of the mod so that others can follow the same path for their own mods.
5. What to do with support for other languages?
6. How to generate 3D SMACX units?
7. Document how the AI thinks: should be somewhat apparent via the Python code.
8. Format of new subroutines: follow Firaxis approach, or invent our own?
9. desired option for mod: to have all relevent files imprinted onto a game.
11. Document all sounds in SMAC(X) to include detailing where they occur.
12. Identify all files in SMAC(X) and detail what they stand for.
13. AI negotiation: need to improve for SMACX, especially base trading.
14. Firaxis patches for C4: how impact ongoing mod?
15. Useless" subroutines: comment out or delete?
16. What to do about culture/religion? (Senethro: Good Q. about Civ4 systems in general)
17. Fixed border distance as in original SMAC or create options that allow modders to easily modify it?
1. Do we develop an accompanying manual, or just ensure everything is covered by the Datalinks?
2. For our C++/ Python subroutines, what format should we follow for consistency from subroutine to subroutine?
3. 3-D graphics for leaders? If so, how construct, and using what graphics generator?
4. Document all interactive keystrokes via Datalinks, or in seperate notepad file?
5. document all necessary functions in SMAC(X) to see what matches up against existing C4 functions.
6. document the process of the mod so that others can follow the same path for their own mods.
7. other languages (French, German, Chinese) support question....
8. How are we going to generate 3D SMACX units?
10. Documenting how the AI thinks: should be somewhat apparent via the Python code.
11. Format of new subroutines: follow Firaxis approach, or invent our own?
16. desired option for mod: to have all relevent files imprinted onto a game.
18. document all sounds in SMAC(X) to include detailing where they occur.
21. AI negotiation: need to improve for SMACX.
22. Mod is being built for Windows platform only? (Senethro: Qs like this one here are VERY pertinent)
25. cheating: how will it be detected, how countered?
26. Firaxis patches for C4: how impact ongoing mod?
27. "Useless" subroutines: comment out or delete?
3. Decide if we want to fix bugs already existing in SMAC.
5. Should we develop an accompanying manual, or just ensure everything is covered by the Datalinks?
7. Mod being built for Windows platform only?
1. 3-D graphics for leaders? If so, how construct, and using what graphics generator?
2. Document all interactive keystrokes via Datalinks, or in seperate notepad file?
3. Document all necessary functions in SMAC(X) to see what matches up against existing C4 functions.
4. Document the process of the mod so that others can follow the same path for their own mods.
5. What to do with support for other languages?
6. How to generate 3D SMACX units?
7. Document how the AI thinks: should be somewhat apparent via the Python code.
8. Format of new subroutines: follow Firaxis approach, or invent our own?
9. desired option for mod: to have all relevent files imprinted onto a game.
11. Document all sounds in SMAC(X) to include detailing where they occur.
12. Identify all files in SMAC(X) and detail what they stand for.
13. AI negotiation: need to improve for SMACX, especially base trading.
14. Firaxis patches for C4: how impact ongoing mod?
15. Useless" subroutines: comment out or delete?
16. What to do about culture/religion? (Senethro: Good Q. about Civ4 systems in general)
17. Fixed border distance as in original SMAC or create options that allow modders to easily modify it?
1. Do we develop an accompanying manual, or just ensure everything is covered by the Datalinks?
2. For our C++/ Python subroutines, what format should we follow for consistency from subroutine to subroutine?
3. 3-D graphics for leaders? If so, how construct, and using what graphics generator?
4. Document all interactive keystrokes via Datalinks, or in seperate notepad file?
5. document all necessary functions in SMAC(X) to see what matches up against existing C4 functions.
6. document the process of the mod so that others can follow the same path for their own mods.
7. other languages (French, German, Chinese) support question....
8. How are we going to generate 3D SMACX units?
10. Documenting how the AI thinks: should be somewhat apparent via the Python code.
11. Format of new subroutines: follow Firaxis approach, or invent our own?
16. desired option for mod: to have all relevent files imprinted onto a game.
18. document all sounds in SMAC(X) to include detailing where they occur.
21. AI negotiation: need to improve for SMACX.
22. Mod is being built for Windows platform only? (Senethro: Qs like this one here are VERY pertinent)
25. cheating: how will it be detected, how countered?
26. Firaxis patches for C4: how impact ongoing mod?
27. "Useless" subroutines: comment out or delete?
This is strictly a no answer zone. We shall seek enlightenment and resolution elsewhere after a period of time. Your posts may only contain full stops (periods) in a paragraph finishing with a question mark.
Ok, go.
Comment