Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

static files #29

Closed
HarHarLinks opened this issue Dec 14, 2019 · 2 comments
Closed

static files #29

HarHarLinks opened this issue Dec 14, 2019 · 2 comments

Comments

@HarHarLinks
Copy link
Contributor

"Mod Manager components" is more descriptive and relevant than just "files".
Here you use "supporting files":

<system:String x:Key="string_dialogCouldNotDownloadStaticAssets">Could not download static supporting files to ME3Tweaks Mod Manager. Mod Manager may be unstable due to these files not being present. Ensure you are able to connect to Github.com so these assets may be downloaded.</system:String>

Out of curiosity, which ones are the static files anyway? Got to do with "content updates"?

@Mgamerz
Copy link
Member

Mgamerz commented Dec 14, 2019

Static files are items that aren't going to change, so I don't include them in the main download, as updates to Mod Manager download the whole package. Things like the object info databases, which together add like 1-2MB even compressed, likely aren't going to change so I only download them once mod manager is setting itself up the first time. "Static" in the idea that they don't change.

But components would probably be more accurate in this case, I'll change it in INT.

@HarHarLinks
Copy link
Contributor Author

i think in cases like this (more often actions like checking, downloading, updating), it also needs to be very clear whether content/files/components refer to M3 or Mods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants