The Kind you put in this column must exist in the Kinds table otherwise you'll get what is known as a foreign key constraint error. Kind - The Kind associated with this Type.Hash - Same as the kinds table but for Type.DIFFICULTY_SETTLER, DIFFICULTY_CHEIFTAIN, etc. Types for the Difficulties table are prefixed with DIFFICULTY_ e.g. Typically prefixed by the singular version of the table it's associated with. Hash - This is simply an auto-generated number associated with the Kind column so that the game's engine may more quickly access it (for all intents and purposes you can ignore this one).KIND_TRAIT, KIND_DIFFICULTY, KIND_CIVIC, etc. Typically in all caps and prefixed with KIND_. I'm going to use the Difficulties heirarchy (all tables involved in creating a difficulty setting) for the purpose of example so you're not just seeing the theory of Kinds and Types but how they exist in game. I still recommend using a convention, whether you stick with Firaxis' convention is up to you.Д«elow I'm going to review each table's columns and how they associate with each other. Note, that there is one single benefit to not using Firaxis' conventions and that is if you use some other prefix other than 'LOC_' you almost guarantee yourself to never have a conflict. For example, you want to know the tag for the warrior unit, well based on Firaxis' convention start with 'LOC_' what it is 'UNIT_' its base name 'WARRIOR_' and what you want 'NAME' so the tag for the warrior unit's name is 'LOC_UNIT_WARRIOR_NAME' which when you're looking at the data/code for the unit it seems obvious and excessive but can be helpful at certain times. This is the convention that Firaxis used quite often you can simply just know what a string is for by reading the Tag or if you don't know the tag for something you can guess it based on what it is. If you look in the LocalizedText table you'll notice that 95% of the tags in there begin with 'LOC_' and have underscores separating words. So having text in a separate table makes sense. For example, in the early stages of the game's development the unit table might not have existed yet but everyone knows certain units will exist in the game and the person responsible for the names and descriptions might want to get a head-start on them. Development - Keeping things separate yet connected allows teams to work on different parts of the game at different times.

Performance - Civilization VI runs on a database via SQLite database tables with more data in each row tend to have slower performance.EnglishName, RussianName, SpanishName, etc). Are you going to have a column for the name of a unit for each language? (e.g. Languages - There are a lot of different languages a game might be translated into.You might think that it would make sense to put each unit's name, description, etc in the unit table along with its attributes like cost, movepoints, etc. Text for units, civilizations, traits, promotions, etc, etc. In Civilization VI there is a lot of text. forgetting semi-colons after SQL statements). After I found out it started taking me less and less time and I started correcting the behaviors that caused those errors in the first place (e.g. This was happening to me a LOT before I knew about these log files. Quite commonly the symptoms of there being an error in the database.log file is that something you've attempted to change is just not even remotely in the game. These are the only two I know for certain but just knowing that the logs are there and that you can check them at least gives you a place to look when you're not sure what's going on. For instance, the database.log shows syntax and database errors and the gameeffects.log shows issues with modifiers.

The log files inside the Log Folder are a valuable set of files. With regular notepad you'll have to re-open the file, however with notepad++ it will detect the file has been changed and ask you if you'd like to reload it. Note - The reason I suggested Notepad++ in the tools section is that you might have the log file open before the error is thrown in there.

These errors populated the database.log file in the Log Folder (See Folders section) when the game was at the loading screen. The yellow lines are (roughly) each time I clicked 'Start Game' at the main menu. The screenshot below contains examples of these types of errors (highlighted in red). These are caused by typing something wrong (syntax) or not inserting a value (foreign key reference which also can be caused by inserting a reference to something before it has been inserted itself). The most common set of errors you'll run into when starting out are syntax and foreign key reference errors.

How to make a mod for civ 6