Ashley's Forum Posts

  • It's out of the question to change the default since it would be a wide-ranging breaking change.

    Further, I think this is more complicated than stated - there is currently no UI to arrange the order, and there is also the question of if an object belongs to multiple families, what is the ordering between families? There is no way to arrange that order either, and I'm not sure how that could even be managed in the editor.

    Another option is to use all the effects on the object instead of the family, if that can be workable.

  • We can't go back to exactly what it used to do. The old approach was simply broken, and people kept running in to the brokenness, and ending up making forum posts, filing issues and contacting support.

    Previous Construct releases are still available - which is specifically done for cases like this where there is some kind of unexpected issue. So if you go back to r197.2 you can carry on using it like it was before, at least in the short term while we figure out what to do about this.

    Considering a permanent change will cause permanent confusion, even years down the line, I would still prefer to use a workaround if one is feasible. That should only cause temporary disruption, and then should be a non-issue years down the line. So before taking any further action it would be useful to know: can you use keytool to rename a key password and continue publishing? Once you have the tool, it should only be one or two lines per keystore - not a lot of work at all.

  • Sorry, deprecated plugins are on track to be removed, and we specifically don't want new uses of them, since it will make it harder and more disruptive when we come to remove it.

  • Hmm, interesting to know, thanks. I wish smart TVs updated their software more recently. My LG TV still runs Chrome 38, which is about 6 years old now...

  • Can you try using keytool to change the key password? I would really prefer to avoid having to change the UI back - we got lots of constant confused users previously, and adding to the support burden really makes a difference to us as a small company with limited resources. I'm sorry for the inconvenience but I'd prefer to try to find any kind of feasible workaround first before we go and change back the Construct UI and end up confusing everyone going through key signing again.

  • As for your question, I don't need C2 runtime, it's my employer who does :)

    Out of curiosity, what's their reasoning for this? As noted we intend to retire that next year.

  • Before taking any action, it would be useful to establish if you can indeed use a new keystore, since that would be a straightforward workaround and not require any further (and potentially confusing) changes to Construct.

  • The problem we have is the build tool was (it seems) updated to ignore the key password when creating keystores. So people kept entering a key password when creating a keystore, which was ignored, then re-entered it when signing the app, and then getting "wrong password" errors. This change was in the beta release for about a month before it came to a stable release, which gave the impression the change was OK.

    If we add back a key password field just for signing, we'll be asking people to enter a password they never previously specified, which would probably cause further confusion.

    So it's not clear to me what to do here, it seems this change to the build tool has thrown a spanner in the works. AFAIK whether or not you can change the keystore depends on the precise method you use for publishing, and in some cases I think you can change it. Otherwise you can try downloading the Java keytool and changing the key password on the keystore - it needs to match the keystore password, since the build tool now only supports both the keystore and key passwords being the same.

  • Can you create a new key store?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The build tool was actually ignoring the key password field, which was causing problems. So we removed it.

  • You do not have permission to view this post

  • You can rename .c3p files to .zip and extract the project files, add any missing files, then zip it back up and rename back to .c3p.

    This should never happen in the first place though - if it's an editor bug and you can identify how it happens it would be a high priority to fix it.

  • It's not clear from just that. You'd have to ask them for more details.

  • The Construct 3 runtime requires WebGL. It's supported everywhere now. So it always works.

  • Both those modes use identical code, so I don't know why there would be any difference.