Question for you. So my company has been using PlayCanvas for a couple years now (fantastic product), and we are trying to create a generic “game” with the logic flow we need.
An example: We have a generic menu system, with designers to come in later and change via parameters. So you can do things like add and remove leaderboards, instructions, link out to external weblinks for different clients, gate these feature with a lead generation component, swap 2D assets, etc etc.
Inside of this generic logic, there will be different minigames. And then inside of those different minigames there is an arbitrary number of different skins of that game.
So, how would you all go about setting this up? In the past I have made a fork between the top and middle layers with branches for the different skins inside a game. But Ideally I would like to be able to make changes at the top layer and have them propagate down into the bottom layers. For example lets say I want the user to have a two second delay when they submit in the leaderboard. I’d like that option to pop up at the bottom layer when a designer is exporting a skin of a game.
Let me know what you think. I know this is all pretty high level, and I honestly may be thinking of this wrong in general. Open to any and all thoughts. Thanks in advance.
TLDR, a single project workflow, you have the top level as master, games as branches and then skins as branches of the game branches.
This allows you to upstream changes as branch merges.
This is not a great solution as it has all your games in one project hence the recommendation of archiving the game branches on a regular basis in that ticket.
You’re right it is also scenes and templates. I think if the project linking is something you are planning on doing, we can probably get by on a boiler plate system until that feature comes out. If there is ever a beta release, we’d love to give it a shot.
So would the project linking system you’re working on essentially have a project be my top layer, and then different projects that are linked to the parent project with the skins being branches of the child project? Then making a change on the top layer project, would propagate down?
Pretty much. Each game project would link to the core project and changes to the core project can be upstreamed to the games. For the skins, you can use branches or I think they could also be separate projects that are linked to the game project. Changes to the game project can be upstreamed to the skins.
The ‘linking’ would effective be a cross project merge.
Okay great I’ll wait for that then. While I’ve got you on that topic (im sure this is being considered somewhere internally) it would be great to have folders with projects on my account. I think my “Projects” screen is already a bit crowded so I can only imagine how it would be in this scenario.
@yaustar Have there been any updates on the project linking? I haven’t seen any movement on the github issue. I’ll hold off on asking again after this, but I’m at a fork in the road with a project where I’m trying to decide if I should wait for the feature or go ahead without it.
Thank yall for the responses. I think I’ll go ahead without it for now but if there is anyway I can help (beta tester etc.) please let me know. Really looking forward to the feature
