Skip to content
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

texture-packer: Handle different exporters #53

Open
sylvainpolletvillard opened this issue Jan 20, 2024 · 0 comments
Open

texture-packer: Handle different exporters #53

sylvainpolletvillard opened this issue Jan 20, 2024 · 0 comments

Comments

@sylvainpolletvillard
Copy link

So assetpack is great and I'm very thankful to the Pixi team for working on this.

Currently, the texture-packer plugin use Pixi exporter:

function pixiTexturePacker(options) {
    return texturePacker({
        ...options,
        texturePacker: {
            ...options?.texturePacker,
            exporter: 'Pixi',
        },
    });
}

which makes sense since Pixi made assetpack.
But unfortunately, I use Phaser 3 for my project and Phaser and Pixi use a different format for JSON texture atlas.

The texturepacker plugin code has some code that expects the Pixi exporter and cause exceptions when using another exporter, despite free-tex-packer-core allowing several exporters to be used.

So my question is: would you consider making this tool work for other exporters format than Pixi's one ? Or is it out of the scope of this project ?

If yes, I'll do my best to provide a PR that enables support for Phaser 3 exporter. If not, I'll fork this project and won't annoy you anymore. Thanks for reading ☺

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant