libs/game_bethesda/src/games/starfield/game_starfield_en.ts


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.1" language="en_US">
<context>
    <name>GameStarfield</name>
    <message>
        <location filename="gamestarfield.cpp" line="116"/>
        <source>Starfield Support Plugin</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="126"/>
        <source>Adds support for the game Starfield.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="139"/>
        <source>Show a warning when ESP plugins are enabled in the load order.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="142"/>
        <source>Show a warning when plugins.txt management is invalid.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="401"/>
        <source>You have active ESP plugins in Starfield</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="403"/>
        <source>sTestFile entries are present</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="413"/>
        <source>&lt;p&gt;ESP plugins are not ideal for Starfield. In addition to being unable to sort them alongside ESM or master-flagged plugins, certain record references are always kept loaded by the game. This consumes unnecessary resources and limits the game&apos;s ability to load what it needs.&lt;/p&gt;&lt;p&gt;Ideally, plugins should be saved as ESM files upon release. It can also be released as an ESL plugin, however there are additional concerns with the way light plugins are currently handled and should only be used when absolutely certain about what you&apos;re doing.&lt;/p&gt;&lt;p&gt;Notably, xEdit does not currently support saving ESP files.&lt;/p&gt;&lt;h4&gt;Current ESPs:&lt;/h4&gt;&lt;p&gt;%1&lt;/p&gt;</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="gamestarfield.cpp" line="427"/>
        <source>&lt;p&gt;You have plugin managment enabled but you still have sTestFile settings in your StarfieldCustom.ini. These must be removed or the game will not read the plugins.txt file. Management is still disabled.&lt;/p&gt;</source>
        <translation type="unfinished"></translation>
    </message>
</context>
<context>
    <name>QObject</name>
    <message>
        <location filename="starfieldunmanagedmods.cpp" line="70"/>
        <source>ContentCatalog.txt appears to be corrupt: %1</source>
        <translation type="unfinished"></translation>
    </message>
</context>
<context>
    <name>StarfieldModDataContent</name>
    <message>
        <location filename="starfieldmoddatacontent.h" line="27"/>
        <source>Materials</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="starfieldmoddatacontent.h" line="28"/>
        <source>Geometries</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <location filename="starfieldmoddatacontent.h" line="29"/>
        <source>Video</source>
        <translation type="unfinished"></translation>
    </message>
</context>
</TS>