While the above described system allows us to easily reuse the same messages within each individual masterlist, we still face a problem in the context of multiple masterlists. Here's a complete list of message anchors that can be found within the common section of the different masterlists.ĭynamicall圜reatedPlugin CreationClubPlugins LatestLOOTthread xxSE_Plugins_Requirements xxSE_NVAC xxSE_Required_Scripts The Problem It's precisely this aspect that I'd like to discuss, and I think that in theory we could reduce the workload for masterlist maintainers significantly, at least when it comes to the localized content within the masterlists. This last point is something that we ideally should further improve, because even though it's a system that makes use of standardised messages that can be referenced through key words - and as such it already reduces repetitive and duplicate data - in the context of multiple masterlists it still means that we often need to distribute the same things multiple times to different places. The past has shown that maintaining a masterlist does not solely mean to add sorting rules and cleaning data, it also means verifying existing data, including the removal of invalid data if we come to such a conclusion, as well as maintaining translations of custom messages that can be found within the masterlists.
Silverlock on their nvse page. windows#
With the prospect of supporting potential further Bethesda games, as well as the potential support for the new Windows Store versions of existing Bethesda games, it is inherently clear that the number of supported games and as such, to be maintained masterlists could further grow.īecause of this, it becomes increasingly important to be as sufficient as possible in maintaining the masterlists.
We currently maintain 8 different masterlists.
0 kommentar(er)
