Jump to content
Sign in to follow this  
Lixil

[PC] Patch Notes 1.19.7 (1061)

Recommended Posts

Hello everyone!

 

A new patch is going up onto the Live servers for PC. This patch will be happening on Wednesday 12/12/2018. Maintenance will start at 8 AM UTC (one hour earlier than normal) and will last for 6 hours.

 

This patch will be introducing two new features. You will now be able to secure your account through Two Factor Authentication (2FA) and we have reintroduced the /report feature. To access the new window type /report in the chat and it will display. For more information related to these new features, please check out our post here.

 

Patch Notes:

  • Added in support for 2FA
  • Updated the /report command to work differently than before

 

Known Issues:

  • Choosing the cheating category will not correctly update the report button. The workaround for this issue is choosing the cheating category before the player name is entered. If the category is chosen first, then the player name is entered, it will work correctly.
  • Using /report (name) will not correctly update the report button. Simply delete the last letter/number of the character's name once in the report form and re-enter it to correctly refresh the button.
  • Like 12
  • Thanks 3

Share this post


Link to post
Share on other sites
4 hours ago, Lixil said:

Known Issues:

  • Choosing the cheating category will not correctly update the submit button. The workaround for this issue is choosing the cheating category before the player name is entered. If the category is chosen first, then the player name is entered, it will work correctly.

Lmao, patch ain't even out and there's already a problem. How do you miss this before going live?

  • Like 1
  • Dislike 7

Share this post


Link to post
Share on other sites

is there a sneak peak for the next intended patch

 

anything juicy

Share this post


Link to post
Share on other sites
1 hour ago, Ch1ck said:

Lmao, patch ain't even out and there's already a problem. How do you miss this before going live?

The reason that the known issue exists is due to the fact that we did catch it. The problem with QA, and software development in general, is that sometimes fixing something has a side effect of breaking other things. Our QA team found the issue but because there was a simple workaround, we decided to not delay the patch. It will be fixed in the next patch that we do, along with another issue that Im currently adding.

  • Like 7
  • Thanks 2

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×