>> The Launcher currently relies on the 'default' profile for sample files (e.g. attributes.xml), so it's unable to create a new profile if it's not there.Oh, I see. I didn't realise the "Welcome" window would create a new profile by itself.
>> And why would you delete the 'default' profile?And why not!? I didn't have a use for it, nor did the game, so I got rid of it. And I'm not the only one who did!
>> It's kinda hard to rely on anything if the users just go around deleting files - you see what I mean.Yes, and no. Yes if we're talking about files in the mod's folders, but we're talking about user profiles! One would expect users to manage them as they see fit. I didn't even had to "go around deleting files", I did it from the game.
>> I'll write a routine that creates a new profile and is independent from the 'default' profile, but it's a lot harder than just using e.g. the attributes.xml from the 'default' profile.Depending on how you look at it, that may not even be necessary. The Welcome screen is intended at new people who only have the default profile, right? So if there is one or more profile but no 'default', there's no need for the welcome window: no problem.
I just a closer took at what that window tells me: "It has been detected that you do not have an MWLL profile yet". Which is wrong, obviously. Maybe a fix to this detection is the only thing needed.
That would leave one potential problem case: a user plays Crysis Wars with one or more profiles, but has deleted the default one. He installs MWLL and uses the launcher: he wouldn't be detected as a first time MWLL user. Is there any significant drawback for that? Would MWLL mess with his Wars profile? I'm thinking about the actionmaps specifically.
The way Crysis handles profiles with regard to mods puzzles me a bit. If I were to launch 'vanilla' Crysis Wars what would happen to my MWLL config? I'm not sure I want to find out
. And there's also the weird requirement of having to join a game in vanilla (I think I never did actually, only logged into CryNet) before being able to join a MWLL server. I'd really like to know what's the problem here.
Speaking of profiles, I have a suggestion for the AutoUpdater: whenever the ActionMapper is updated, the included default_actionmaps.xml should replace Mods/mwll/default_actionmaps.xml. That way, newly created profiles would always use an up-to-date actionmaps.
Actually, I remember part of the reason why I deleted my default profile: so the Actionmapper would stop asking me to choose a profile. I figured that without any choice to make, the profile selector wouldn't pop up. Instead, it kindly noticed me it automatically selected the last remaining profile... Nice try anyway ^^.
I'd like to cut that step off as much as possible, as I doubt many people regularly use and configure several profiles.
My idea on how to do that:
Make the Actionmapper remember the name of last loaded profile.
On launch, check the number of available profiles:
- 0 profile
Something went wrong. Did some users go around deleting files? 
- 1 profile
No need for a reminder, just use that profile! - 2 or more profiles
Check the name of the last loaded profile:
- If no name is recorded or if doesn't point to an existing profile, show the profile selector.
- If it points to a valid profile, load that one.
With the already present Switch Profile option (working as it does right now, not using this logic of course), I think all the bases are covered.
Too much trouble just to save one click? Yeah, probably... but I still like the idea, so I post it anyway.
