-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A more comprehensive description of tools setup would be appreciated #93
Comments
Dear Chris,
Thank you for your reply. I had missed the popped-up drop-down menu when selecting protontricks. After realising this and selecting flatpack, both Pandora and Bodyslide work without any problem. It doesn’t seem to matter what the working directory is for bodyslide, both the ‘data’ folder as well as the ‘/Calientetools/bodyslide’ folder work.
I have actually no other deployer set up than the ones in the wiki. So no reverse deployment. Despite this, Pandora and Bodyslide find the relevant mods just fine. They work flawlessly as far as I can tell but I still have a lot of testing to do.
I want to thank you for this awesome mod manager. The deployers and the root level require some thinking, and some mods need manual adjustment of the staging folders. But that aside, it works fantastic. And miles better (and faster!) than MO2 and Vortex, at least on the Steam Deck.
I hope you keep developing this tool. It is awesome.
Many kind regards,
Martin
Op 29 dec 2024 om 00:05 heeft Chris ***@***.***> het volgende geschreven:
The wiki currently lacks information about newer features like reverse deployers. I will add chapters for those in the future.
Probably the best way to set up a reverse deployer for Skyrim is to set the target directory to the same directory your Bin deployer points to (the one containing SkyrimSE.exe). Make sure to enable Use ignore list to exclude all vanilla files.
As for tools: It's usually best to set the mode to Guided and runtime to Wine. Then use the directory containing the tool's executable as working directory and simple enter the name of the executable into the Tool executable field. Here is a example for Nemesis:
tool_setup.png (view on web)<https://github.com/user-attachments/assets/2e26e5c7-0bb8-4786-9c57-66b5fa0070f5>
Not sure what causes the permission issues. Are you using the Flatpak version of Limo? If so: Make sure Limo can talk to org.freedesktop.Flatpak. This should always be the case unless you changed it manually.
—
Reply to this email directly, view it on GitHub<#93 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLQZ7Z2KJUQVR5IWJGPRIOD2H4VDDAVCNFSM6AAAAABUJGYG56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGU2TEMZWG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear persons in the know,
the wiki gives a good explanation on how to start modding with Limo. So far I've installed a few mods and it works! Now I want to setup some tools such as bodyslide and Pandora. But I can't get it to work: when choosing native runtime it reports 'permission denied', and it can't seem to start Wine either. Moreover, what deployer needs to be chosen and which working directory for the reverse deployer? It would be great if this could be added to the wiki as well. Thanks in advance!
The text was updated successfully, but these errors were encountered: