rojo-rbx / tarmac Goto Github PK

The underlying architecture of Tarmac's packing does support configurable padding sizes, it just isn't exposed to the user. Currently, spritesheets are padded with a single pixel.

Adding another optional config, spritesheet_padding_size, would allow the user to modify that value in their tarmac.toml.

This is relevant because I am experiencing frustrating sprite bleeding in some cases, and adding a touch more padding would presumably hide the problem.

1. Open https://github.com/rojo-rbx/tarmac/tree/main/examples/02-spritesheets
2. Delete tarmac-manifest.toml
3. tarmac sync --target local
4. Observe examples/02-spritesheets/pack-these/init.lua
5. tarmac sync --target local
6. Observe examples/02-spritesheets/pack-these/init.lua

It's now just

return {
}

Currently tarmac fails to upload any decals. Uploading will give a Roblox server API error:

[ERROR] Roblox API returned HTTP 500 Internal Server Error with body: The page cannot be displayed because an internal server error has occurred.

(returned when running tarmac sync --target roblox)

It seems that codegen behavior had changed at some point, without being documented. Even with codegen explicitly set as false, Tarmac adds .lua files for each image file upon sync (even with --target none), without requesting it. We have our own codegen format that reads directly from tarmac-manifest.toml at compile-time, so this is completely useless for us.

I've attached a screenshot of this behavior, with our current configuration.

Everytime I use tarmac it always gets uploaded under my personal account and not the specified group.

.toml file

name = "BV-Images"
upload-to-group-id = GROUP_ID #group link is valid, just don't wanna post my group link here
asset-cache-path = "cached-images"

[[inputs]]
glob = "images/**/*.png"
codegen = true
codegen-path = "images.lua"
codegen-base-path = "images"

Error Message:

Right now Tarmac is lacking a way to support for the new cloud API, supporting this may allow us to incorporate managing other asset types as well.

My fork had this pull request, it still needs work to incorporate into the project, however. Could perhaps instead use rbxcloud to simplify our internals around Cloud API a bit?

Main functionalities user-side should be:

• It should allow passing API key directly via --api-key argument in the CLI
• It should also allow using environment variable - perhaps TARMAC_API_KEY?
• If an API key is provided or present; use Open Cloud API for uploads otherwise fallback on cookies.