i cannot believe it. pygame in a browser! the drea- oh, wait it uses async‽ guess i'll have a reason why i have to learn that now, lol.
faceofkitten
Recent community posts
in Unity games the executable is often not set to be allowed to execute. i don't know whether that's Unity's or the author's system fault.
anyway, this solution works for all Unity games where the author didn't bother (or know how) making sure that anyone can run it.
- most graphical file managers support setting executableness of files.
1. browse towards the game's directory
2. right click "NSaFN0.4Linuxpublic.x86_64" and open the file's properties.
3. find and toggle the executable setting. (sometimes it's called differently. e.g. in Thunar it's in the "Permissions" tab and is called "Allow this file to run as a program".)
4. run by double or single click (depends on your file manager).
- the universal way from terminal:
1. open a terminal emulator and cd to the game's directory
2. call "chmod +x NSaFN0.4Linuxpublic.x86_64"
3. run from terminal by calling "./NSaFN0.4Linuxpublic.x86_64"
the Linux build is broken on my desktop. it just scrolls to the left on its own and doesn't take any input. i managed to manually set it to windowed but that didn't help. it's weird that the touch input button things are displayed even if i only a keyboard and mouse connected.
it works on my laptop (with touchscreen).
looking good. but the engine has a few annoying flaws. (Linux build)
trying to push buttons on the wall is a pixel hunt. when the reticle points at a button, it should be able to be pressed.
when turning around (by mouse) too many times, it doesn't turn much more. i can only assume that it happens because the pointer position doesn't get reset and once it reaches the edge of the screen the game doesn't receive any more inputs.
edit: indeed, i have noticed/read the disclaimer only after writing this.
i think this is Unity's fault. it doesn't set the x-bit on the executable, which would tell the system that it's okay to execute the file.
if you haven't already, extract the archive.
most gui file managers have an interface for the read-/write-/executeable bits in the file's properties dialog, which is probably reachable by rightclicking the file. the two i have installed (Thunar & Pcmanfm) have a "Permissions" tab. there should be a checkbox or a some other gui element about execution or execute.
the ultimate solution for any Linux distribution: open the directory in a terminal emulator and run "chmod +x NSaFN*.x86_64". ('*' wildcard so it's valid for future versions.)
no. it happens even after failing the task while going to bed. maybe it's related to the potatoness of my 10y/o chrome book.
the transitions are not consistent in the order of fade to black and room switching. but when the bug happens it always switches the room first before fading to black before switching back to the starting room.
it seems to be completely random where it happens. i did manage to explore the whole place once and don't remember the bed rooms bugging out ever.
i fear my computer is too slow for transporting the plant ooze. but i've found a warp glitch while clenching in the woods. and found myself at the home of the coyotes. i thought this time i had it too... poor Rascal, having to go back to the plants for thirds? fourth? maye he should have taken some tallies.
and of course my save was overwritten, too. T_T
edit: the solution is to not just mash space as fast possible, but do it in a rhythm.
button mashing is and has always been the worst possible game mechanic.