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
fastgmad publish
errors after "preparing config" (Steam error: "a file was not found")
#1
Comments
Also, just as a sanity check, I checked to see if gmod's |
Damn that sucks, I'm guessing that Steamworks doesn't understand symlinks on Unix. Works fine on Windows. I'll have to disable that for Unix builds |
Give v0.1.2 a try |
The same issue occurs. I don't believe symlinks were the culprit anyway; I'm creating and publishing the .gma from a local git repo, and I do symlink the relevant addon folder in that repo into the GarrysMod addons/ folder, though I don't believe that should be affecting anything--I also use the original path, not the symlink, for gmpublish. If you want to test the exact same addon I've been trying for reproducibility, you can find it here on GitHub: chev2/gmod-addons
|
Fixed in next update |
Here is my console log:
Seems like it gets something wrong at 'preparing config'.
For reference, I use this command to pack a folder to a .gma:
fastgmad create -folder "addons/auto_flashlight" -out auto_flashlight.gma
The folder is structured like this, which I believe shouldn't cause any issues:
addons/auto_flashlight/lua/autorun/...
addons/auto_flashlight/addon.json
The addon only contains 1 Lua file and the addon.json:
Also, I'm able to use
fastgmad update
to update the addon without any errors being printed in fastgmad, however this doesn't seem to actually fix the addon as attempting to download the workshop addon via gmpublisher results in an error, and the displayed file size on the page still says0.000 MB
.OS:
EndeavourOS Linux x86_64 (kernel 6.1.52-1-lts)
Shell (not sure if this matters but I'll put it here anyway):
bash 5.1.16
fastgmad version:
0.1.1
The text was updated successfully, but these errors were encountered: