LeeS
Imperator
You have a structure like:
Lua will evaluate for A, and if A is not true, it will then evaluate for B, and if B is not true, it will execute the "else" clause. The portion in red will never be executed and is I think breaking the if xxx then yyyyy elseif rrrrr then ssssss else zzzzz end structure of a conditional "code-block ".
-----------------------------------------------------------------------------
Look more closely at your code and I think you will find you have an extra 'end' in the code at line 65. It does not match-up to the "for" on line 61 nor to the "if" on line 62. Code-breakages like this cause the lua 'parser' to see line number 66 as the terminator for the "function" on line 54, which makes it impossible really for the system to give a 'correct' error report. I have had similar types of errors reported when I forgot the second '=' in '==' but never got an error directly related to the actual problem.
-------------------------------------------------------------------------------
Don't be suprised if Events.EndCombatSim.Add(YouWillFollowMeToHell) does not work correctly. My understanding is Events.EndCombatSim will only run if the human player can observe the action of the 'Sim'.
--------------------------------------------------------------------------------
Not Sure what other people are currently using to ferret-out code errors.
I look 1st at the code in ModBuddy for errors in syntax like missing </Row> closers in XML. Modbuddy is nearly useless for finding SQL or LUA errors, however. In the images you attached to your post, whatever program you are using to view the code is showing a little "code-block" symbol just to the right of the line-numbers. That vertical line + symbol system is showing you everything that would be successfully assigned to a function within lua. ModBuddy does the same, so in Modbuddy I quickly check for that in my lua files.
I always check the lua.log and the Database.log 1st for any errors in my code. Remember that lua errors show only in the lua.log.
LiveTuner (a part of the SDK that comes with ModBuddy) will also show you the contents of the lua.log in real-time as you run the game and test a mod.
Alternatively you can ALT-TAB from the game to desktop view, open your browser, and use you browser to look at the contents of the lua.log, but this is a poor second to LiveTuner, since it is a lot of fiddling around to get to something LiveTuner will do by default. Also, when using the 'open the lua log in Notepad' method, you only get the contents of the lua.log at the instant you open the log to look at it, and you really need to close the file again before trying to proceed with anything else in-game.
Code:
if A then
SomethingA
elseif B then
SomethingB
else
SomethingC
[color="red"]elseif D then
SomethingD
end[/color]-----------------------------------------------------------------------------
Code:
[1292078.468] Syntax Error: C:\Users\Lee\Documents\My Games\Sid Meier's Civilization 5\MODS\Kingdom of Two Sicilies (v 2)\Mod\TwoSicilies_Decisions.lua:67: ')' expected (to close '(' at line 53) near 'save'-------------------------------------------------------------------------------
Don't be suprised if Events.EndCombatSim.Add(YouWillFollowMeToHell) does not work correctly. My understanding is Events.EndCombatSim will only run if the human player can observe the action of the 'Sim'.
--------------------------------------------------------------------------------
Not Sure what other people are currently using to ferret-out code errors.
I look 1st at the code in ModBuddy for errors in syntax like missing </Row> closers in XML. Modbuddy is nearly useless for finding SQL or LUA errors, however. In the images you attached to your post, whatever program you are using to view the code is showing a little "code-block" symbol just to the right of the line-numbers. That vertical line + symbol system is showing you everything that would be successfully assigned to a function within lua. ModBuddy does the same, so in Modbuddy I quickly check for that in my lua files.
I always check the lua.log and the Database.log 1st for any errors in my code. Remember that lua errors show only in the lua.log.
LiveTuner (a part of the SDK that comes with ModBuddy) will also show you the contents of the lua.log in real-time as you run the game and test a mod.
Alternatively you can ALT-TAB from the game to desktop view, open your browser, and use you browser to look at the contents of the lua.log, but this is a poor second to LiveTuner, since it is a lot of fiddling around to get to something LiveTuner will do by default. Also, when using the 'open the lua log in Notepad' method, you only get the contents of the lua.log at the instant you open the log to look at it, and you really need to close the file again before trying to proceed with anything else in-game.
, hmm lets see if we can make that fit Apollo 
fortunate to have LeeS he's one of the best for advice/guidance here a civfanatics imo nice job 
(it's a classical age unit with 17 cs, so at half hp is +4 = 21, more than a longswordsman)
(standard speed) --> 2 
---> 3*2 = +6 
the function that enables the science-boosting policy works. And now I understand the complains: I knew that HappinessToScience meant that added the extrahappiness as science (e.g. 100% * +5 Happiness = +5 Science) but instead it adds x% science from global generated science when excess happiness > 0.
the function that adds to coastal cities +1 culture dummy buildings according to 10% culture of the capital doesn't work;
