32 Replies
Solution
The game path should be
C:\SteamLibrary\steamapps\common\SatisfactoryOh, I think I see my mistake
I put that path but added FactoryGame at the end
Now it says build successful but it exited with code 1, could it be because my Steam wasn't open? Seeing it has auto started its daily update
Log would tell
The packaging fails but it does launch Satisfactory and I can see my mod listed by SML so that's weird
Hmmm, if you disable launching, does it still fail?
>add crash AlpakitInvalidCopyDestination
What should the logs match (regex)?
Invalid.game.directory.specified.for.CopyToGameDirectory.{0,50}FactoryGame
What should the response be?
Make sure your Alpakit CopyToGameDirectory points to the root install directory and not the FactoryGame subfolder
Known crash 'alpakitinvalidcopydestination' added!
Invalid game directory specified for CopyToGameDirectory: C:\SteamLibrary\steamapps\common\Satisfactory\FactoryGame
Make sure your Alpakit CopyToGameDirectory points to the root install directory and not the FactoryGame subfolder
-# Responding to
alpakitinvalidcopydestination triggered by @Robb (Now™)It does
Huh, that is weird
My CopyToGameDirectory does point to the correct path and not to the FactoryGame subfolder anymore
Yeah, I know
Robb just told the bot a new trick, so that next time it'll auto respond 😄
Oooh got it x)
Wait it's not solved
I'm still getting an error when trying to package the mod
I don't see any errors in the most recent log file you posted, only warnings
I might be blind though
Discord doesn't display everything by default if you don't download the file, here's a screenshot of that last log file
It says
Packaging failed with ExitCode=1And I couldn't find any errors
I do see some
UnknownFunction [] in the log I don't know if that's related
A lot of them actuallyI did download the whole file to look at it yeah, the ExitCode at the end which I missed is the only indication of failure I'm familiar with
I get those too, safe to ignore
Hmm ok thanks, I hope it won't cause me issues in the future
I think if you get engine pdbs you can find out what they are but they don't matter for us
That's because you don't have the debug symbols for the editor, otherwise it'd say names. But yes, that's a warning
Ah ok I see
Well it does launch the game and my mod does show up so I guess that works for now
Maybe try restarting the editor? But yes, I can't think of anything
Didn't work, but I guess that's not really an issue anymore
Anyways, thanks a lot