Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Developer Tracker

Star Wars: The Old Republic > English > Developer Tracker


CommunityTeam
Darth Malgus - Belsavis World Boss not respawning | 10.28.2020, 12:55 PM
Hi all,

Thanks for the different reports concerning the Belsavis Wolrd Boss issue you all encounter.

Our team is currently looking into it. I'll update you when I have more information.


CommunityTeam
Did no one bother to proof read? (Feast story) | 10.28.2020, 04:34 AM
Hi iFenris,

Thanks for the report concerning the missing word in A Dash of Kindness Mission.

I've transferred the information to our team. I'll update you when I know more.


CommunityTeam
Maintenance: October 27, 2020 | 10.27.2020, 07:31 AM
Hi,

All SWTOR servers are once again available!

Thank you for your patience.


CommunityTeam
Agent Story Mission on Voss Bugged | 10.27.2020, 05:17 AM
Hi all,

As mentioned in the 6.1.4b patch notes, this bug will be fixed with today's patch.
  • Players will once again be able to interact with the Tu-neh fruits in the Imperial Agents' Class Mission "Paying Respects" on Voss, as intended.


CommunityTeam
The Foundry FP - Revan part | 10.27.2020, 05:10 AM
Hi Grendel_Echo,

Thanks for the report concerning the bug with The Foundry Flashpoint.

Our team is currently looking into it. I'll update you when I have more information.


DanielSteed
Maintenance: October 27, 2020 | 10.26.2020, 10:24 AM
Hey everyone!

The patch notes for tomorrow's maintenance are now up and you can find them here.


CommunityTeam
Game Update 6.1.4 - Known Issues | 10.23.2020, 11:58 AM
Hi folks,

The following known issue has been added to the list:
  • The "iRating Adjustment" buff is not stacking correctly when wearing items with alignment requirements. Workaround: Re Equip any item again.


CommunityTeam
Crew missions break Cantina Rush | 10.23.2020, 06:11 AM
Hi ceryxp,

Thanks for the report concerning the bug with the returning companion and Cantina Rush Mission.

I've transferred the information provided to our team for additional verification. I'll update you when I have more information.


CommunityTeam
Maintenance: October 27, 2020 | 10.23.2020, 03:48 AM
Hey everyone,

We will be taking the servers offline on October 27, 2020 to deploy Game Update 6.1.4b.

Details:
DATE: October 27, 2020
TIME: 5:45AM - 8:00AM PDT (1245 - 1500 UTC)
VERSION: 6.1.4b

Patch notes will be available on Monday, here: http://www.swtor.com/patchnotes.

Thank you for your patience as we maintain Star Wars™: The Old Republic™!


CommunityTeam
Agent class quest | 10.23.2020, 03:40 AM
Hi dsbrock,

As mentioned in this thread: Agent Story Mission on Voss Bugged and in the the known issues list: Game Update 6.1.4 - Known Issues, the issue you encounter is a known issue.

Our team is currently looking into it. I'll update you in the threads above when I have more information.


CommunityTeam
Story Broke fix asap | 10.22.2020, 11:58 AM
Hi TattooYoda,

Thanks for the report.

Our team is currently investigating this bug. I'll update you when I have more information.


CommunityTeam
Game Update 6.1.4 - Known Issues | 10.22.2020, 11:57 AM
I've added the following issue to the list:
  • The "Task at Hand" Mission can not be completed by Republic characters. The launch button, walking into the phase, or using the highlighted keyboard, are not triggering the cutscene.
    • Workaround: Resetting the mission on the fleet and not on Odessen should allow players to start the Mission with the launch button.


EricMusco
Group and Warzone Mismatch Fix | 10.22.2020, 11:03 AM
We've seen good results so far from the fix we deployed and so we are now rolling it out to all servers. Let us know if you continue to experience being grouped with another player and then get placed in a separate Warzone.

Thanks all.

-eric


JenHarkness
Guild Ship missing | 10.22.2020, 10:59 AM
Hi everyone! I know the guild ships have been disappearing for a lot of guilds lately, and it seems like it's been around forever. The good news is that things should be much better after the release of 6.1.4. Since this has been around a while, I wanted to take a bit of time to give you all a peek behind the curtain to help explain why it was so hard to track down. I also really want you to understand just how much we appreciate your forum posts and bug reports. Even when we don't reply, as a developer my first stop in investigating a backend issue is always looking at logs, and the more detailed the reports are, the easier it is for me to find something.

A bit of background on the Backend
Like many games, we store our persistent character data in a database. To make updates faster, we have a cache layer between the game and the database that batches up updates. Then we write the batch to the database. The benefit is we get better performance, but the drawback is that if there is one bad update in the batch, we abort the entire batch. Most of the time, the effect of aborting is that characters get kicked to character select, which isn't great, but is better than the data being corrupted. The good thing is, these errors are pretty rare, and are always the highest priority for us to fix.

So why might an update fail? Well, one of the nifty things you can do with a database is define a constraint on your data. That's a rule that can never be broken. Now the database is your last line of defense against something going wrong and your data getting corrupted. For this story, the important constraint is on unique character names. If we try to write a batch of updates, and one of the characters in that update has the same name as someone else in the database, the batch gets aborted.

A Victim of our own Success
Now, you all might remember some complaints on the forums lately about character renames not working. Behind the scenes, we have a big list of all the names on each server, so that if someone tries to use a name that's taken, the rename gets rejected before it gets anywhere near the database. Well... how does that list of names get built, you might ask. Basically, before we let you guys into the servers after a restart, the servers ask the database for that list of names so that they can make quick decisions later.

Here's the part where we have become a victim of our own success. It turns out that the programmer who wrote that database query back in 2009 or so added a parameter for how far back in the past to search for taken names. He happened to put 3000 for the default number of days. Yup, that's a bit over 8 years, and we launched a bit less than 9 years ago. It's a bit off because of some database maintenance we did the first year, but you get the point. So anyone who tried to rename a character with one of the names that was last played 8+ years ago would have the rename look like it succeeds, but then the database says no.

Luckily, that was a pretty easy fix, just increase the number. (Although if we start having rename issues in 2093, feel free to yell at me!)

OK.. but why would this have anything to do with guild ships??
Well, it turns out that sometimes the data that stores info on your guild ships was part of the batch that was being kicked out because of a bad rename. Yes, I know the guild ship problems have been happening for years, but that's because anytime we were having database errors, sometimes the guild ships were being caught in the crossfire. However, like I mentioned above, we always fixed the database errors super quick, so people would complain about guild ships, but then we couldn't reproduce it and they died down, because we'd already fixed the database error.

Here's the good news, this time it's really fixed. We've both fixed the rename error, and thanks to the guilds who have given super timely info, we were able to spot the guild ships getting caught in the crossfire. Now that we know what's going on, we were able to make it so that if the guild ship does get batched up with a bad batch, it will be automatically reloaded. So, no more disappearing flagships even if we have database*errors in the future. For realz this time.* (We hope!)


CommunityTeam
Game Update 6.1.4 - Known Issues | 10.22.2020, 09:22 AM
Hi GeeksCraft,

Thanks for reminding me of this bug. I was currently adding it to the list. You were too fast.
  • There is no lip-sync in the French and German conversation cutscenes in the "Meeting Jekiah Ordo" Mission.


CommunityTeam
No Lipsync in german cutscene when you meet Jekiah | 10.22.2020, 09:13 AM
Hi all,

Thanks for the reports concerning the lip-sync bug in the conversation cutscenes of "Meeting Jekiah Ordo" Mission in French and German.

Our team is currently investigating this bug. I'll update you when I have more information.


CommunityTeam
Game Update 6.1.4 - Known Issues | 10.22.2020, 07:21 AM
Hi folks,

I've added the following issues to the list:
  • Items:
    • The Obsidian Squad Recon Walker's visual effects disappear when the mount is used or when the flourish is used.
  • Others:
    • The ENTER button can not be used to initiate research in the filter section of the “Who” tab.
    • Quick Travel Mission and summon can lead to instant death.
    • Right-click "Invite to group" option doesn't always work.


EricMusco
Group and Warzone Mismatch Fix | 10.21.2020, 12:24 PM
Hey folks,

As some of you know there has been an intermittent issue in SWTOR where in rare circumstances, grouped players can end up in different Warzones. We are testing a fix for that this evening on Darth Malgus only. If you are a PvPer on DM, feel free to jump in and queue for Warzones like you always do. Let us know if you run into any issues! We'll circle back tomorrow and let you know what we are seeing. Thanks as always.

-eric


CommunityTeam
Maintenance: October 21, 2020 | 10.21.2020, 07:49 AM
Hi,

All SWTOR servers are once again available!

Thank you for your patience.


CommunityTeam
Agent Story Mission on Voss Bugged | 10.21.2020, 06:40 AM
Hi Pokemon-Man,

As mentioned in the Game Update 6.1.4 - Known Issues post, the bug you encountered is a known issue.

Thanks for the report.
Star Wars: The Old Republic > English > Developer Tracker