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

[Request] Having builds in a file of its own. #7

Open
Presac opened this issue Oct 8, 2020 · 2 comments
Open

[Request] Having builds in a file of its own. #7

Presac opened this issue Oct 8, 2020 · 2 comments

Comments

@Presac
Copy link

Presac commented Oct 8, 2020

I thought it could be a good idea to have the builds in a file of its own instead of being coupled with the settings in config.ini.

In my case, I generally use two different computers, one at home and one when visiting family. I would like to have the template codes be synced between the two, for example by saving the build file in a cloud folder. I could of course do the same right now, but it doesn't seem ideal when settings is in the file too.

@Presac Presac changed the title Having builds in a file of its own. [Request] Having builds in a file of its own. Oct 9, 2020
@thesimonho
Copy link

I second this.

I was trying to find the location where buildpad saves its data but couldn't find a file associated with builds. What is the filename/location in case I want to back it up? @xvwyh

It would be very nice to have builds saved to a separate file somewhere so they're easier to backup and move around to different computers

@xvwyh
Copy link
Owner

xvwyh commented Mar 7, 2021

Both the builds and addon's settings are stored in \Guild Wars 2\addons\arcdps\arcdps.buildpad\config.ini. Backups are being made automatically in \Guild Wars 2\addons\arcdps\arcdps.buildpad\backups, but you'd have to manually restore them in case something goes wrong.

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

3 participants