Move the AlephOne Folder Out of Documents (Windows)

[AdreKiseque]

Aleph One currently generates a folder in a user's Documents directory to store quick save data (and possibly other things, but that's all mine has). Though this isn't uncommon practice, Documents is really not an appropriate place to store application files like this, especially in the current day where Documents is often synced to OneDrive. More appropriate would be the installation directory, the AppData folder, or even the native Windows "Saved Games" folder in the user folder. I hope this change can be considered.

[Zoran-The-Great]

Agreed. My vote goes to the installation directory.

Having files for a game spread across the OS is just bad outdated practice and disrespects the users choice of where the game directory is placed.

In regards to the zip install, it also breaks portability in the event that the game folder is ever needed to be moved.

This is also the behavior of other predominant source ports for other games like GZDoom, EDuke32, DarkPlaces,, etc. where game saves, screenshots and the like are all stored within the directory of where the executable is.

[treellama]

At the time it was implemented, this was the recommended location by Microsoft. I think there is a Saved Games folder now, but we would have to implement some migration strategy. In any case, there is no guarantee the install location is writable, so that is not a good option.

[Zoran-The-Great]

At the time it was implemented, this was the recommended location by Microsoft. I think there is a Saved Games folder now, but we would have to implement some migration strategy. In any case, there is no guarantee the install location is writable, so that is not a good option.

Microshaft also seems to think that garbage like recall, forced automatic updates and jamming copilot down your throat is a good idea... So...

For what reason would the install directory not be writable?

As mentioned, this isn't a problem for other source ports. Just trying to discern what the difference is in this case.

[AdreKiseque]

The other source ports you mention are all portable installations, you extract a zip file and plop it in wherever you like. But for something that installs through, say, Steam, the installation directory typically goes in Program Files, which requires elevation to write to. Obviously, we don't really want to be requesting those sorts of permissions just to save data and the like.

I'm not super familiar with how Steam lets developers configure installations, but assuming the main directory for the binary and associated resources is fixed, the best option is to just store the extra files in AppData, which exists explicitly for this sort of thing.

This isn't on the Aleph One team, though. Microsoft has been notoriously bad and unclear with guidelines and standards for this sort of thing, and different MS products even conflict in this regard. But yeah, for a variety of logistical reasons, Documents is a pretty bad location, regardless of official recommendations.

[Zoran-The-Great]

The other source ports you mention are all portable installations, you extract a zip file and plop it in wherever you like. But for something that installs through, say, Steam, the installation directory typically goes in Program Files, which requires elevation to write to. Obviously, we don't really want to be requesting those sorts of permissions just to save data and the like.

I'm not super familiar with how Steam lets developers configure installations, but assuming the main directory for the binary and associated resources is fixed, the best option is to just store the extra files in AppData, which exists explicitly for this sort of thing.

This isn't on the Aleph One team, though. Microsoft has been notoriously bad and unclear with guidelines and standards for this sort of thing, and different MS products even conflict in this regard. But yeah, for a variety of logistical reasons, Documents is a pretty bad location, regardless of official recommendations.

Yes, which is what I alluded to previously when referencing the zip install option available on this repo yet the Aleph One folder is still placed in the documents directory...

Why does steam dictate how Aleph One is installed?

The source for all 3 games is public and freely available. The steam version is irrelevant at this point.

[AdreKiseque]

The Steam version has achievements!

But yeah, I missed that you meant the zip install, my bad. In that case, there's no reason I can think of that the installation directory couldn't be used.

[Zoran-The-Great]

The Steam version has achievements!

But yeah, I missed that you meant the zip install, my bad. In that case, there's no reason I can think of that the installation directory couldn't be used.

Having the zip install truly portable would be appreciated.

Hopefully this is considered.

[Kolfering]

The user could still decide to install the game in Program Files for instance where the game won't be able to write the saves unless the user is running it with elevated privileges.

[AdreKiseque]

The user could still decide to install the game in Program Files for instance where the game won't be able to write the saves unless the user is running it with elevated privileges.

That's largely on the user. It's typically understood you shouldn't manually put things in Program Files unless you know what you're doing. Adding a disclaimer and/or making the location configurable (I recently booted up an emulator that was considerate enough to ask if I wanted to store data in the installation directory or in Documents... it still created a second folder in Documents even with the other option selected but it's the thought that counts) could help minimize trouble but you can only do so much to protect people from themselves.

[Zoran-The-Great]

The user could still decide to install the game in Program Files for instance where the game won't be able to write the saves unless the user is running it with elevated privileges.

That's what the executable install is for.

[Zoran-The-Great]

So has the zip download actually been made portable now or is it still installing config files and save games in the appdata/documents directories?

If not, why is there even a zip option since there's literally no difference from the exe install?

[Zoran-The-Great]

@Kolfering

So has the zip download actually been made portable now or is it still installing config files and save games in the appdata/documents directories?

If not, why is there even a zip option since there's literally no difference from the exe install?

[treellama]

The zip file contains both the exe and the data files. The exe is just the engine.

[Zoran-The-Great]

The zip file contains both the exe and the data files. The exe is just the engine.

No kidding...

You seem to fail to understand that zip install options are supposed to be portable meaning you can move the game folder to another system and continue where you left off which is not possible with config files/save games being stored in appdata/documents which is EXACTLY what the exe install does.

Why even offer both if they have the same final result? Non-portable.

[treellama]

They are no such thing, they are just zip files with the exe and the data files in them. Have been that way since the early 2000s. I think there is a legitimate case here for moving the data files to the new Saved Games folder, as difficult as a migration as that will be. But a portable install is outside the scope of this issue; please stop bringing it up.