Provides automatic installation scripts for OpenRA with Tiberian Sun & Red Alert 2 + Dune 2 (Windows, Linux)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

160 lines
5.6 KiB

8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
  1. Introduction
  2. ==============
  3. This Github repository provides a bunch of scripts for installing TS/RA2 on OpenRA.
  4. The following operating systems are currently supported:
  5. - Windows 10
  6. - Windows 7
  7. - Ubuntu (16.04 LTS, 15.10, 15.04 LTS, 14.10, 14.04 LTS)
  8. - Linux Mint (17.3, 17.2 & 17.1)
  9. - Debian (8.3.0)
  10. - OpenSUSE (Tumbleweed, 42.1, 13.2)
  11. - Fedora (23, 22)
  12. - Arch Linux
  13. A lot of people are willing to play Tiberian Sun and Red Alert 2 mods in OpenRA, no matter if they're at unfinished state or not. Personally, I feel the official OpenRA wiki may be really hard to understand for novice people who just want to play these titles and show little interest in cryptic compilation processes.
  14. That's why, as not official support is not provided yet, I decided to do something about this TS/RA2 issue/dilemma: I made a bunch of scripts and instructions that should make life for an average user a bit easier and help installation of these two awesome titles (TS/RA2) on OpenRA.
  15. **NOTE:** As the development of OpenRA & Red Alert 2 continues, this script will likely become unusable some day.
  16. **NOTE 2:** As APT package manager updates have been dropped from some old Ubuntu based operating systems (such as 14.10), not all required packages to compile OpenRA may be available via internet anymore.
  17. **Installation instructions**
  18. --------------
  19. **Windows**
  20. 1) Make sure you have .NET Framework 4.5 installed on your computer
  21. (Read *WINDOWS-BEFORE-INSTALLATION.txt* for further information)
  22. 2) Double click *windows-install.bat*
  23. 3) Follow the instructions
  24. **Linux (All distributions)**
  25. 1) Open terminal window. In terminal, run:
  26. ```
  27. bash linux-install.sh
  28. ```
  29. 2) Follow the instructions
  30. **Post-installation instructions**
  31. --------------
  32. **To play Tiberian Sun**
  33. Launch the game and download the required asset files from the web when the game asks you to do so.
  34. **To play Red Alert 2**
  35. You must install language.mix, multi.mix, ra2.mix and theme.mix into
  36. \My Documents\OpenRA\Content\ra2\ (Windows)
  37. .openra/Content/ra2/ (linux)
  38. You find these files from original RA2 installation media (CD's):
  39. - theme.mix, multi.mix = RA2 CD Root folder
  40. - ra2.mix, language.mix = RA2 CD Root/INSTALL/Game1.CAB (inside that archive file)
  41. **Multiplayer**
  42. It's recommended to build OpenRA using exactly same GIT source files for multiplayer usage to minimize possible version differences/conflicts between players. Please make sure all players have exactly same git versions of their in-game mods (RA, CNC, D2K, TS, RA2). Version numbers are formatted like 'git-e0d7445' etc. and can be found in each mod description in the mod selection menu.
  43. **Uninstallation**
  44. --------------
  45. For uninstallation, please see specific instructions for your Operating System below.
  46. **Windows**
  47. Since the game has been compiled from source and no additional setup programs are provided, all you need to do is to delete the contents of 'OpenRA-tibsunra2-Windows' folder and \My Documents\OpenRA\.
  48. **Ubuntu/Linux Mint/Debian**
  49. If you want to remove OpenRA, just run
  50. ```
  51. sudo apt-get purge --remove openra-bleed-tibsunra2
  52. ```
  53. in your terminal window.
  54. **OpenSUSE**
  55. Run
  56. ```
  57. sudo zypper remove openra-bleed-tibsunra2
  58. ```
  59. in your terminal window.
  60. **Fedora**
  61. Run
  62. ```
  63. sudo dnf remove openra-bleed-tibsunra2
  64. ```
  65. in your terminal window.
  66. **Arch Linux**
  67. Run
  68. ```
  69. sudo pacman -Rs openra-bleed-tibsunra2
  70. ```
  71. in your terminal window.
  72. **About patches & hotfixes**
  73. --------------
  74. **Patches**
  75. Patches are files that are being used for patching the main game (OpenRA) so that it compiles successfully with Tiberian Sun & Red Alert 2 added.
  76. Basically, Red Alert 2 locates in a different Github repository so patches are needed in order to merge it successfully with the OpenRA codebase. Additionally, some minor patch codes have been added for compilation of Tiberian Sun.
  77. Patches do not affect any bugs or features existing in the game.
  78. ```
  79. Location: /data/patches/
  80. ```
  81. Usage: add new patch file into the /data/patches/linux/ directory (Linux) or \data\patches\windows\ (Windows)
  82. **Hotfixes**
  83. Hotfixes are considered as patches as well (yes, they are patch files, too). The main difference between patches and hotfixes is that hotfixes are meant to be used to fix bugs or add features in the game codebase whereas patches just make OpenRA compilation process with Tiberian Sun & Red Alert 2 possible.
  84. Hotfixes are unofficial in nature. They've not officially been applied by OpenRA developers or any other party and thus playing the game with them may make your version of openra-tibsunra2 incompatible with the official 'openra-bleed' and RA2 mod, even if git version numbers match with other players you see in the lobby.
  85. Hotfixes can be used with other players. However, the hotfixes must have been applied into openra-tibsunra2 versions of any players you want to play with (not forgetting compatibility of git version numbers).
  86. Hotfixes are optional and they've been disabled by default.
  87. ```
  88. Location: /data/hotfixes/
  89. ```
  90. Usage: add new hotfix patch file into the /data/hotfixes/linux/ directory (Linux) or \data\hotfixes\windows\ (Windows)
  91. **Why are Windows & Linux separated (patches/hotfixes)?**
  92. The main reason for this is because Windows & Linux use different line endings in patch files. Different end of lines may make patch files incompatible in other OS so consider this more or less as a precaution.
  93. **How do I create new hotfixes?**
  94. You need a Unix tool 'diff' to create new hotfixes (patch files). For additional information, please see, for example, http://www.cyberciti.biz/faq/appy-patch-file-using-patch-command/
  95. Remember to check "end of line" (Windows or Unix) for every hotfix patch file you create.