Tweet
(..)
Our goal is make an clone of the original game Sid Meier's Alpha Centauri, and its expansion, Sid Meier's Alien Crossfire without changing or adding any gameplay elements. Our second goal is to correct the most obvious bugs in the original game and the expansion like social engineering rollover bugs.
(..)
Our goal is make an clone of the original game Sid Meier's Alpha Centauri, and its expansion, Sid Meier's Alien Crossfire without changing or adding any gameplay elements. Our second goal is to correct the most obvious bugs in the original game and the expansion like social engineering rollover bugs.
(..)
It is makes no sense from programmatic viewpoint to first program bugs and lesser level mechanics (I expect there will be some) in, overriding the base code, and then attempting to fix the bugs.
Also, there has been a very popular idea supported by this statement from Firaxis Civ4 World Builder Manual
MANAGING THE SCENARIO
If you have never managed a project before one of the first things you will notice is that interest will rise and fall like a number of civilizations in history. You need to capitalise on the rises in interest and try to minimise the falls in interest. Aim to have the bulk of the heavy work done during rises in interest. Have someone do all the XML for the tech tree, or someone to create the map and city placements. Hopefully you will have interested a python scripter to do scripts during these highs. When interest begins to fall is your big moment. You need to consolidate what has been done during the highs and compile them into something that can be played. The easiest way to minimise (and hopefully avoid) a low in interest in your scenario is to have something that can be played. If people are playing your scenario (even if it’s only ¼ finished) then interest will be generated again. Then can you look to implement the next set of changes/features. By riding and manipulating the interest of people you can fulfil your original goal of creating a fun scenario. Sure, it does take time to create a good, fun, playable scenario. But in the end there is only ONE person who is required to maintain a high interest throughout the entire scenario’s lifecycle: YOU!
Good luck and good designing.
If you have never managed a project before one of the first things you will notice is that interest will rise and fall like a number of civilizations in history. You need to capitalise on the rises in interest and try to minimise the falls in interest. Aim to have the bulk of the heavy work done during rises in interest. Have someone do all the XML for the tech tree, or someone to create the map and city placements. Hopefully you will have interested a python scripter to do scripts during these highs. When interest begins to fall is your big moment. You need to consolidate what has been done during the highs and compile them into something that can be played. The easiest way to minimise (and hopefully avoid) a low in interest in your scenario is to have something that can be played. If people are playing your scenario (even if it’s only ¼ finished) then interest will be generated again. Then can you look to implement the next set of changes/features. By riding and manipulating the interest of people you can fulfil your original goal of creating a fun scenario. Sure, it does take time to create a good, fun, playable scenario. But in the end there is only ONE person who is required to maintain a high interest throughout the entire scenario’s lifecycle: YOU!
Good luck and good designing.
Therefore I am posting this poll and asking the comunity to decide:
1) "Yes to goal issue, yes to update issue" - means you agree that both the Goal paragraph in Mission Statement must be changed to better represent reality and the mod must done step-by-step and playable all the time (as per paragraph above)
2) "Yes to goal issue, no to update issue" - means you agree that the Goal paragraph in Mission Statement must be changed to better represent reality but the continuability of mod shouldn't be ensured the proposed way (you are welcome to post your own proposal)
3) "No to goal issue, yes to update issue" - basically vice versa of 2nd option, also you are welcome to post a proposal of Goal if you think it should be changed in some other way than proposed.
4) "No to both" - again, you're welcome to express any proposal on any of them.
5) "XenoBanana" - if you just wondered here and dont know what the guys here are all about, this is the option for you.
THIS THREAD IS NOT FOR DISCUSSIONS, IF ANY DISCUSSION IS NEEDED, YOU ARE WELCOME TO MAKE A NEW THREAD WHERE TO DISCUSS. IF THIS RULE IS BROKEN, I WILL ASK ILLUMINATUS TO MOVE THE POSTS TO NEW THREAD.
And one more - it is recommended to post about which option you voted and the reason/comment you have on it.
Thank you for voting,
bT