ZeldaVerde's Forum Posts

  • I'm not concerned about layout exclusions though, fwiw.

    That was just an alternative for getting the same results of a "template layer" but going by Ashley's "name-based" proposal.

    yea it can get complex, though a layer can not be a template/replica and global layer at the same time imo.

    Yes, it would make no sense. That is a non-issue.

    I don't get the claims of it being overcomplicated—it's just an "extension" of global layers with slightly altered functionality (remove instances carrying over from the master layer, and allow unique instances on non-master layers). So much of it is already there, you know?

    Maybe they didn't get what we want yet? I feel the same.

    I don't want to be rude and I obviously don't know their code base. But it is global layers that don't share objects, a feature that already exists but excluding part of it.

    I really don't want to underestimate complexity here but can't you "basically" just change the drop down menu where you typically select "yes" for "global" to be like "type": ("regular" or "global" or "template") where "template" is the EXACT same code you already have for globals BUT with the object syncing part deleted?

    The nesting part Diego mentioned would not be a problem because it would be exactly as it already is, and switching between those types would also do exactly what id does today for globals.

    Again, Ashley and Diego, you've always been very nice to me and I really don't want to be rude.

  • Imo the most robust and flexible way would be fairly similar to how objectType templates work: you can set something as a template layer and you can set another layer as a replica of it (could just be that any aditional layer with the same name is a replica), then on that replica you can disable copying of specific properties, effects and for a more completete came maybe we could even choose if sub-layers and content should be copied (in that case it could supersede global layers).

    The exact meaning of "first layer with the name" scares me in the context of existing projects if they go with that.

  • Well, first of, thank you once again.

    Second of, the version without the specific UI is already much better than what we have. If you think it would come much sooner, I'd rather have that and work around the limitations myself by renaming layers.

    If that is the case, just please do consider adding the ability to select layouts later on.

  • Can we get an update on this? Is this feature coming or not? I know it may take a while but I'd just like to know if it is at all coming. Thanks.

  • It would be great to copy and paste an entire layer from one layout to another. Or when copying a bunch of sprites on one layout, being able to paste them on another layout and have them keep the same layer.

    I assume you mean copying a layer without its object instances?

    Yes to both, which also reminds me about the issue where creating objects with a hierarchy from templates does not create all children in the correct layers, which was said not to have been solved before because there was no guarantee two layouts would have the same layer structure. So maybe if Ashley actually adds what we are talking about here and depending on how he does so, we could also have that.

    But also, you and I are now a bit off topic and this should probably be a different discussion.

  • In general, yes. But can we, instead of going only by names, have an option to select to which layouts we want that to apply? Cause like, we may want to change the "Background" layer of all game level layouts but not of a menu layout that may also have a layer named the same.

    Also, please note that a very important part of this is that we want them to share properties (inspector properties and effects), so please do include that.

    And please, with all due respect, and I do respect you a lot, try acknowledging that this is very very very needed and not just some niche thing we are requesting.

    Thanks as always Ashley.

    Edit: just realized there is no good way to figure out where a new layer should go in the layer order of all layouts it was also created in, as they may even have a different number of layers. Can we maybe just make a family or something of layouts and we get all the layer structure and settings to sync from a template layout to all replicas?

  • The problem is that the layers content needs to be different, it cannot be shared:

    i.e. on level 1 there are mountains on the background layer and on level 2 there are clouds.

    But you still want a shared layer setup that is consisten across levels, like [postProcessing, foreground1, foreground 2, world, player, enemies, background1, background 2]. Now after creating 100 levels and noticing you need to make some change to that layer set-up you need to repeat it 100 times.

    Exactly. That is what I meant, Ashley. Global layers are great but what we want here is global layer structure and settings, not global layers.

    Edit: Another way to say it is: We want global layers but that don't share object instances. Can you "just" make it an option to have global layers do exactly all they already do but share objects?

  • So I'm making a game where each layout is a different level. Obviously, as the game logic is the same for any level and so is the artstyle, all levels have the exact same layer structure. But then, whenever I want to change anything about these layers or add a new one, I have to do that to all my level layouts, which are ever increasing in number.

    It goes without saying that this is very error prone. Is there a way to have something kind of like in between regular layers and global layers where settings, effects and whatnot are the same but objects aren't, or really anything else that would fulfill that need of mine?

    Thanks.

    Tagged:

  • It was the extensions. Thanks as always Ashley and sorry for bothering you with such a rookie mistake.

  • While using the script as demonstrated in the example given on the Audio scripting reference page, I get this:

    What am I doing wrong?

    Thanks in advance.

    Tagged:

  • Oh, so now they work just like event sheets do, which I didn't realize. So sorry for that and thank you so much as always.

    Edit: Now that I think of it, I think this was because of the way I replaced the main script when creating the new project. After setting the main script, we are back to the same error that started this thread. So no, the "weird typescript setup" wasn't the problem.

  • Oh ye, makes sense. Thanks.

  • It is exactly the same error, but here you go: drive.google.com/file/d/1b-xocb2KfHf4UnULT8djQ7MeogYRCdWQ/view

    Do you also get the same error on your end? It seems like something related to my browser to me, idk.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • So, I've created a new project. It won't give me errors anymore but now runOnStartup() just isn't called... What?

    Edit: It all appears to still come down to that "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR".

  • Am I dumb or is there no javascript gamepad plugin implementation done yet?