---> Latest Empires data files and some instructions <---

[Pocus]

Here is the latest set of data files for Empires (and DLC):

https://1drv.ms/u/s!Au6qiLME-7qigZloZGN ... Q?e=LiW7yP
from March 25th, 2021. Valid 4 weeks. The 1.35 game patch itself will also provide the latest database once finalized, in Data\Database

How to edit files:
Avoid editing CSV files directly if possible. It's very difficult to see what has changed there, as there is no formatting. Instead, edit the relevant file(s) in the database (either in xls or xlsx format, so ensure you have compatible software).

I would advise coloring some of the cells of a line you edit in a very specific color to track your changes. This is important because the file you edit might change in a future patch, so you must be sure of what you edited. An alternative solution is to create a brand new column (wherever you want) of type COMMENT, label it as you wish ('Notes' or whatever), and add anything you feel is important to note there. You can create as many COMMENT columns as you wish; they are completely invisible to the ARCHON engine.

Do not create empty lines in the XLS files you manipulate between data. If possible, prefer appending files and avoid inserting new lines into a file, as this can break all saved games, most of the time.
Ensure you give unique identifiers, often when you create a line, you'll need to add an ID, which is the first column in many files. It must be unique, which is another reason it's better to append, to know which ID you can use. However, FACTIONS.XLS does not have identifiers, but you must provide a valid faction alias.

Be sure to check when you need to add a $ and when you should not before aliases. Copy what exists, and you should be fine.

Once you are satisfied, export the XLS(X) in .CSV format, using SEMI-COLON and not COMMA as the field delimiter.

Ensure you make incremental changes and back up your files over several levels. One of the best practices you can have is to add things in small amounts, test, and if that's working, copy these files as a backup and start another limited amount of work. If you change many things and it's not working, finding the error might be very difficult. The fewer changes you make before an error occurs, the easier it is to remember/see where the error is.

[Pocus]

Shortcuts and halting the debugger

****************************
* Shift+F11 - open script debugger
* Shift+F12 - toggle object inspector
* F - cycle through terrain display modes (normal, hide FOW effect, hide weather effect, hide both)
* Ctrl+Shift+I - rerun the AI for the current turn
* M - toggle between normal camera and top-down
* Q,E - rotate camera
* X - restore default camera rotation
* Shift+Home - toggle script profiler
* Shift+End - reset script profiler
* Ctrl+F11 - reload shaders, edit and continue supported
* Ctrl+F12 - reload scripts, edit and continue supported
* Ctrl+Home - reload textures which have changes since loading
* Ctrl+End - reload UI and string files
* PrtScn - take a screenshot (saved in My Games\AgeodEngine\SCREENS)
* Ctrl+Shift+P - start or stop recording a video (slideshow)
****************************

Halting the debugger
Use DebugBreak in the code to halt the debugger on this line
You need to be in Windowed mode, not Fullscreen
DEBUGMODE 1 should be added or edited in USER.TXT

[Pocus]

Updated to March 25th, 2021

[Pocus]

Updated on April 3rd, 2024, with DB from August 2022 (latest edits in).