This one kind of ballooned out of control again, with >390 commits included :P A lot of this is because of translations, however, which was one of the main themes this release. It's still smaller than 311, however, which is also because midway into its development, I have gone on an extended break from WB development. I reserve the right to return at any time, however :P All mentioned commits are authored by @Utumno or @Infernio unless otherwise mentioned. ----------------------------------------------------------------------- ### Python 3.12 (#669) The development began with 3c2837c, which upgraded the codebase to Python 3.12. This turned out be quite a journey (see the commit message for more information). ----------------------------------------------------------------------- ### FileInfo(s) (#336) Remember how I talked about #336 "returning with a vengeance" in the 312 commit, but then there was only a single commit mentioned in that section? Whoops. The reason is that all that work ended up only getting merged in 313, starting with 24fb7fb, which got rid of some ancient, deprecated APIs on FileInfo. See also the refreshes section down below, with which this topic is tightly coupled and hence shares many commits. fb769f0 moved operations and APIs from DataStore to ListInfo subclasses. In d42d769, we refactored ESM swapping and worked towards dropping the table attribute from DataStore, which was then done in ca48e96. Lots of code was simplified and the complexities of persistance here laid bare. This was a necessity for tackling the refreshes. 0a69959 tackled renames, which are still a difficult subject. More work to be done (see #580), but this was more about tackling #336, hence why it's in this section. This issue was closed in c6761b5, but see the refresh section below for more details on that merge. ----------------------------------------------------------------------- ### Localization (#55, #500, #677) This started back in 311, continued throughout 312 and concluded here in 313. Our translations are completely overhauled and done through Weblate now. This is what I picked as the title of the release, since so much effort got poured into it, not only by developers but also by translators. Work in 313 began with a86c2e1, which is the followup to 2442285 from 311. This commit edited our translatable strings to improve their translatability by getting rid of wtxt formatting, dropping leading and trailing spaces, replacing '%' specifiers with named '%(...)' specifiers and improving various miscellaneous problems like concatenations that make translating harder. 394cea7 continued this topic by beginning the transition to Weblate. A POT (PO Template) file was introduced, meaning we could now use more standardized infrastructure like msgmerge to handle updating our translations. We wrote some special porting code to handle substitutions like %s -> %(...)s (named specifiers that we now prefer for their improved translatability, see also #55) and switched all our translation files to UTF-8 (they were a jumble of different encodings before). The second part of the Weblate transition occurred in 4dc8570. This brought us significant architectural improvements like translations being compiled at buildtime rather than runtime, which meant we could stop shipping our vendored dependencies (msgfmt and pygettext from the Python upstream) at runtime. And, of course, it set up the CI infrastructure for an automatic flow of translatable strings to Weblate and updated translations back into the WB repo. Part 3 arrived directly afterwards in dea7ce0. Various small fixes to the CI setup made their way in here. In addition, we improved our script architecture significantly. All scripts now log in one place (scripts/log/*), use the standard Python logging API and feature --help text. Finally, the build script got massively simplified by dropping its brittle git stashing. Instead, we explicitly exclude the files we don't want to include in the built releases. fd36189 fixed a couple issues with our translatable strings like double spaces or usage of '...' instead of the Unicode ellipsis '…'. add5b8f then improved our l10n generation script to automatically add the 'python-format' flag to appropriate translations, which significantly improved Weblate's handling of our translations, making it highlight and warn about translations that don't properly handle the format specifiers (along with other cool features, like Ctrl+1/2/3 etc. to directly insert format specifiers from the source string into the translated string you're working on). 50e5b02 saw a few more small fixes and improvements to the translatable strings, but most importantly brought the first new languages in the form of Swedish by David Brofalk and Turkish by @TheMalteseFalcone. In ded5321, more translatable strings got edited to make translations easier (e.g. by making the ==Last== marker translatable) and pulled in a new Ukrainian translation by @IllusiveMan196 along with various translation updates. More translation updates were pulled in with da619a7. In c8380e1, @xsSplater finished the Russian translation of WB. e8b8665 brought in even more translation updates. The last big merge of this release was e648960, which introduced a new Tamil translation by @TamilNeram and updated some other languages. ----------------------------------------------------------------------- ### App Launchers (#570) There's still a lot to do here, but we got started refactoring the app launchers (the little icons on the status bar that launch other applications, e.g. LOOT). dbdccd5 saw saw a load of miscellaneous cleanup and refactoring in app_buttons.py. ----------------------------------------------------------------------- ### Refreshes (#265, #353) One of the other big goals of 313 besides the translation rework was refactoring the refresh system. We want to eventually move to event-based refreshes (see #265), but to do that, we need a rock-solid system for tracking refreshes. This is closely related to #336 (see above), because in order to track refreshes properly, we need to track files properly. bcf08e3 began work here by reworking the way we calculate changes to the load order. It also introduced RefrData (adapted from BAIN's RefreshInfo) to centralize all the various bits of refresh info (updated/added/deleted files). fb769f0 centralized refreshes by moving various operations from DataStore to subclasses of ListInfo. Along the way, a few edge case bugs were fixed and the code got a major facelift. In eea41fa, the BSA load order calculations were refactored heavily. The result is much more accurate APIs, a cache and support for Morrowind BSA load order. That also paves the way to the BSA tab (#233). Finally, in c6761b5, the FileInfo(s) APIs got a few more improvements, refreshes got centralized further and the final phase of the refresh refactoring can be begun in earnest. And the first part of the final phase of #353 also managed to sneak in at the last minute in 222954b, where we can, at last, pass the RefrDatas introduced by the merges mentioned above to RefreshUI, which should signifcantly reduce the amount of GUI redrawing we have to do when refreshing. ----------------------------------------------------------------------- ### Game support improvements @sibir-ine contributed many improvements to our out-of-box game support, especially for Starfield, along with some fixes and updates for the record definitions. Many thanks! 906e14a restored support for the disc/retail versions of older games, which we accidentally broke when we rewrote Steam game detection back in 20dd955. Whoops! ----------------------------------------------------------------------- ### Skyrim VR ESLs (#673) Skyrim VR does not support ESLs out of the box. However, a third-party SKSE plugin was created that backports ESL support to Skyrim VR. So in 313, we added support for these. This is interesting, because it's the first time we have a truly dynamically supported game feature, where we need to check for the existence of the SKSE plugin to know whether or not the game supports ESLs. c815d10 includes some preliminary support by fixing a bug where WB would write out BPs with a header version that SSE introduced, but Skyrim VR does not understand (without the third-party plugin). ca361bd fully implemented support for ESLs in Skyrim VR. ----------------------------------------------------------------------- ### Fallout 4 (#482, #525, #680) More FO4 record definition work landed in d6d53c4. This merge introduced some new tools for building record definitions and implemented 7 new record types. I honestly miss writing the FO4 record definitions, it's very methodical and lets me just turn my brain off and listen to music, so perhaps look forward to more of these from me in 314 :) The FO4 Next Gen Update also happened during 313's development, so we added support for it in cb24caf. ----------------------------------------------------------------------- ### Starfield updates (#681, #688) We still barely support Starfield, but some improvements have been made to WB's support for it. c54aa91 added support for saves created by Starfield v1.9. 6ef81f4 featured some preliminary work on Starfield support, including work towards v1.14 save files, reverting much of the Overlay support (thanks Bethesda...), reverting the CCC file workaround, etc. With the newer Starfield updates comes a new plugin type, medium plugins (plus there's the blueprint plugins, and the older overlay plugins that Bethesda broke). It became clear that our current, mostly ad hoc, handling of plugin flags would no longer scale. So in 6229baa, we tackled this mess by encapsulating all that complexity in a new class, PluginFlag. The rest of the outstanding Starfield support for 313 was also implemented in this merge. As a side effect, a lot of refresh complexity was reduced, so this is also under #353 (see refresh section above). ----------------------------------------------------------------------- ### Persistent language setting (#26) The oldest still-open issue in the WB repo was closed in this version. Issue #26 was about making the language switching option in the settings dialog persistent. There was a good reason why this issue was open for so long, however: WB's settings are stored per game, but language has to be set before a game is chosen. This fundamental problem made this issue infeasible for a long time. However, with all the translation improvements and updates that landed in 313, we decided to tackle this. We settled on introducing a new TOML file for early boot settings, which also permitted us to introduce another long-requested feature: remembering the last-selected game and defaulting to that in the game selection dialog. All these changes and improvements landed in 50af459. ----------------------------------------------------------------------- ### Load order (#578) Lots of random refactorings up above improved our load order handling, but a concerted effort to improve it even further was made as well in issue #578. The first major merge related to this was 7345863, which massively reduced the complexity of _games_lo.py and moved the static data (e.g. the CCC fallbacks) to game/, where it belongs. Somewhat born out of this and the launcher refactoring mentioned above, ini_files.py got a major facelift in e5dcd17. The entire parsing logic got rewritten and lots of complexity disappeared. More load order refactoring happened in 3587801, where we cleaned up pinned plugins handling to pave the way for better Starfield support (see section above). ----------------------------------------------------------------------- ### Customizable checkbox colors (#511) Not done yet, but @lojack5 did great work towards this goal in f962cc9, where the checkbox PNG images were replaced with dynamically generated SVGs. This already has the advantage of scaling perfectly on high DPI displays, but will also allow us to make their colors customizable in the future. As a bonus, the game icons also got turned into SVGs for high DPI scaling. ----------------------------------------------------------------------- Massive thanks to everyone who contributed to this release, including: @Utumno, @Infernio, @sibir-ine, @lojack5, @TheMalteseFalcone, @xsSplater, @robertgk2017, @cottondisciple, @jbostrus, @IllusiveMan196, @Evan555alpha, @TheBronn, @TamilNeram, @JonySnowball, @ernieIzde8ski, @Ortham and many more who GitHub's contribution tracker doesn't list.

Add support for the Fallout 4 Next Gen Update #680

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions