Denniz
Aug 10, 2008, 04:17 PM
Changes for BTS Patch 3.17
For now we are not going to accept any of the new BTS 3.17 map scripts. "No Espionage" option must not be checked.
Illegal
The following must not be checked:
No City Flipping From Culture
No Technology Trading
Always Peace
Permanent War or Peace
New Random Seed on Reload
Advanced Start
No Technology Brokering
Unrestricted Leaders
No Espionage
Changes to the Crash Recovery Policy
There where two updates to the posted policy (http://hof.civfanatics.net/civ4/rules.php?show=disallowed). One reflects the reality that we have not been making exceptions for multiple crashes with a submission. The other is a new savefile requirement that we will be enforcing immediately. Please read the policy carefully.
Crash Recovery
This section outlines the only exceptions allowed to the Reloading/Replaying section the submission requirements when attempting to salvage a game following a crash to desktop (CTD).
The CivilizationIV.ini file setting: "AutoSaveInterval" must be set to 1.
Only the most recent autosave file can be used. Only one turn can be replayed.
The turn replayed must be replayed as close to the way it was the first time as possible.
We also require a save taken at the point when you have replayed up until the crash occurred.
The save file used to restart from must be supplied with the submission. Use one of the intermediate upload slots.
We also require a save taken when you have replayed up to the point where the crash had occurred.
As soon as you submit your game to the HOF website and have the submission #, send an email to hof.civfanatics@gmail.com with a message detailing what turns or game dates you crashed on. Otherwise, we won't know you crashed and will just assume the replaying is outside HOF rules and act accordingly.
Note: We will not accept more then one crash exception for any game, no matter the cause of the crash. The policy is intended as an aid for the occasional crash. It is not a guarantee of acceptance. Submissions will be evaluated on a case by case basis. We will work with you where possible to help stabilize your system. The policy is not intended as a crutch for someone attempting to play a huge map when their system can't support it. You should work within the limitations of your system.
For now we are not going to accept any of the new BTS 3.17 map scripts. "No Espionage" option must not be checked.
Illegal
The following must not be checked:
No City Flipping From Culture
No Technology Trading
Always Peace
Permanent War or Peace
New Random Seed on Reload
Advanced Start
No Technology Brokering
Unrestricted Leaders
No Espionage
Changes to the Crash Recovery Policy
There where two updates to the posted policy (http://hof.civfanatics.net/civ4/rules.php?show=disallowed). One reflects the reality that we have not been making exceptions for multiple crashes with a submission. The other is a new savefile requirement that we will be enforcing immediately. Please read the policy carefully.
Crash Recovery
This section outlines the only exceptions allowed to the Reloading/Replaying section the submission requirements when attempting to salvage a game following a crash to desktop (CTD).
The CivilizationIV.ini file setting: "AutoSaveInterval" must be set to 1.
Only the most recent autosave file can be used. Only one turn can be replayed.
The turn replayed must be replayed as close to the way it was the first time as possible.
We also require a save taken at the point when you have replayed up until the crash occurred.
The save file used to restart from must be supplied with the submission. Use one of the intermediate upload slots.
We also require a save taken when you have replayed up to the point where the crash had occurred.
As soon as you submit your game to the HOF website and have the submission #, send an email to hof.civfanatics@gmail.com with a message detailing what turns or game dates you crashed on. Otherwise, we won't know you crashed and will just assume the replaying is outside HOF rules and act accordingly.
Note: We will not accept more then one crash exception for any game, no matter the cause of the crash. The policy is intended as an aid for the occasional crash. It is not a guarantee of acceptance. Submissions will be evaluated on a case by case basis. We will work with you where possible to help stabilize your system. The policy is not intended as a crutch for someone attempting to play a huge map when their system can't support it. You should work within the limitations of your system.