Closed Erokaution closed 1 year ago
Does love.filesystem.write
works? If so then there's nothing to worry about. love.filesystem.isSymlink
is relative to the save directory and game directory.
Does
love.filesystem.write
works? If so then there's nothing to worry about.love.filesystem.isSymlink
is relative to the save directory and game directory.
outputs..
Do note I'm not actually working on any love2d project. I've never touched love2d before now, and I'm only testing this because a game wasn't working and I was trying to find out why, and this appears to be a engine issue and not a individual game issue from what I can see (which i obviously could be wrong).
With this said, if there's anything I can do to give a clearer idea on what's going on, let me know.
I assume your t.identity
is set correctly, so this appears to be PhysFS bug (library that love.filesystem
uses under the hood).
With issue #1880, the reporter deduced that löve versions prior to the as of now unreleased 12.0 has a PhysFS bug that caused their symlink related issue; not sure if this is the same problem or not though.
Oh right. Looks like it's duplicate of #1880 indeed except it's in Windows instead of Linux.
I'm under a Windows 10 environment. I have my %appdata%\Roaming folder as a symlink to a different drive. Here's a image showing a commandline print of 'dir /a', which shows the Roaming folder being a Symlink.
With this said, love.filesystem.getAppdataDirectory() locates to "C:/Users/Athetia/AppData/Roaming". Moreover, love.filesystem.isSymlink(love.filesystem.getAppdataDirectory()) returns false. It appears that love2d is not seeing the Roaming folder as being a symlink. Attempting to do any file operations on my main Windows user account fails. I am assuming it's because love2d is attempting to load from a appdata folder that doesn't exist at the specific location it's expecting.,