| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
easier-to-read-code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
language.
Since we don't have the same launcher the games have, we'll have to avoid including ALL
the datafiles, as the localization-dcps are usually intended to work alone. For now, it's hardcoded
to only load english.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
getters/setters, avoiding direct writes.
|
|
|
|
was off by one
|
|
|
|
|
|
|
|
|
|
"fangame" for now)
This does a minimal engine-startup to open any dcp's and get the proper "startup.settings"-file,
and then get the name/caption fields from that file. There are currently no handling of localized
strings used there (base_string_table would be the culprit). And, there is also no secondary
checks for language (but for that matter, there is no support for chosing language if multiple
exist at this point either).
|
|
packages.
This is helpfull for consistency between registering and lookup, and allows for explicit removal/adding
of sub_paths for the engine. But most importantly it keeps the loading consistent and non-duplicated
for detection.
|
|
|
|
|
