Ashley's Forum Posts

  • 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.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • 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?

  • 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.

  • That error is nothing to do with Cloud Save. (It's a false positive and totally harmless.)

    It's difficult to help without knowing what the real problem is.

  • I'd also point out that if it loads very quickly, it is correct that it would only be set to the value 1, since it will have finished loading before you read the value for the first time.

  • I'm not sure what you're after regarding Z order. Construct has various features to control Z order, such as send to front/back, order relative to another object, and sorting Z order by things like instance variables. Which would be relevant to your addon?

    AFAIK the Addon SDK docs are up-to-date so if they don't cover something it would need to be added.