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

Autodetect Local Mods folder for WOTC #246

Open
Iridar opened this issue Dec 22, 2020 · 4 comments
Open

Autodetect Local Mods folder for WOTC #246

Iridar opened this issue Dec 22, 2020 · 4 comments
Labels
Status: Review Verify bug or check feasibility of a new feature. Type: Enhancement
Milestone

Comments

@Iridar
Copy link

Iridar commented Dec 22, 2020

A fresh "installation" of AML automatically adds the Local Mods folder for vanilla XCOM 2:

..\steamapps\common\XCOM 2\XComGame\Mods

But not for War of the Chosen:

..\steamapps\common\XCOM 2\XCom2-WarOfTheChosen\XComGame\Mods

I suggest that it should add both Local Mods folders automatically.

@RevZero RevZero added Status: Review Verify bug or check feasibility of a new feature. Type: Enhancement labels Jan 4, 2021
@RevZero RevZero added this to the v1.6 milestone Aug 18, 2023
@Dragon-32
Copy link

Would you really want two local mods folder? Why not just install in one? I've been using just the base game one for years. I just think it'd be needlessly confusing having two locations to check for an installed mod.

@RevZero
Copy link
Member

RevZero commented Aug 18, 2023

Currently, AML just reads the existing the mod folders from the ini-file. It would not add XComGame\Mods if it wasn't there. On the other hand it would add both, if the game would automatically add them.

The steam mod folder is an exception. If it is not there, it will be added by AML. Not sure what the reasoning behind that was. The folder should also be automatically added, as soon as there are workshop mods. Otherwise it wouldn't work, would it?

@Iridar
Copy link
Author

Iridar commented Aug 19, 2023

Would you really want two local mods folder? Why not just install in one? I've been using just the base game one for years. I just think it'd be needlessly confusing having two locations to check for an installed mod.

  1. When a modmaker compiles a WOTC mod in WOTC SDK, it will be copied into WOTC\XComGame\Mods folder, not the vanilla one.
  2. Highlander requires being loaded from the workshop folder or the XComGame\Mods folder, it will not work from any other folder. And I don't know if it will work in WOTC if loaded from vanilla XComGame\Mods.
  3. Third party mod installation instructions could just be saying "Unzip your mods into XComGame\Mods". Without specifying each specific folder. Having two XComGame\Mods folders, but loading mods only from one of them - that's needlessly confusing.

@Dragon-32
Copy link

OK I see with 3, I'd hope the people for whom 1 and 2 are relevant would be capable of dealing with it.

I read the original suggestion as being "create the folder" but it's "create the folder and define in AML's config"?

Maybe Solariz created the Steam mod folder because they didn't want the Steamworks API to fall over? I don't recall it being mentioned in the early days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Review Verify bug or check feasibility of a new feature. Type: Enhancement
Projects
None yet
Development

No branches or pull requests

3 participants