Tekamthi
Emperor
- Joined
- Aug 12, 2016
- Messages
- 1,938
Re: the text issue above, the SQL must've failed on some command, aborting the text inserts that come at the end of the file (and maybe some other database things) -- rather than a mod file being deleted entirely. Recent versions of VP have seen some name changes to default table, field, variable names etc. in database, resulting in many mods not working for trivial reasons.
To be helpful to CAYM and other users of this mod, what just about anyone here can do is open the SQL in text editor (attached as buildings.txt a few posts above), load the mod in-game (optionally firetuner too, for creating test scenarios), and start checking block by block, in the order they appear in the file, for the specific SQL command that fails -- can be as simple as checking that each block is reflected in civilopedia: pick a block of code in the middle of the file, and try to find it reflected in game. Some don't show in civilopedia but most do. If its there, move down to the next block; if it's not, move up to the previous block, til you find the first sql change that isn't showing in-game. Clearly the top of the file is working, but its aborting somewhere in the middle. Its a relatively long sql file, and unless CAYM has some intuition on this already, this is probably what he'll have to do anyway to fix this.
I haven't played this mod yet, otherwise I might do this myself, but its really not that difficult to narrow down SQL errors, even with minimal SQL literacy
To be helpful to CAYM and other users of this mod, what just about anyone here can do is open the SQL in text editor (attached as buildings.txt a few posts above), load the mod in-game (optionally firetuner too, for creating test scenarios), and start checking block by block, in the order they appear in the file, for the specific SQL command that fails -- can be as simple as checking that each block is reflected in civilopedia: pick a block of code in the middle of the file, and try to find it reflected in game. Some don't show in civilopedia but most do. If its there, move down to the next block; if it's not, move up to the previous block, til you find the first sql change that isn't showing in-game. Clearly the top of the file is working, but its aborting somewhere in the middle. Its a relatively long sql file, and unless CAYM has some intuition on this already, this is probably what he'll have to do anyway to fix this.
I haven't played this mod yet, otherwise I might do this myself, but its really not that difficult to narrow down SQL errors, even with minimal SQL literacy