| .. |
|
archivemanager.cpp
|
Initial support for Cyberpunk 2077. Enh, it works for me.
|
2025-08-22 05:41:09 -07:00 |
|
archivemanager.h
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
database.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
database.h
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fsproxy.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fsproxy.h
|
Initial support for Cyberpunk 2077. Enh, it works for me.
|
2025-08-22 05:41:09 -07:00 |
|
fusearchive.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusearchive.h
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusebase.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusebase.h
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fuseinterface.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fuseinterface.h
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
FuseMounter.pro
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
fuseproxy.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fuseproxy.h
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusesandbox.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusesandbox.h
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusestuff.cpp
|
Sorry, this is a broken commit, but I've been working toward VFS integration, atomic mod activation/deactivation within the VFS, and overall stability. I'm committing because at this point it's "playable", but you'll still need to be aware of profiles and profile_selections in your sqlite3 database. At this point, I still haven't implemented a means to differentiate profiles in a meaningful way. (Also, ignore the Archive Test option in Main, that's still something I'm trying to solve wrt fully swapping from libarchive to libunarr.)
|
2025-11-05 01:25:26 -08:00 |
|
fusestuff.h
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
main.cpp
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
modarchive.cpp
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
modarchive.h
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
signalhandler.cpp
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
|
signalhandler.h
|
Implement FUSE VFS as a very early implementation. It can, does, and will break your game.
|
2025-08-20 07:57:00 -07:00 |
