Best way to manage assets in a team-based Roblox project?

Help and Feedback Platform Usage Support
1

Hello all!

I’ve been struggling with a workflow issue involving me and my team.

We use a Rojo + Git workflow for version control, which has been a great fit for us. Each programmer works on their own feature in a separate branch, and merging + resolving conflicts is usually straightforward.

But the real pain point is:

Managing Assets

Each programmer works with their own local Place File—just like a local Git repo. When building different features, devs often need to bring in assets to test or complete their work.

The problem comes when it’s time to merge. Asset management becomes the biggest headache.

We end up spending a ton of time:

  • Tracking down which developer has which assets
  • Manually copying, importing, or replicating parts
  • Rebuilding scenes or setups just to get feature parity

It’s not that it’s impossible, just frustrating and tedious—especially with multiple devs contributing at once.

Is there a better way to handle asset management across developers?

Is there a tool, plugin, package,or even Roblox-native solution that I was blind to that helps with this?

For context:

  • We’re using rbx-ts (TypeScript → Luau compiler)
  • Assets are primarily used for testing + final integration
1 Like
2

Maybe use packages need to have good control to not overwrite it

3

1. Treat assets separately from code.

  • Scripts = Rojo + Git.
  • Assets = managed outside of Rojo’s syncing whenever possible.
  • Keep your .rbxl place files or .rbxlx light, only for asset importing/staging.

2. Use Roblox’s “Packages” (native tool).

  • One person creates or updates the asset.
  • Publishes the update.
  • Everyone else just updates the package in their Studio!
    No manual copy-paste, no hunting down assets.

Downsides:

  • Needs some discipline (“remember to publish the package when done”).
  • Minor Roblox bugs happen sometimes (but overall it works well).

In your case:
Create a shared “Assets” place or game where packages are stored and synced!

3. Create a dedicated “Asset Repo” (secondary Git repo or Studio place).

  • Have a second GitHub repo only for asset .rbxm files.
  • OR, make a “SharedAssets” Roblox place that’s only for models, GUIs, etc.
  • Devs pull from this shared place regularly, just like syncing code.
  • Less chance of place file conflicts.

4. Use external asset versioning plugins (optional).
There are some community tools like:

These aren’t as popular yet but some teams use them for automated asset importing/exporting into Git-friendly formats.

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.