Chadori's Forum Posts

  • For those interested in the alpha-release, kindly email: support@constructcollection.com. Unfortunately, only limited slots can be accommodated. Thank you.

  • Hi everyone, great news.

    The Construct Master Collection is finally Addon SDK v2 compliant.

    1. PlayFab Master Collection
    2. Mobile Master Collection
    3. Mobile IronSource Collection
    4. Web Master Collection
    5. Game Master Collection
    6. AppLovin MAX Collection
    7. Google Admob Collection
    8. Monetization Collection

    The following plugins have also been updated to the latest rewritten SDK:

    1. PlayFab Master Collection
    2. Mobile IronSource Collection

    The following plugins have also been updated to the latest SDK versions:

    1. Google Admob Collection
    2. AppLovin MAX Collection

    Sorry for being silent for the past month. I was traveling and needed to concentrate on completing the milestone.

    The following plugins have also been updated to the latest versions, and all remaining bugs have been fixed:

    1. Mobile Notification
    2. Mobile AppsFlyer
    3. Mobile OneSignal
    4. Mobile Review

    Now that all the problems have been fixed, I can be more active again in providing support.

    I will also be making an alpha-release beforehand to make sure everything works.

    Stay tuned!

  • Release 50 - Stable Update

    Hi everyone, there is a new stable update for the Construct Master Collection, please click here to read the release note and download the update.

    Thank you.

  • Hi everyone, there's been a minor issue with the release demo project named "PlayFab Purchase Validation" for the Mobile IAP (Pro) plugin which uses the old expressions instead of the simplified new expressions. Although you can fix this yourself by checking the JSON output directly.

    This issue happened since I test on a separate branch from release, and when a test is successful, it gets merged with the release branch. Recently, due to the many changes and tests to be done for each platform, the merges probably got mixed up.

    I have corrected the demo project for the upcoming release. However, for those using the current release, you can just download the updated demo project below directly.

    This demo project is only for those who are using the free PlayFab validation service for Mobile IAP for Android or iOS.

    I hope this helps. Sorry for the inconvenience.

    Thank you.

  • Release 49 - Maintenance Update

    Hi everyone, there is a new maintenance update for the Construct Master Collection, please click here to read the release note and download the update.

    Thank you.

    Hi Ashley, to translate, we are just asking for something that even artists or non-programmers can understand. And I don't mean actual or pro artists; I mean the wannabe kind.

    To illustrate, just give us an action that makes us feel like we're making progress and feel like tech savvies with no effort. Leave the dB values to the nerds.

  • I have fixed the Firebase plugins, and they seem to be working fine. Although I'll have to cross-check with other plugins, I'll hold it until the next release.

  • Hi igortyhon, I will note this for the next update. Thank you.

  • clarkgame

    Great work, also I would like to ask: Do you have any plan for SDK2 update?

    Hi, yes, compliance with Addon SDK v2 is on the milestone list. I'm just waiting for the Construct Team to finish the API, because I believe it's not yet finished.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Release 48 - Maintenance Update

    Hi everyone, there is a new maintenance update for the Construct Master Collection, please click here to read the release note and download the update.

    Thank you.

  • Hi haypers, this happens when the Mobile Advert Families Programs plugin is added last in the Construct 3 project. I requested a feature to fix this with the Construct 3 Build Service, but just like most of my requests for mobile to support SDK integrations, this was unprioritized by the Construct Team as well.

    For the fix, you can use the public issue with the Mobile Cloud Save plugin.

    1. Fix using the Construct 3 editor.
    2. Fix using the text editor (reliable fix).

    If this happens, you only have to do this once in your project.

    Basically, the goal is to put the Mobile Advert Families Programs plugin at the top of the objects list of the Construct 3 project.

    The plugins that need this fix in the collection when this bug occurs are the following:

    1. Mobile Cloud Save
    2. Mobile Advert Families Programs

    I'll try to bring this issue up again with the Construct Team. Unfortunately, this is the only way to support the listed plugin features while still following the Construct 3 Build Service guidelines while also supporting the built-in Mobile Advert object. There is another workaround, but it takes more time through a plugin than for the Construct 3 engine to just support it itself.

    We should have references about this in the Discord Community as well.

    I hope that helps.

  • Release 47 - Maintenance Update

    Hi everyone, there is a new maintenance update for the Construct Master Collection, please click here to read the release note and download the update.

    Thank you.

  • Hi, you can use our Mobile IAP (Pro) plugin if you need subscriptions and other advanced features.

    constructcollection.com/documentations/mobile/mobile-iap

    The latest Billing version is also in Beta on our Discord server, pending a stable release.

    discordapp.com/invite/eS3HK88

    Ashley

    Therefore addon developers have, as a minimum, over a year to update their addons (one year starting from the next stable release). We will review this schedule over time and milestones may be delayed if necessary, but we are publishing this as a guide for addon developers to plan with on the assumption that this schedule will be adhered to.

    I would like to request that this timeline be extended to at least 2 years. Not because it takes time for us plugin developers to port the plugins to Addon SDK v2, but because I doubt the API will be able to catch up with the needs of the plugin developers.

    For context, it's been 5 years, and the scripting interface is still incomplete. It's only recently that the majority of the features have been interfaced with the scripting API, but that's still only relative to the event sheet.

    Assuming it took a year to cover all essential APIs for the plugin developers to get to work, which I doubt, they still cannot just instantly port all the plugins; additional time is still needed.

    Even if the plugin developers can work concurrently as new APIs roll out as new update releases, you cannot expect them to, especially those who are doing this only out of the kindness of their hearts for the community in their free time.

    Ashley

    As I've said before, I am keenly aware of the amount of work this will create, and that is regrettable. However, please understand that we are not doing this for fun: the current compatibility disasters and future risks are in my view so severe, that this is very much necessary, despite the magnitude of the problem it will create in the short to medium term. If you don't believe me or disagree with that judgement, I'm there's not much more I can add, other than to say that you either learn the lessons of history, or you are doomed to repeat them. The industry came up with encapsulation to solve these kinds of problems, and we are moving towards that industry-standard approach. If we postponed this by a few years and then were forced to do it anyway, it would be even more difficult and even more addons would need updating. So if it's going to happen - and in my view it absolutely has to - then the sooner we act the less bad it will be.

    Why are you trying to convince or gaslight everyone into believing that the developers are too lazy to update the plugins? That's not the issue here; the issue is that you are pushing for Addon SDK v2, making it look like it will solve all our problems with encapsulation when it barely has any API in it.

    You are launching an Addon SDK v2 with an incomplete API and blaming plugin developers that we do not cooperate. We're aware of what you're trying to do; you are making yourself look good and making it look like you have every customer's best interest in mind. 

    When, in reality, you are the one not cooperating. How are we supposed to port the existing plugins into the latest Construct 3 editor where, otherwise, other engines would work?