Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer

Patch Issue, April 11th - Information

STAR WARS: The Old Republic > English > General Discussion
Patch Issue, April 11th - Information
First BioWare Post First BioWare Post

AllisonBerryman's Avatar

04.11.2012 , 11:50 AM | #1 This is the last staff post in this thread.  
Yesterday (April 11th), some patch-related changes were mistakenly deployed early. These changes only affected those logging into the game for a brief window. We corrected this unintentional change as soon as possible.

Game Update 1.2 is now deployed to the live servers. If you downloaded the early-deployed patch yesterday and did not re-patch the client, you should be able to login and play without additional patching.

We apologize for the confusion and inconvenience caused.

[Edited 4/12 to reflect current information.]

StephenReid's Avatar

04.12.2012 , 07:31 AM | #2
Good morning everyone. After yesterday's patch deployment issue, we issued information about re-patching in good faith, specifically this statement:

1. If you are currently re-downloading the client, and are in initial "downloading" phase (around 11GB), you can exit the launcher to interrupt this download and play 1.2 tomorrow without having to complete it. If you reach any "installing" phase, you will need to complete the re-download.
Sadly, it now appears that information was incorrect.

At this time, we understand that anyone who cancelled the patching process as described above will need to complete a full re-download of the game client, or re-install the game and then re-patch. There are two options available to you:
  1. Allow the launcher to re-download the full game client and patch to Game Update 1.2
  2. If you have access to physical install DVDs from a retail box, uninstall your game client and re-install the game, then patch to Game Update 1.2
Both of these options will allow you to play Game Update 1.2.

We sincerely apologize for the inconvenience and the confusion caused by this messaging.