Eastside Hockey Manager
Недостаточно оценок
How to import EHM 2007 rosters into EHM:EA
От archibalduk
Eastside Hockey Manager: Early Access has an Import feature which allows you to import databases from Eastside Hockey Manager 2007. This simple guide explains how to prepare and import a database in three steps. It explains where to place the files and how to choose your import settings (such as start year - e.g. so you can play a 1974/75 database using a 1974 starting season).

I originally wrote and published this guide on www.ehmtheblueline.com
   
Наградить
В избранное
В избранном
Удалить
Introduction
Eastside Hockey Manager Early Access has a different database format compared with EHM 2007. However, EHM:EA has a database import function which makes it easy to convert and import EHM 2007 databases.

There are three simple steps to importing a database (and one optional step):

1. Use an import_config.cfg file to apply any import settings you might need.

2. Copy the database to your data/database/ folder.

3. Import the database using the Import function in EHM:EA.

4. OPTIONAL: Tidy up your imported database folder.

I originally wrote and published this guide on http://www.ehmtheblueline.com
Step #1: Customising the import settings using import_config.cfg
A database can be imported without an import_config.cfg file. In which case the game will import the data using the 2014/15 rule set and with a 2014/15 start date. If this is acceptable, then you can skip to step 2 below (i.e. “Copying your database to the Database folder”).

An example import_config.cfg file can be found in the data/database/historic 2006 folder. You can edit this file using Notepad (it is just a plain text file). Alternatively, you can create a fresh file using Notepad and saving it as import_config.cfg (do not inadvertently save it with a .txt file extension).

The two essential commands that you must use in the file are:

"START_YEAR" 2014 "DEFAULT_RULE_SET" 2014

The start year can be any year between 1970 and 2014 (i.e. 1970/71 – 2014/15).

The default rule set determines what rules and league structures will be used. This value can be either 2006 (i.e. EHM 2007 rules and structures) or 2014 (i.e. the 2014/15 rules and structures).

Optionally, it is possible to rename the league and tournament names on import (unlike EHM 2007, EHM:EA will accept renamed league names):

"CHANGE_COMP_NAME" "Old long name" "New long name" "New short name" "New abbreviation" "New regular season trophy name" "New playoff trophy name"

EXAMPLE:
"CHANGE_COMP_NAME" "Russian Superleague" "Kontinental Hockey League" "Kontinental Hockey League" "KHL" "Kontinental Cup" "Gagarin Cup" "CHANGE_COMP_NAME" "Czech Elite League" "Czech Tipsport Extraliga" "Czech Extraliga" "" "" ""

Once you have finished setting up your import_config.cfg file, you should save it to the same folder as your EHM 2007 database .dat files.

Note that once the database has been imported, the import_config.cfg file no longer has any effect on the database. If you want to adjust the settings in import_config.cfg then you will have to re-import your EHM 2007 database.
Step #2: Copy the database to your \data\database\ folder
You should copy your EHM 2007 database files into a new sub-folder within your C:\Program Files (x86)\Steam\SteamApps\common\Eastside Hockey Manager\data\database\ folder:

Step #3: Import the database using the Import function in EHM:EA
Load EHM:EA and click on “Import Database” from the main menu screen.


You will be prompted to select the EHM 2007 database to import. The start year is listed in brackets next to the name of each database. Click on OK and the game will start converting the database.

The process can take around 5 minutes. Once it is complete, you can select your imported database like usual from the “New Game” button.
Step #4: OPTIONAL: Tidy up your imported database folder
Unlike EHM 2007, the database in EHM:EA consists of a single database.db file along with the usual .cfg files. Once EHM:EA has finished importing your database, you can safely delete all of the .dat files from your database folder. This will probably save you around 35mb per database so it’s well worth doing if storage space is at a premium.