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
Nexus with gw2launcher #419
Comments
Did you mean localized? Localized execution gives each account its own GW2 folder, so addons have to be added to the account's folder for that account to see them. If you simply delete the folder (either the entire Gw2Launcher folder or specifically the account's folder), it will be automatically recreated with the addons from the original folder, assuming it hasn't been configured to exclude addons. If you meant virtual vs basic mode, virtual mode changes the location of your user folder per account, so if any addons are using the documents folder for example, it'll be different per account. |
This is a problem with the release version, which simply ignores any files in the root addons folder. You'll need to manually copy those files to get the addons working. The beta version doesn't have this problem. |
Thanks, I'll try the beta. Is there some way to know when there's an updated beta to try? |
The beta version is something you can generally ignore. I don't actively update it, it's always in response to someone. It's effectively just the previous release version with minor changes to fix problems like this. |
Reporting back, seems to solve my problem, thanks :) |
I'm running virtualized, and I just started using nexus, but it seems like when virtualized, I don't see my addons dll files in the root of addons, which nexus seems to prefer. Am I doing something wrong? thanks
The text was updated successfully, but these errors were encountered: