Currently, while rules can be copied and pasted between experiences in Game Maker, presets cannot be transferred across different experiences. This limitation significantly reduces the efficiency of creating new experiences.
The issue appears to be related to NFT asset restrictions. However, logic assets are not bound by such limitations and can be shared universally. Therefore, enabling the ability to copy and use presets only for logic assets would be a practical and valuable update.
By allowing logic-based presets to be shared across experiences, creators can dramatically reduce repetitive work and instead focus on enhancing the quality and creativity of each experience. This would be a meaningful step toward improving the workflow and overall productivity of experience builders.
Thank you for the idea. While I am not a creator, this seems to me very intuitive and valuable to speed up experience development. Do you think this would represent significant amount of development work that would require a SIP proposal or is this a quick win that TSB developpers could include in their map on the fly?
Tagging @theKuntaMC and @Cyril in case this can be brought to the dev team.
Great idea, should be simple enough to execute on and could add a ton of efficiency.
The issue appears to be related to NFT asset restrictions.
Even in these cases, it seems like you should still allow people to use presets, they just shouldn’t be able to publish if they don’t have multiple copies. IMO you don’t necessarily have to restrict this to just logic assets.
@shont It would also be super helpful if you could provide an example of a type of preset that you would want to use across multiple games, that you can’t get simply from copy pasting rules in the rules system.
Definitely something that would speed up development a lot. I would love to see more work on the preset system. Enabling the sharing of presets across experiences would be huge, maybe within the same account.
I remember the last time I transferred an experience to another account, the preset threw an error due to missing assets or asset ownership issues.
That being said, if we enable preset sharing, we will need to handle the asset problem during transfers.
I can see why this feature is not available at the moment. If you limit it to logic assets, then if you copy and send it (along with the preset list), there shouldn’t be a problem.
I am personally unclear of the technical challenges this might require.
I did just move this post from General to SIP: Ideas, though, as that’s where an idea like this should start.
If during the course of discussion, it is deemed an easy fix by devs, it may still be best that it is advanced as a SIP, so that we work through the process and put a formal request in front of the dev team.
Other examples of bypassing the SIP process might include an idea that would be pulled from the operations budget (which this idea does not fall into).
This sounds like it could be another feature request. A lot of us were talking about making the next feature request come with a funded amount to hire a freelancer to help TSB product team instead of putting it solely on them.
General
SIP: Ideas