Hi folks, Unfortunately, it seems that our CS droids were in error when they responded to Ashania's original tickets and for that, we apologize. Currently, in the event of a tie on Voidstar, the winner is randomly chosen. We are going to be improving this with 1.2, but in the meantime, that is how winners are currently chosen for ties on Voidstar. Again, I apologize for any confusion and thank you for letting us know about this.

**UPDATE 9:10AM CST (7:10AM PST/10:10AM EST/3:10PM GMT/4:10PM CET) : All game servers are now available. Thank you for your patience! ** **UPDATE 9AM CST (7AM PST/10AM EST/3PM GMT/4PM CET) : Today's server maintenance has been extended. At this time, we do not have an estimate for the end of the maintenance. Thank you for your patience.** Hello everyone, we wanted to let you know that we will be performing scheduled maintenance for seven hours on Wednesday, February 22nd, 2012 from 2AM CST (12AM PST/3AM EST/8AM GMT/9AM CET) until 9AM CST (7AM PST/10AM EST/3PM GMT/4PM CET). All game servers and SWTOR.com will be offline during this period. This maintenance is expected to take no more than seven hours, but could be extended. For our new players, this weekly maintenance is done in order to make general improvements and to check performance of the game so that we can continue to provide a consistent, quality experience. Quite often (but not always) after a maintenance period there will be a patch to download. After the maintenance, please login via the launcher to download the latest patch. If your launcher was open during the maintenance, you must close and reopen it for a fresh login. Scheduled Maintenance Date: Wednesday, February 22nd, 2012 Time: 2AM CST (12AM PST/3AM EST/8AM GMT/9AM CET) until 9AM CST (7AM PST/10AM EST/3PM GMT/4PM CET) All game servers and SWTOR.com will be offline during this period. This maintenance is expected to take no more than seven hours. Thank you for your patience as we maintain service for Star Wars™: The Old Republic™.

Discuss this week's Community Q&A blog in this thread!

Hello and welcome to the official Q&A thread for questions to be answered for the February 24th, 2012 Q&A blog post. As a reminder, we’ll be starting up a weekly Q&A blog series in which we will select ten questions from the community and post answers to them every Friday. We’ll have the next set of answers next week on February 24th, 2012, but before that, we need your questions! Please use this thread to ask your question (one per community member, so make it count!). On Tuesday at 2PM CST (8PM GMT), we will close this thread, select ten questions, and get answers to them for Friday’s blog post. In order to increase the chances of having your specific question answered and to help us keep the thread manageable, here are some guidelines on asking questions: Keep your question relatively short. Background details are welcome, but don’t go overboard. Please actually ask a question. We want to hear constructive feedback elsewhere in the Forums. Use common sense – we cannot answer everything, especially on far-reaching content. This should go without saying, but be respectful. Limit yourself to one question in this thread, please. You can always ask another question next week! And finally, as a reminder, this is not a discussion thread. Do not comment about what somebody else has posted. Any other posts apart from questions in the thread will be removed. With that being said, please ask away!

Hi there Joaby! Just wanted to let you know that the servers will be located in Australia.

Thanks for all the questions, everybody! As we mentioned before, we'll be closing this thread now to select questions. Tune in this Friday to see if your questions get answered!

Please discuss Stephen Reid's blog post, Incoming changes to global cooldown UI, in this thread.

Discuss this week's Community Q&A blog in this thread!

Hello and welcome to the official Q&A thread for questions to be answered for the February 17th, 2012 Q&A blog post. As a reminder, we’ll be starting up a weekly Q&A blog series in which we will select ten questions from the community and post answers to them every Friday. We’ll have the next set of answers next week on February 17th, 2012, but before that, we need your questions! Please use this thread to ask your question (one per community member, so make it count!). On Tuesday at 2PM CST (8PM GMT), we will close this thread, select ten questions, and get answers to them for Friday’s blog post. In order to increase the chances of having your specific question answered and to help us keep the thread manageable, here are some guidelines on asking questions: Keep your question relatively short. Background details are welcome, but don’t go overboard. Please actually ask a question. We want to hear constructive feedback elsewhere in the Forums. Use common sense – we cannot answer everything, especially on far-reaching content. This should go without saying, but be respectful. Limit yourself to one question in this thread, please. You can always ask another question next week! And finally, as a reminder, this is not a discussion thread. Do not comment about what somebody else has posted. Any other posts apart from questions in the thread will be removed. With that being said, please ask away!

I encourage everyone to report anyone who does this intentionally in-game.

Hi everyone! The resolution for this issue is now up in our public test server: Fixed an issue causing players to not receive Warzone Win mission credit upon winning a Warzone match when the first player to enter the zone leaves the zone before the match concludes. As a reminder, because development is ongoing during testing, it should be noted that all changes and updates listed in the patch notes should be considered incomplete and are subject to change or removal before release to the live servers. If this fix is successful, it will be implemented when 1.1.3 goes live. Thanks again for your continued patience!

Hi everyone, We will be bringing down servers for four hours on February 9th, 2012 from 2AM CST (12AM PST/3AM EST/8AM GMT/9AM CET) until 6AM CST (4AM PST/7AM EST/12PM GMT/1PM CET) in order to deploy a patch. This patch will resolve the following: Killing players on Ilum will now consistently grant Valor and mission credit as intended. All servers will be offline during this period. This deployment is expected to take no more than four hours. Upcoming Patch Date: Thursday, February 9th, 2012 Time: 2AM CST (12AM PST/3AM EST/8AM GMT/9AM CET) to 6AM CST (4AM PST/7AM EST/12PM GMT/1PM CET). All game servers will be offline during this period. This deployment is expected to take no more than four hours. Thank you for your patience as we maintain service for Star Wars™: The Old Republic™. Edit: Patch went live, we are unsticky-ing this thread.

Hi everyone, I wanted to let you know that we will be deploying a patch tomorrow (details coming very soon) with the following resolutions: Killing players on Ilum will now consistently grant Valor and mission credit as intended. Once again, thank you for your patience.

Hi folks, We recently implemented a change to the global cooldown UI with Patch 1.1.2 and we realize that it has been a hot topic here in the Forums. In an effort to prioritize any new changes to the UI, we wanted to poll the community on their opinion of the current global cooldown UI. Please vote in the poll above! As a reminder, please only vote with the cooldown UI changes in mind.

Hi everyone, I wanted to give you all a quick update. The dev team has been investigating the cause of this issue and they're closer to figuring out a solution. As mentioned before, we'll keep you updated with any new developments. Thanks again for your patience on this.

Hi folks, Thanks very much for the feedback on this. We've sent this up internally to investigate and we will update as soon as we have more information for you. Thank you for your patience.

Hi everyone, Thank you for reporting this issue. We're currently investigating and we'll give you an update as soon as we have one. Apologies for the inconvenience, and thank you for your patience.

Liebe Spieler, wir werden am 7. Februar vierstündige Wartungsarbeiten an unserem Dienst vornehmen, und zwar von 9 Uhr MEZ bis voraussichtlich 13 Uhr MEZ. Während dieser Zeit werden alle Spielserver nicht erreichbar sein. Wir gehen davon aus, dass diese Arbeiten nicht länger als vier Stunden dauern werden, aber behalten uns eine Verlängerung vor. Für unsere neuen Spieler: Diese wöchentlichen Wartungsarbeiten erlauben es uns zum einen Verbesserungen am Spiel vorzunehmen, und zum anderen die Leistung der Server zu überprüfen, um euch auch auf Dauer ein konsistent hochwertiges Spielerlebnis zu liefern. Nach diesen Wartungsarbeiten wird es oft (aber nicht immer!) einen neuen Patch zum Herunterladen geben; wir würden euch daher empfehlen nach Wartungsarbeiten immer euren Launcher zu starten. Planmäßige Wartungsarbeiten Datum: Dienstag, der 7. Februar 2012 Zeit: 9 Uhr MEZ bis 13 Uhr MEZ Während dieser Zeit werden alle Spielserver nicht erreichbar sein. Wir gehen davon aus, dass diese Arbeiten nicht länger als vier Stunden dauern werden, aber behalten uns eine Verlängerung vor. Viele Dank für eure Geduld, während wir daran arbeiten Star Wars™: The Old Republic™ weiter zu verbessern. Update: Die Wartungsarbeiten haben begonnen. Update: Hier die Patch Notes. Update: Die Server sind wieder online.

Bonjour à tous, nous souhaitions vous faire savoir qu’une maintenance prévue aura lieu pendant quatre heures le mardi 7 février 2012, à partir de 09H00 CET (heure de Paris) et jusqu’à 13H00 CET (heure de Paris). Tous les serveurs du jeu seront indisponibles pendant cette période. Cette maintenance ne devrait pas durer plus de quatre heures, mais pourrait être prolongée. Pour nos nouveaux joueurs, cette maintenance hebdomadaire est destinée à améliorer le jeu de manière générale et à vérifier les performances afin que nous puissions continuer d’assurer un service constant et de qualité. La plupart du temps (mais pas à chaque fois), il y aura une mise à jour à télécharger suite aux périodes de maintenance. Veuillez vous assurer de mettre à jour votre lanceur de jeu après chaque période de maintenance. Si votre lanceur était actif pendant la maintenance, vous devrez le fermer et le rouvrir pour vous reconnecter. Maintenance prévue Date : mardi 7 février 2012 Durée : De 09H00 CET à 13H00 CET Tous les serveurs seront indisponibles pendant cette période. Cette maintenance ne devrait pas durer plus de quatre heures, mais pourrait être prolongée. Merci pour votre patience pendant les maintenances de Star Wars™: The Old Republic™.

Hello everyone! We wanted to let you know that we will be performing scheduled maintenance for four hours on February 7th, 2012 from 2AM CST (12AM PST/3AM EST/8AM GMT/9AM CET) until 6AM CST (4AM PST/7AM EST/12PM GMT/1PM CET). All game servers will be offline during this period. This maintenance is expected to take no more than four hours, but could be extended. For our new players, this weekly maintenance is done in order to make general improvements and to check performance of the game so that we can continue to provide a consistent, quality experience. Quite often (but not always) after a maintenance period there will be a patch to download. After the maintenance, please login via the launcher to download the latest patch. If your launcher was open during the maintenance, you must close and reopen it for a fresh login. Scheduled Maintenance Date: Tuesday, February 7th, 2012 Time: 2AM CST (12AM PST/3AM EST/8AM GMT/9AM CET) until 6AM CST (4AM PST/7AM EST/12PM GMT/1PM CET) All game servers will be offline during this period. This maintenance is expected to take no more than four hours. Thank you for your patience as we maintain service for Star Wars™: The Old Republic™. Update: The maintenance has started. Update: The servers are back online.

Hello and welcome to the official Q&A thread for questions to be answered for the February 10th, 2012 Q&A blog post. As a reminder, we’ll be starting up a weekly Q&A blog series in which we will select ten questions from the community and post answers to them every Friday. We’ll have our first set of answers next week on February 10th, 2012, but before that, we need your questions! Please use this thread to ask your questions (one per community member, so make it count!). On Tuesday at 2PM CST (8PM GMT), we will close this thread, select ten questions, and get answers to them for Friday’s blog post. In order to increase the chances of having your specific question answered and to help us keep the thread manageable, here are some guidelines on asking questions: 1) Keep your question relatively short. Background details are welcome, but don’t go overboard. 2) Please actually ask a question. We want to hear constructive feedback elsewhere in the Forums. 3) Use common sense – we cannot answer everything, especially on far-reaching content. 4) Limit yourself to one question in this thread, please. You can always ask another question next week! 5) And finally, as a reminder, this is not a discussion thread. Do not comment about what somebody else has posted. Any other posts apart from questions in the thread will be removed. With that being said, please ask away!

Hi again, Once again, thank you for your patience on this issue. We've found a possible solution for this and we will be implementing it in an upcoming patch as soon as we're able to test and verify this solution internally. This process takes a bit of time, but know that we are working to implement it as soon as we can.

Hey everyone, Due to the odd nature of this issue, one of our developers has asked us to post this on his behalf in order to clarify what is happening: The network call in question is from a 3rd party library we use as part of our launching system. The call is intended to optimize the performance of a P2P feature of this library which we do not use and do not intend to use. Note that the call is to a public stun protocol server which is, in fact, hosted by the University of New Hampshire. A future update to our launcher will disable this completely. We hope that answers your question!

Hi everyone, I wanted to let you all know that we have been investigating this issue with the patch note not matching up to in-game behavior since we started seeing these type of threads yesterday. After some investigation, it appears that there was some miscommunication between teams and this patch note was not intended to be included in this last patch. This is a high priority issue for us, and it won't be resolved overnight, but we are actively working towards a solution. We apologize for the error with the patch note and we will also work to prevent situations like that from happening again. The patch note has since been removed and we will keep you updated on the status of a resolution to this issue. Thank you very much for your patience and for your understanding.

Apologies for the delay, but I was waiting to make sure that it was on internal radar and being worked on before I posted.