What does Database.log report for errors? Without knowing what sort of errors you are getting it is nigh on to impossible to respond meaningfully. You might have incorrect SQL (or XML) syntax. Missing commas or semi-colons where necessary or just fundamental code mistakes stemming from not have a good enough grasp on how database coding works, and what the various database-tables used in the game require and accept. These kinds of mistakes usually result for SQL files with messages like So look through database log for message saying "near" something there is a syntax error. "Near" in database.log lingo means previous to but that does not mean directly before an indicated character symbol. Sometimes the indicated error can be several lines before the indicated character. Database.log reports the "nearest" thing it can understand before the syntax error. You might have incorrect ModBuddy / Modino file procedures You might simply have typo mismatches such as calling something UNIT_CHEESEBURGLER in one place and UNIT_CHEESEBURLAR elsewhere. This will usually result in Invalid Reference messages in Database.log You might have tried to add something to the game which it already has, such as a unit called UNIT_SETTLER. This sort of thing will always show up in Database.log as a Unique Constraint error message. These are common types of errors that have probably come up with pointers to the needed solution earlier in this thread.