The underlying logic should be sound, but this needs a bit more testing before use.

Additional note: This only handles global setting values currently, additional methods need to to be added for handling guild, member, user, channel, and role settings. (More to come on this PR)

I have one question on this: how would the user specify the path to the data file? It's not like we have a consistent location for the actual location of Red in V2 which would mean that predefining the location of the data file for a cog is probably not a good idea

I wasn't planning on this being entirely automated, it would still require a user defined path. (possibly with either a prompt or a file drop)

This just lays the groundwork for some mass config changes from a file. with minimal direct interaction with Config. Still a WIP.

Ideally, at some later point when more conversion tools are ready, you could point a V3 instance at an old V2 install location and have it import every setting which it knows how to (which would still require individual cog creators to specify a conversion spec, and the location their files were stored relative to the base path of V2)

If you think this doesn't belong in base red, I can package this as a coglib instead when the downloader and cog manager are ready to support that.

Yeah, I was clarifying there would be user interaction at some point in the process. I think the basic framework of this belongs in core though

I'm putting any further work on this one on hold until resolution of #1294 since I will need to work directly with some of config's internals for this.

#1335 should help significantly with this.

get_raw and set_raw should make incorporating proper conversions for things at the correct scopes easier. I haven't forgotten about this PR, but I haven't worked on it since my prior comment either.

This has been significantly modified to use new config methods, properly scope data, and if not properly scoping the data, put the data in a custom data group.

With the modifications made, this requires fully retesting which I have not subjected it to yet.
I do not have time to do this today, so this will not be ready for b9 unless someone else has the time to test this.

Do not merge this even if it looks ready at any point until I update otherwise. This can be merged whenever now.

This has been tested now. The following conversions are tested and working:

1. Bank Accounts
2. Custom Commands
3. Economy Settings
4. Filter
5. Past Names
6. Past Nicknames

I'd appreciate a second set of eyes on this though.

Modlog's conversion is not done, but it also is not available through a menu. If I didn't miss any issues with this, this can be merged as-is and have the modlog conversion added as a later PR as unlike the ones here, the modlog conversion will be non-destructive (All of the above imports override existing values (but should retain values without a setting in v2 data))

This also is not specific to any backend as it works directly with config. rather than with the drivers.