playcanvas / playcanvas/editor

Add the ability to overwrite sprite assets in the Sprite Editor while keeping references (multipack)

Open
#142 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: publishing enhancement
Dominant language
TypeScript
Stars
1.3k
Forks
215
Avg merge
1d 29m
Merged PRs (30d)
30

Description

I would like to be able to update sprites in my Playcanvas project using Texture packer with "Multipack" turned on. (to export a series of atlases rather than one)
And for Playcanvas to replace the sprites currently named the same, that are already in the project. (Specifically for UI work)

Currently, all of the sprites get jumbled up if Texture packer reshuffles the items across the atlases.
Even being able to replace sprites in a folder with new ones of the same name (and they will in turn update in the scenes) would help.

As a dev, I don't want to re-update all of the sprites manually when I am sent new assets from the designers.
It's very common for all assets to be split over a fair few atlases.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing a Texture Packer import with Multipack enabled in the Sprite Editor and inspect how sprites are assigned across atlases. Trace how same-named sprites are replaced and how scene references are maintained; done means reshuffled multipack assets update existing sprites without manual scene re-linking.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.