Incorrect game path handling with symlinks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
My main MOULa installation is at /home/dpogue/Plasma/MOULagain/Uru Live
My local DS installation is at /home/dpogue/Plasma/DS/Local
I have set up my local DS installation such that dat and sfx are symlinks to the folders in the MOULa installation.
korman is configured to point to my local DS installation.
When I export an Age with SDL, it attempts to save files into /home/dpogue/Plasma/MOULagain/Uru Live/SDL which does not exist, instead of /home/dpogue/Plasma/DS/Local/SDL. This seems to be because at export time we do everything based off the destination of the .age file in the dat directory, and attempt to find other folders based on its parent.
I think this might work if we didn't call resolve() on the file path, since that seems to be what is unraveling my symlink.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the export-time path handling for an Age with SDL, especially where the .age destination in the dat directory is resolved. Verify whether resolving the path follows the dat symlink, then confirm that generated SDL files use the local DS installation's SDL directory rather than the MOULa installation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blender, python
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100