I noticed some people have had issues figuring out whats wrong with their code. Theirs an easy way to enable debugging in civ4 with error reporting.
In your civ4 ini file, your going to want to set these options:
HidePythonExceptions = 0
LoggingEnabled = 1
OverwriteLogs = 1
RandLog = 1
MessageLog = 1
and of course this one comes in handy:
CheatCode = chipotle
What all the above will do is the following:
#1. You get python error popups when your code doesnt run
#2. you can look in My Documents\My Games\Sid Meyer's Civilizations 4\Logs
and there will be a PythonErr.txt, it contains the actual parser errors for your python code. If you dont want to actually test it in a python envoirnment, this is the next best thing for all you guys (plus it makes it handy for testing against the civ4 api, *AND* I have begun mapping out the methods the didnt want to give us in the api documentation)
Just thought id share.
In your civ4 ini file, your going to want to set these options:
HidePythonExceptions = 0
LoggingEnabled = 1
OverwriteLogs = 1
RandLog = 1
MessageLog = 1
and of course this one comes in handy:
CheatCode = chipotle
What all the above will do is the following:
#1. You get python error popups when your code doesnt run
#2. you can look in My Documents\My Games\Sid Meyer's Civilizations 4\Logs
and there will be a PythonErr.txt, it contains the actual parser errors for your python code. If you dont want to actually test it in a python envoirnment, this is the next best thing for all you guys (plus it makes it handy for testing against the civ4 api, *AND* I have begun mapping out the methods the didnt want to give us in the api documentation)
Just thought id share.
