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

Allow to swap assets of any object type #7365

Merged
merged 3 commits into from
Feb 4, 2025
Merged

Allow to swap assets of any object type #7365

merged 3 commits into from
Feb 4, 2025

Conversation

D8H
Copy link
Collaborator

@D8H D8H commented Feb 3, 2025

Following steps

  • Check in quick customizable templates if more objects must be hidden.

@D8H D8H marked this pull request as ready for review February 3, 2025 16:19
@D8H D8H requested a review from 4ian as a code owner February 3, 2025 16:19
let smartObjectsCount = 0;
for (const type in assetPack.content) {
const assetCount = assetPack.content[type];
if (!sortedContentType.includes(type)) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It feels a bit light as a check to decide if the object is a smart object. If we add 3D particle emitters or 3D cubes in a pack, it will display them as a smart objects.

Copy link
Collaborator Author

@D8H D8H Feb 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If smart objects mean an object with some logic, it's the case for any object so I think it's not a big deal.
We can add lines for more objects in the future if we think it becomes useful.
I see it as a "others" category but less boring.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But it's quite deceptive when users purchase something and they end up with boring objects.

Copy link
Collaborator Author

@D8H D8H Feb 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no easy way to know if an object comes from engine or an event-based extension. And even in this case, the limit is blurry because the 3D particle emitter is from an event-based extension and it may not fit everyone definition of "smart object".
I think when there are new cases, we can add specific lines for them.
The choice of words:

  • "smart object" avoids diminishing the appeal for asset packs with custom objects (which is an actual use-case)
  • "other" avoids the risk of mislabeling new objects (which rarely happens, is only a bug that can be fixed easily)

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Smart objects is probably fine. If some are becoming super "well known", we'll add specific names for them in the future.

@D8H D8H merged commit 8c98239 into master Feb 4, 2025
5 of 6 checks passed
@D8H D8H deleted the asset-swap branch February 4, 2025 16:22
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

Successfully merging this pull request may close these issues.

3 participants