I know why quest.txt isn't properly saved (thus why your character progress isn't properly saved).
It seems that the quest.txt is saved to "mp_import" instead of "import". This I think is due to vfs_append() uses stdio instead of physFS and thus doesn't translate the mount point properly.
I can't make heads or tails of Egoboo's filesystem so I haven't been able to fix this crucial yet small bug.
The quest.txt bug
Moderator: Developers
- Seth
- Chest Mimic (Community member)
- Posts: 150
- Joined: Wed Aug 11, 2010 11:05 pm
- Location: U.S.A.
- Contact:
Re: The quest.txt bug
Could you please say what “stdio” is for?
Why can't you make “heads or tails” of it? Is this something you have never seen before, or is it just confusing in this instance?Zefz wrote:I can't make heads or tails of Egoboo's filesystem so I haven't been able to fix this crucial yet small bug.
- Zefz
- Squirrel Knight (Administrator)
- Posts: 3820
- Joined: Wed Jul 23, 2008 1:27 am
- Location: Norway
- Contact:
stdio is a input/output library for C which uses different way than PhysFS to read a file.
I mean that Egoboo's implementation of PhysFS is kinda complicated and isn't very intuitive in my opinion. I know where the problem is and what needs to be done to fix it. It's the exact how that I haven't figured out
I mean that Egoboo's implementation of PhysFS is kinda complicated and isn't very intuitive in my opinion. I know where the problem is and what needs to be done to fix it. It's the exact how that I haven't figured out
-
- {]-[0{0|307 (Developer)
- Posts: 1864
- Joined: Wed Jul 23, 2008 4:22 am
- Location: Minnesota, USA
The problem with the wrapper for physfs is with the way it adds and removes virtual paths, how the paths are expanded when you try to get a real directory name, and some minor notation problems having to do with beginning a path with a '/'...
Really, I felt that it might be easier to roll my own code at some point!
Really, I felt that it might be easier to roll my own code at some point!