Original Post — Direct link

Please help me im stuck. The mission Brewing for a rebellion at Buckinghamshire has crashed and I cannot proceed any further. It says reach the longhouse and i get there and when i try to ''Force the door'' Noone helps me. Sig and the assasin just stand there and dont help open the door. It also doesnt show the green # on the door or on the map whne the mission is selceted its bugged!! All my autosaves are still bugged and my hard save is arriving in England. Please can you help 
This is On Uplay Plus on PC.

If this cant be fixed then i will be abandoning the game im not starting again

about 4 years ago - UbiExcellent - Direct link

@ashtg133 Hey everyone! We haven't received any reports about this issue before. Would any of you be able to send over a video of this happening, so I can get that over to our teams to be evaluated further please?

about 4 years ago - UbiExcellent - Direct link

@ashtg133 Hey everyone! We haven't received any reports about this issue before. Would any of you be able to send over a video of this happening, so I can get that over to our teams to be evaluated further please?

over 3 years ago - Ubi-Borealis - Direct link

Hello there!
 
I'd like to reach out to you all with an update. I'm happy to announce that the development team intend to deploy a several fixes for "Brewing Rebellion" in TU 1.2.2. This update will be deployed 15 June, 2021 at 2 PM CEST / 8 AM ET. The list of fixes includes the following:

  • The door to the longhouse in Buckingham cannot be forced open
  • Quest NPCs, such as Basim and Sigurd, cannot be interacted with
  • The Thegns are not registered as rescued after they are freed
  • Objective marker appears off-map during the "escort the thegns to safety" objective
  • "Secure the Longhouse" is not marked as completed

 
If you are still encountering issues with "Brewing Rebellion" following TU 1.2.2, please don't hesitate to update this thread so we can take a closer look. Please include a video that shows the following:

  • You have the latest Title Update installed on your platform. You can view this information in the opening game menu in the bottom right-hand corner.
  • The issue you're experiencing in-game following this update.

 
Additionally, please ensure that you have an up-to-date save uploaded to the cloud. We can then pass these reports to the development team for further investigation.
 
Thank you! 😊

over 3 years ago - Ubi-Borealis - Direct link

Hello there!
 
I'd like to reach out to you all with an update. I'm happy to announce that the development team intend to deploy a several fixes for "Brewing Rebellion" in TU 1.2.2. This update will be deployed 15 June, 2021 at 2 PM CEST / 8 AM ET. The list of fixes includes the following:

  • The door to the longhouse in Buckingham cannot be forced open
  • Quest NPCs, such as Basim and Sigurd, cannot be interacted with
  • The Thegns are not registered as rescued after they are freed
  • Objective marker appears off-map during the "escort the thegns to safety" objective
  • "Secure the Longhouse" is not marked as completed

 
If you are still encountering issues with "Brewing Rebellion" following TU 1.2.2, please don't hesitate to update this thread so we can take a closer look. Please include a video that shows the following:

  • You have the latest Title Update installed on your platform. You can view this information in the opening game menu in the bottom right-hand corner.
  • The issue you're experiencing in-game following this update.

 
Additionally, please ensure that you have an up-to-date save uploaded to the cloud. We can then pass these reports to the development team for further investigation.
 
Thank you! 😊

about 3 years ago - Ubi-Borealis - Direct link

Hello there!

I apologise for the delayed update. I'm happy to confirm that the development team have deployed a couple of fixes for "Brewing Rebellion" with the release of TU 1.4.0. This update was deployed 9 November, 2021, and contained fixes for the following issues:

  • The Thegns are not registered as rescued after they are freed.
  • Basim and Sigurd didn't follow the player in "Brewing Rebellion." 


We will now be marking this thread as resolved.

If you are encountering any further trouble with "Brewing Rebellion," please don't hesitate to reach out to us with an update within this thread. Please include a video which shows the following:

  • You have the latest Title Update installed on your platform. You can check this in the bottom right-hand corner of the main menu.
  • How you are unable to progress in "Brewing Rebellion." Please be as specific as possible with the issue you've encountered, as this will help the development team to investigate further.


I recommend uploading the video to a sharing platform, such as YouTube or Google Drive, as this will allow you to post a shareable link within this thread for us to take a closer look at.

Thanks! 😊

over 2 years ago - Ubi-Keo - Direct link

Hello everyone, 

I'd like to reach out to you all with an update. The development team have contacted us and have confirmed that the following issues should be resolved with the release of Title Update 1.5.1.

  • The Thegns aren’t registered as rescued
  • Basim and Sigurd don’t follow when escorting the Thegns to safety


You can read the full patch notes here.

The patch will be deployed today at 12 pm UTC/GMT, 1 pm CET, 7 am EST, 4 am PST, and 11 pm AEDT. If you are still experiencing this issue after installing the new update then please don't hesitate to share an update within this thread so we can notify the development team.

When sharing a new report, please can you provide us with the a video which shows the following:

  • You have the latest Title Update installed on your platform. You can check this in the main menu screen before loading your save.
  • That you are unable to progress in the quest "Brewing Rebellion" as The Thegns aren’t registered as rescued or Basim and Sigurd don’t follow when escorting the Thegns to safety.


Additionally, please ensure that you have an up-to-date save file uploaded to the Cloud. This support article can help you to do this.

We can then use these reports to reopen the investigation should the issue persist following the 1.5.1 update.