Happy Wednesday! PDX Ryagi here, Today’s Tinto Talk is going to be a very short one, so that we can dive straight back into processing 1.3 Beta feedback itself. Still, we wanted to give a brief update on what’s coming up in the 1.3 Beta and where we’re at in the process.

While the initial launch of 1.3.0 open beta was a bit rocky, we feel patch 1.3.2 was a huge improvement building off the groundwork that 1.3 gave us. In some ways, now that the beta has been stabilized properly, the true nitty gritty feedback can begin. We have heard some of you feel the economy and plagues could still use some tuning, so this doesn't mean we’re completely done with them, but we do feel the major issues were solved. If you have any issues with 1.3 that you think could use extra attention, I’d highly encourage you to post about them. Especially here, or in our daily feedback threads.

Future update schedule for 1.3 open beta​

Beta 1.3 will be receiving weekly patches. These will consist of one patch in the first half of the week (For as yesterday’s patch released on a Tuesday) with optional room for a hotfix in the 2nd half of the week.

To assist with these patches, as well as get feedback for the state of the beta in general, we’re continuing with our daily feedback threads. Some threads are “Themed” around a particular topic, while others are more general. Each Friday we will post a miniform, similar to the one posted here which helps us collect some numerical data on the status of the open beta. (Or at least, the status of those that opt in to respond of course).

As a reminder, the open beta is expected to run for about a month! So this process will continue throughout June and into early July.

In game bug reporter​

In the launch days of EU5, we gave players access to an in-game bug reporter tool, however this tool had some issues to work out in the backend, so we temporarily disabled it until a new version could be put together. Now that new version is here in the 1.3 Open Beta! Our public bug report forums are still the bread and butter of bug reporting, but this tool will hopefully come in handy for those that prefer it.

Here’s how it works:
1. You can find the in game bug reporter in the escape menu, but we highly recommend using the hotkey (ctrl + f7 by default) where possible, as it will automatically capture a more accurate screenshot.

2. After you open the report panel, you can fill in a title, description, and steps to reproduce the issue. Be as descriptive as you can!
here is the report issue panel

3. After you have filled in these fields, click the “Gather Data” button on the bottom. This will gather various logs from your machine, and that give us more context to fix the bug on our end.

4. All logs are selected by default, you can deselect ones you do not wish to send for whatever reason.

The Logs gathering section of the panel

5. Click send report! After a short wait, a confirmation message will appear. From here you’re done and your bug has been successfully sent.

After this the report is sent and received, it begins the same process as manual bug reports. For privacy reasons, in-game bug reports are only accessible to the account that reported it and certain Paradox Staff (Such as QA teams and community teams). However if you are logged into the same account you used to report the bug in game, you can track the status of it via our section on the forums titled “Bug Reports [In Game]”.

Here is where your private in game bug reports can be found on the forums

Of course, it’s by no means expected to check in on your own reports, nor do we anticipate this behavior from everyone (A majority in fact, probably won’t be checking). If you prefer to just click the report button, fire and forget, no worries! But for those of you who do want to keep an eye on the status of the bugs you report in game, we hope this new avenue of reporting bugs is utilized.

Live Text, Q&A, June 11th, 15:00 CEST/9AM EST​

When we began the process of the video Q&A last month, we immediately realized that there was no way we’d be able to answer all the questions you have. So we opted to make a follow up live text Q&A over on Discord.

Paradox has been using the same Discord Q&A system for a while now, so there’s a good chance you’re already familiar with process, but incase you aren’t here is how it works:

1. Make sure you have joined the official Discord
2. Submit questions via command in dedicated Ask-and-chat here channel.
3. Questions are reserved, and answered live by the dev team who will be standing by.
4. Questions and their answers are shown publicly in a dedicated questions/answers channel.

Here an example from our EU4 10th Anniversary Q&A. Almost 3 years ago.

We'll be posting announcements and pointers to this process in discord when the Q&A begins, once the channels are up and ready to go, so if you're interested in participating but don't really understand the process as it's described above, no worries.

That’s all for this week folks! We hope you continue to give us feedback on the 1.3 Open Beta, tune into our live text Q&A, and fill out our Friday miniforms. Next week we'll be diving into the feedback we have received on the updated Italian Situations in 1.3. Until next time

• PDX Ryagi