vlzvl could you share some sort of a roadmap for 2024 for your game?
Sure, although there's nothing similar to a "roadmap" at the moment, since the game is on
"early access".
This alone means that development time is shared between
- fixing based on people's feedback (bugs, features, usability etc.)
- adding new content
- *testing targeted builds
- repeat
when the backlog of feedback is reduced (its kinda big at the moment, with some things that needs prioritisation), the "3. testing targeted builds" will start happening, through a number of testers, against newer maps, content, features etc.
So, nothing is set time-wise as a proper roadmap would show, as priorities are changing.
However, the ETA is still set to Q3 2024, which might move slightly towards the end of it or Q4 2024, but nevertheless 2024.
Where is the save location in Linux?
Just fired up my
Linux Mint and it seems it was found under
/home/vlzvl/.local/share/Steam/steamapps/common/The Darkness Below
You can also get to the local files from Steam through:
Steam Library -> Right click on game -> Manage -> Browse local files
However, there's no need for that as I found the issue.
It seems the Linux binary isn't behaving correctly against the build type on last version, meaning:
- not showing the introductory message when entering the "Silkmoor" (you can check that quickly with 4 prebuild characters)
- not showing the ending message on "Tomb of the Dreamer"
Which is not something terribly missed though, as the game basically ends there, there's no more content on "Prelude" build.
It was also a busy update and something messed up on linux (windows binary is fine).
I just build quickly a linux binary with "prelude" build type and tested again on my steam linux mint version, on last update, which shown the
introductory message this time on "Silkmoor", which means it respected the build type this time and I believe it will do the same on "Tomb of the Dreamer".
Added a note to double check that thing when I upload the next update, but it seems the wrong build made it to Linux, instead of the "Prelude" one, which caused these two (2) event messages to not be shown / handled correctly.
Thanks for your efforts on this one