Descriptive Problem Summary:
If any part of a path targeted by flist() contains certain characters (such as an accented é) it will fail to return the contents of the path.
I've not tested all other file-related operations, but was surprised to see fcopy() and fexists() seemed to function correctly even when flist() failed.
Numbered Steps to Reproduce Problem:
1: Place game's folder in a path containing an (é).
2: Run game that would try to use flist() to access files within its own directory.
3: No files get detected.
-1: Place game's folder in any path that only contains normal letters.
-2: Run the game.
-3: Files get detected as expected!
flist("savefiles/") would return all my save files stored in a folder named "savefiles" when the game is run in any directory.
flist("savefiles/") only returns my save files if I run the game in a directory that only contains regular characters.
Does the problem occur:
Every time? Or how often?
All the time.
In other games?
I've isolated it to the flist() call itself in a fresh environment so yes.
In other user accounts?
Yes assuming it's still running on a path containing applicable special characters.
On other computers?
Unable to test.
When does the problem NOT occur?
When you target flist() at a path that contains only regular characters.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
It was working on this computer a few years ago without issue in a directory containing an é, and had a project that could use flist() successfully that now cannot function when run in the same directory. I'm uninterested in testing every version that's come out in the last few years to find out which it was.
Run the game from any directory that doesn't contain applicable special characters. -which is pretty annoying for people who foolishly made a user account containing an é.
Nov 28 2020, 4:10 pm