Some notes for you before playing The Journey to Epsilon Pegasi minicampaign:

GENERAL NOTES

This is the second release, some changes to the first release include:

-More playgame possibilities are accounted for; missions are harder to break.
-Fixing game balance issues. Some missions are harder, some have become easier since the first release. In some missions, players will receive "mission-coded" privileges on easier difficulties, and suffer some penalties on harder difficulty settings. For example, a Shivan vessel in mission 7 will take longer to recharge its beams on Easy, but will immediately fire on Hard.
-Additional mission tweaks that made the missions better overall, not  affecting difficulty.
-Fixing typos, rewriting some dialogs and briefings.
-Minor consistency fixes.

The first release was tested for FreeSpace Open 3.6. The second release is optimized to work on v3.6.9. If a mission crashes for an unknown reason, check your FSO build first. Missions are not expected to work properly in a version older than v3.6.9. Some may not work at all with v3.6.

The campaign was tested and optimized for Medium difficulty. If a mission is seemingly impossible on Hard or Insane, just lower the difficulty level to Medium, and it will be much better. A mission on an easier difficulty setting might also become hilariously simple, and even impossible to lose.

The missions are tested both with and without MediaVPs. Using or not using MediaVPs is not expected to cause issues.

All the missions are replayable in the Mission Simulator, with additional craft and weaponry that are unavailable while playing in Campaign Mode.

INSTALLATION

You are expected to have FreeSpace Open v3.6.9. (or newer) to be able to properly run the campaign. If you do not know what FreeSpace Open is, use Google! The campaign will not work at all on Retail FreeSpace.

There are two ways to install a home-made campaign for FreeSpace Open. The first is the classical way:
	1. Extract the contents of the archive.
	2. Mission and campaign files (*.fs2 and *.fc2) go to FreeSpace/data/missions; the custom GTD Orion nameplate goes to FreeSpace/data/maps.
If you do this, the campaign is supposed to appear on the campaign list in the Campaign Room. If not, check if you have extracted the *.fc2 files, too. Without an *.fc2 file, no campaign is listed on the campaign list.

The second is the new way. This method was invented for those campaigns that use a large number of new mods.
	1. Create a folder in your root FreeSpace folder, named something like "JtEP."
	2. Create a "data" folder inside your JtEP folder.
	3. Create a "maps" and "missions" folder inside your "JtEP/data"
	4. Mission and campaign files (*.fs2 and *.fc2) go to FreeSpace/JtEP/data/missions; the custom GTD Orion nameplate goes to FreeSpace/JtEP/data/maps.

CONTACT

Please submit feedback and report problems in the release thread at Hard Light Productions forums (use Google to find it!), or directly to the author (email address below).

TopAce, FREDder and Project Leader for the Journey to Epsilon Pegasi project,
ahartai@yahoo.com