Chadori's Forum Posts

  • lucid that's great! And also thank you for updating and fixing the SCML plugin.

    Maybe after releasing Spriter 2. You can also port the SCML to C3runtime so that we can take advantage of Construct 3's performance with the new runtime to be able to do more with Spriter 2's new features. Thanks.

    Basically for more reliable, faster and stable maintenance and innovation of the Editor and Runtime and also to keep up with up-to-date HTML5 technology which wasn't that feasible or as fast with only Construct 2 - One Time Payment.

    Including, website, cloud build service, server, feature requests, bug reports and especially making the Construct Team bigger to respond to all those previously mentioned, faster and better in terms of quantity and quality.

    I hope that shed some light on the subject.

  • —

    My solution was to reference an updated version of the Cordova Plugin that will be compatible with the CLI 8.0.0.

    Here : github.com/Scirra/Construct-3-bugs/issues/1864

    The solution might be more applicable for the original developer, Nepeo.

    You are just going to have to wait for him to create a fix. It doesn't seem to be bad enough case though.

    I bet he can fix it soon, just need a little bit of patience.

    Agreed.

    We pay a subscription to make it work!

    What's the point of subscribing if something always breaks or doesn't work?

    It is an experimental feature [C3 runtime]. Of course, it isn't even recommended for publishing.

    You can export at your own risk.

    Besides, you can still export using the usual way.

  • You do not have permission to view this post

  • My solution was to reference an updated version of the Cordova Plugin that will be compatible with the CLI 8.0.0.

    Here : github.com/Scirra/Construct-3-bugs/issues/1864

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This situation might be similar to my case ::

    github.com/Scirra/Construct-3-bugs/issues/1863

    It might not be the problem with the C3 runtime but the Cordova plugin doesn't support the CLI version 8.0.0..

    You will have no problem using Cocoon.IO though as it doesn't use the latest Cordova CLI version.

    Although, you'll have problems with updated ones like the Construct 3 Build Service and Phonegap.

    That's what I've gathered from my tests. Although, I could be wrong. But I just want to give my hypothesis on the matter as the error report is quite similar to mine.

    Also, the other way around will also get an error. Older Cordova Version supporting a newer Cordova Plugin will also result an error.

    So the C3runtime is not supported at the moment with Cocoon.IO.

    Because of the 'cordova-plugin-file', which the new runtime is using is using a latest version which doesn't work with older Cordova CLI versions.

    I also encountered it here, on this closed bug report of mine ::

    github.com/Scirra/Construct-3-bugs/issues/1859

    My point is that this may be only a conflict between cordova plugin versions and cordova cli versions. Not the C3runtime. Although I could be wrong, this is just based on my tests.

  • You can of course. Although, at your stage, I wouldn't count on it. We know that because you asked that question in the first place.

    You can do it by either with your own back-end or the Photon plugin for easier management.

    But yes, it will take a massive amount of time and money. Although, if you become practical enough and remove the time or money heavy consuming elements, then it really is very possible.

    Although, I recommend that you start small first. And work your way through.

    Or you could practice doing it, and fail after finishing. But probably on your next try, you can make it successful afterwards. But that requires patience since you won't earn from practicing unlike starting small.

    You can pick either the Short-Term Plan or Long-Term Plan.

  • They would at most very likely white-list all cordova plugins the community provides. Yeah, you just really posted on a different place.

  • It is possible using the Construct 3 Build Service. Just request cordova-plugin-gameanalytics to be white listed on the Build Service on the link below, if it isn't yet white-listed.

    Link:

    github.com/Scirra/Construct-3-bugs/issues

  • You are confusing how export to C2/C3 works.

    This is the general idea:

    Construct 2 -> Export -> Cordova -> Builder :: Phonegap/Cocoon.IO -> Android or IOS

    Construct 3 -> Export -> Cordova -> Builder :: C3-BuildServ./Phonegap/Cocoon.IO -> Android or IOS

    There are no trade offs. Since you can also do this.

    Construct 2 -> Export -> Cordova -> Builder :: C3-BuildServ./Phonegap/Cocoon.IO -> Android or IOS

    The only trade-off is the runtime features and editor features of Construct 3.

    But after export, they are all the same.

    For GameAnalytics, you still can't export straight as a Xcode/sign Release APK file. You will still have to export out as a Cordova Project in C3. Correct me if I am wrong.

    You always need Cordova if you want to make HTML5 games on Construct 2 or 3. And expect it to run on mobile, both on Android and IOS.

    Unless you have a native compiler. [Which you don't have to worry about, for now.]

    Construct 2 and Construct 3 exports to a Cordova Project. And you will need to build it using Cordova Tools or Cordova Cloud Builds.

    Like Construct 3 Build Service, Phonegap and Cocoon.IO.

    What it actually means is that, you need to include the Cordova Plugin Reference of the Game Analytics Plugin for it to work on Android and IOS. Or basically, Mobile.

    The Cordova Plugin Reference for the Game Analytics is cordova-plugin-gameanalytics.

    Because you have asked this, I believe you still haven't tried exporting to Cordova for Android / IOS with Cordova plugins extensions.

    But I can't teach and tell you everything in just this reply alone.

    So, I recommend you to search for some tutorials on how to build Cordova Apps on Construct 2 or Construct 3 with Cordova Plugins like Admob and IAP using Cocoon.IO.

    That should do it. Good luck!

  • Well. You are given three choices by the 3 of us.

    1. Export on C2 and build on C3. It will work if the Cordova Plugin reference is white-listed on the C3 Build Service. [Mine]
    2. Port the Construct 2 Cordova plugin to Construct 3. So you can also edit on Construct 3 and take advantage of the new Construct 3 features. [Kyatric]
    3. Use the AJAX plugin and avoid 3rd party Construct plugin and Cordova plugin dependencies. [WackyToaster]

    No wrong answer, all are working. It is up to you to pick which is more beneficial to you.

    Although, you can also just use the Game Analytics plugin. Which is available for both C3 and C2.

    Construct 3:

    construct.net/make-games/addons/95/gameanalytics

    Construct 2:

    construct.net/construct-2/addons/96/gameanalytics

  • Yes. Export on Construct 2 and Build using the Construct 3 Build Service.

  • MPPlantOfficial

    The private messaging system was removed, as far as I know is to comply with the GDPR by preventing the collection of private data in the first place. And all messages to be made public through the forums with full-control for the sender to delete and modify its message or topic.

    In Layman's term, it was removed for everyone's safety.

    Regarding the Mobile Build Service, as what I've understood from Nepeo. There should be no build attempt limit, and the mobile build service is a built-in feature included in the Construct 3 Subscription.

    Although there is a Mobile Build Service size upload limit.

    Previously::

    +Compressed : 500MB

    +Uncompressed : 500MB

    Currently::

    +Compressed : 1GB

    +Uncompressed : 1GB

  • Nepeo Thanks a lot. At least when someone needs it. It is there and available.

  • I don't know about the issues you've came across.

    But, to be honest, on the performance side. I wouldn't recommend.

    Some of us on the Construct Community, we were checking out your plugin on how it achieved it.

    I didn't get to read it for long but as I recall, it loops through all the event sheets and events.

    On Large Scale projects, it would take a very huge amount of resources just to look for a function.

    When in fact, functions are supposed to be optimized to be quick referenced. And not search through the event sheets.

    And the most heavy part of it is that it runs every tick. The performance overhead it provides is very hard and bad.

    Good try though.