2022s
Preventing duplicate assets in Crayta packages
Nov 11, 2022When publishing packages on Crayta, you will undoubtably run into a situation where assets from a package dependency are ending up in your own package.
Avoiding this is fairly simple, if you know what to look for.
The key to avoiding this is to ensure you haven’t modified any of the package dependencies before publishing your package. This goes for creating and updating a package.
To quickly tell if you’ve modified a package dependency:
- Go to the package publish/update screen
- Right click the top element and click “Remove”, followed by “Cancel”
- This will reveal the status icons in your asset list
Next, click on the two checkboxes at the bottom of the dialog to display all assets
Your screen should look something like this
These icons indicate files you own have changed:
These icons indicates files from a package have changed:
At this point, if I published this package, I would end up with duplicates of questScript and userQuestsScript.
Since these assets come from the Quest System package, and I’m also the author, the solution is to update the Quest System package first. This will “commit” the modifications to the Quest System package, and they will no longer be considered modified by the crayta packaging system.
If you do not own the modified package, you have 2 options:
Revert the changes to the package dependencies. It’s possible you simply opened a file by accident, and that’s enough for crayta to believe its been modified. To revert, simply right click the asset right in the package window and click on “Revert”
The other option is that you’ve intentionally modified a package dependency. Maybe you’ve extended a package with custom functionality. In that case, you do want to include the new script in your package. You will need to be very clear in your package guide that the user must use your customized version of the script, rather than the version from the dependency package.
Rails credentials coming up empty
Apr 13, 2022Ran into a problem today where trying to edit rails credentails with rails credential:edit was bringing up an empty editor window. The credentials themselves were fine, I could read them with rails credentials:show, but the editor itself was blank.
On top of that, even though the command line was telling me that my credentials were saved, nothing seemed to be changing about the file.
Turns out that windows still supports a legacy file format called 8.3. The result is that a long file path can container a ~ character. A change was made to rails back in July 2021 to escape spaces in paths. That same code is also escaping the ~ character.
So a once innocuous path of C:\users\Josh~1\AppData\... became C:\users\Josh\~1\AppData\.... Obviously the resulting path doesn’t exist, so the editor was bringing up a new file!
A quick patch to rails to expand 8.3 filenames fixes the problem.