andrei-drexler / ironwail

High-performance QuakeSpasm fork
GNU General Public License v2.0
480 stars 43 forks source link

[FeatReq] autosave/ and screenshots/ should be organized diffrently #273

Open lavenderdotpet opened 7 months ago

lavenderdotpet commented 7 months ago

autosave/ should either be saved in as a .autosave/ [hidden folder]

or the way i would prefer in /home/user/.local/share/ironwail/ screenshots/ should either do the same or put it in the dir the engine is running from and for windows u could go the route of putting stuff in the Documents\ folder its just annoying to keep having to delete the auto saves folder from my mod dir

4LT commented 7 months ago

I'm not fond of creating more hidden files, but I do like the idea of using a subdirectory of $HOME/.local/share ala the XDG proposal instead of polluting the mod directory.

In the meantime, there is a script I wrote that strips out extraneous files

====

However, theoretically assets (the entirety of the .ironwail directory) should be under $HOME/.local/share... perhaps generated files could go to $HOME/.cache?

lavenderdotpet commented 7 months ago

yeah i prefer the freedesktop specifications setup i just said the top one if they wanted to do the bare minimum

id also suggest addons.json and addons.url.dat should also go into ./local/share/ironwail image

mmillar-bolis commented 7 months ago

What about implementing fs_savepath to give the user the option to specify a write path, in the manner that later Quake/idTech engines do?

tunbridgep commented 6 months ago

honestly, I would love a -userdir command-line argument to specify the folder where ironwail.cfg, autosaves, screenshots etc go.

Not only will this not pollute mod directories, it also lets us use the same settings file for multiple mods.

Ideally, the engine would load cfg files in -userdir first, then would use the XDG path, then the mod directory, so mod developers can include autoexec.cfg and etc to apply various needed settings without interrupting our user configs.