C3/mobile apps.

I made a ton of little language learning apps to help my daughter learn to communicate. I found that people are using the HTML versions from my website, but they want them as actual apps and they're willing to buy them. Which is great, but I made like 40 of them and now they all need to be combined in to 4 or 5 apps.

I started making them during quarantine, which was what? 4 months ago. I really don't want to spend the next 4 months recreating them and I'm wondering is there away to open the .c3p's that I want to combine all at once in C3 and then save them as 1 file.

I haven't dared try it yet because I'm afraid of ruining the .c3p files. Are there any tips? Tricks? Hints?

Thanks.

dop2000,

Oh that's amazing! Thank you.

And yes, that should go on the site - that's a great example.

C3/Mobile App.

Can I get some help thinking this through?

I am making simple language apps. In these apps the player has to put the words in order to make a sentence.

At the moment I do this by having image blocks (img1, img2 ...) and text blocks (txt1, txt2 ...)

So txt1 must cover img1 and so on and so forth. When the text blocks all cover the correct image blocks they player gets an arrow to go to the next level. It's a quick and dirty setup, but it means I am constantly resizing the img blocks to fit the words, which is a pain AND it's a hint to what comes next.

What I'd really like is away for the player to just put the words in order without the blocks behind them. Is there anyway to setup this to tell C3 that txt1 goes first and txt2 is next and txt3 is after that and keep going until they are all lined up in order?

The other problem is every sentence is a different length and the words need to be able to fit anywhere on a line (or area) so the player can put them in the wrong order - the player needs to be able to be wrong so they can figure out how to make the sentence.

Any thoughts on how to get C3 to realize txt1 is first, txt2 is second and so forth?

Thanks.

dop2000

Thank you for your reply.

I tried that just now and received this error: Failed to open project. Check it is a valid Construct 3 single-file (.c3p) project.

So I changed all the "version": "r206", to r204.2 - still no go.

Then I tried changing everything to version 20400 and r204 - and that didn't work.

Each time I deleted the old file and re-zipped it, once using Windows zip and the next using 7-Zip (using their .zip, not their .7z)

I tried it with 2 different games and each time get the same error. I feel like I'm close, but may be missing something that's obvious and right in front of me.

I'm going to take a break and try again later - see if it comes to me.

Thanks again.

—,

Thank you for your reply.

The c3p files that have been opened and saved in r206, I can't open those in the current version. Or at least I don't know how to revert those .c3p files back into something that r204 can open.

When I try to open those files I am told that they can't be opened in r204 and need to be opened in r206.

Do you know how to convert them back?

—

Mostly my panic is that there is a company that wants to include my learning apps in their program. My intent was to send them several apk demos this week. Unfortunately, like my Google Play game many of the learning apps were also opened and saved in r206 and I can't make them into apks either.

I would have never knowing used the Beta version. I don't know enough about the program to know if it's a bug or if I'm just misunderstanding what's supposed to happen. (I mean, you've seen my questions on the solid behavior lol )

Now I'm stuck waiting for r206 to become the stable version and a perspective paying customer on hold.

—,

That's the thing, I have no idea. Honestly, I'm not trying to be difficult I'm really that confused.

When I attempt to export the apk or bundle I get the error:

"Unfortunately your project failed to build. The build log is included below in case it includes any information about the problem. You may need to adjust project settings, included plugins or application signing options." And the log in in the first post

If I go to the export manager, it's not there.

Once a month I backup all my games, so I have the game from about a month ago (without all the changes I've made in the last month) I can open that in the current version of C3 (because it was never saved in r206) and I can export that without issue.

After Googling for hours I came across what I think is a bug log in github, but I don't see a solution.

So I'm stuck.

I know, bizarre isn't it? I don't get it either.

Every time I try to make the APK or a bundle I get an error log telling me it failed and no APK or Bundle file to download.

It's so frustrating. I want to update the Game on Google play. I also tried the desktop version - same issue.

At least now I've figured out it's because it's the unstable version, but why C3 opened that I have no idea.

—

Thank you for your reply.

Honestly, I have no idea if there's a bug. For all I know I'm doing something wrong because C3 possibly added a new feature and the documentation hasn't been updated, but when I posted that question I didn't get an answer. I just can't figure out how to stop it from happening.

I know I can create an APK and a bundle using the current stable version of the software, but because C3 opened as the unstable version and didn't inform me it was unstable, I now can't open my game in the stable version and I can't create an APK or bundle of my game. Which means I can't update Google play. It's so frustrating.

I have no idea why C3 opened that version. I couldn't tell you how to even get to that version.

I cannot be the only person this has happened to in the history of C3.

Do you know if there is any way of reverting my game back to the current version or am I stuck with it?

Actually 2 things, any idea how I ensure that C3 never randomly opens the unstable version? Maybe is there an unstable version blocker I need to enable in the settings? That would be keen.

Thanks again.

(And thanks for listening to my rant.)

A few days ago I opened my browser to use C3 and got some message about using r206, I just clicked Ok thinking 'If C3 wants me to update I'll update'.

Nothing warned me that it was the unstable Beta version. When you're using the unstable Beta version why isn't there a Giant Banner telling you so? Unless you look at your URL there is no way to know.

Now I can't make an apk or a bundle for Android.

I can't open the game in the current stable version C3 without getting an message telling me I must use r206 and if I open any other game it uses the unstable version automatically.

Why did I get a message prompting me to use r206?

Without recreating the entire game is there anyway to use the stable version of C3 or must I wait until r206 is stable?

When will r206 be stable?

Why isn't there a giant banner in the unstable version warning people they are using it?

Last week I was able to make both an APK and a Bundle without an issue. Today I used the same keystore document, alias and password and I get this long list of errors that I don't understand.

I did make some changes today, but nothing big.

Last week I added some plugins to C3, but those plugins aren't used in this app.

I tried creating a new keystore document as a test, but that didn't work either.

Any thoughts?

Error: Checking Java JDK and Android SDK versions

ANDROID_SDK_ROOT=~~/androidSDK (recommended setting)

ANDROID_HOME=~~/androidSDK (DEPRECATED)

Using Android SDK: ~~/androidSDK

:wrapper

BUILD SUCCESSFUL in 0s

1 actionable task: 1 executed

Subproject Path: CordovaLib

Subproject Path: app

Task :app:preBuild UP-TO-DATE

Task :app:preReleaseBuild UP-TO-DATE

Task :CordovaLib:preBuild UP-TO-DATE

Task :CordovaLib:preReleaseBuild UP-TO-DATE

Task :CordovaLib:packageReleaseRenderscript NO-SOURCE

Task :app:compileReleaseRenderscript NO-SOURCE

Task :app:generateReleaseResValues

Task :app:generateReleaseResources

Task :CordovaLib:compileReleaseRenderscript

Task :CordovaLib:generateReleaseResValues

Task :CordovaLib:generateReleaseResources

Task :CordovaLib:packageReleaseResources

Task :app:createReleaseCompatibleScreenManifests

Task :app:extractDeepLinksRelease

Task :CordovaLib:extractDeepLinksRelease

Task :CordovaLib:processReleaseManifest

Task :app:processReleaseManifest

Task :CordovaLib:compileReleaseLibraryResources

Task :CordovaLib:compileReleaseAidl NO-SOURCE

Task :CordovaLib:generateReleaseBuildConfig

Task :CordovaLib:parseReleaseLocalResources

Task :CordovaLib:generateReleaseRFile

Task :CordovaLib:javaPreCompileRelease

Task :CordovaLib:compileReleaseJavaWithJavac

Task :app:mergeReleaseResources

Task :CordovaLib:bundleLibRuntimeToJarRelease

Task :app:bundleReleaseResources

Task :app:checkReleaseDuplicateClasses

Task :app:compileReleaseAidl NO-SOURCE

Task :app:generateReleaseBuildConfig

Task :app:javaPreCompileRelease

Task :app:processReleaseResources

Task :CordovaLib:bundleLibCompileToJarRelease

Task :app:compileReleaseJavaWithJavac

Task :app:dexBuilderRelease

Task :app:desugarReleaseFileDependencies

Task :app:mergeReleaseShaders

Task :app:compileReleaseShaders NO-SOURCE

Task :app:generateReleaseAssets UP-TO-DATE

Task :CordovaLib:mergeReleaseShaders

Task :CordovaLib:compileReleaseShaders NO-SOURCE

Task :CordovaLib:generateReleaseAssets UP-TO-DATE

Task :CordovaLib:packageReleaseAssets

Task :app:mergeReleaseAssets

Task :app:mergeExtDexRelease

Task :app:processReleaseJavaRes NO-SOURCE

Task :CordovaLib:processReleaseJavaRes NO-SOURCE

Task :CordovaLib:bundleLibResRelease NO-SOURCE

Task :app:mergeReleaseJavaResource

Task :app:mergeReleaseJniLibFolders

Task :CordovaLib:mergeReleaseJniLibFolders

Task :app:mergeDexRelease

Task :app:collectReleaseDependencies

Task :app:configureReleaseDependencies

Task :app:parseReleaseIntegrityConfig

Task :CordovaLib:mergeReleaseNativeLibs

Task :CordovaLib:stripReleaseDebugSymbols NO-SOURCE

Task :CordovaLib:copyReleaseJniLibsProjectOnly

Task :app:mergeReleaseNativeLibs

Task :app:stripReleaseDebugSymbols NO-SOURCE

Task :app:buildReleasePreBundle

Task :app:packageReleaseBundle

Task :app:signReleaseBundle

Task :app:bundleRelease

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.

Use '--warning-mode all' to show the individual deprecation warnings.

See https:/~~/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 4s

44 actionable tasks: 44 executed

Built the following bundle(s):

~~/app-release.aab

—

On a side note, I don't know why the thumbs indicated that I down voted your reply. I didn't down vote it, but it won't let me up vote it.