Chadori's Forum Posts

  • Hi everyone, releasing a new update soon.

    If you have any feedback, please make sure to write it this week so that I can apply it in the next release.

    Thank you!

  • Release 46 - Stability Update

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

    New plugins

    1. PlayFab Master Collection (v2)
    2. PayPal - Web payment service!

    Thank you.

  • The PayPal plugin is now production-ready! I am really looking forward to the release of this new plugin.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hi everyone, I'm preparing for the next version update. There is also an upcoming new PayPal plugin for web payments, if you have any concerns, please visit the Discord Community by clicking the link below.

    https://discord.com/invite/eS3HK88

  • Hi, sorry for the late response in the Discord Server, it should just be like this.

    PlayerManager.getEmailStatus(PlayerManager.loopEmailList)

    I hope that helps.

  • Hello, probably this issue: bugs.chromium.org/p/chromium/issues/detail

    Basically, Construct 3 is an HTML5 engine that uses Chrome Webview for Android, which has always been problematic and have horrible performance. It's not Construct 3's fault though, at least directly, rather the tech they use, which Google provides.

  • I usually import Spriter in an empty Construct 2 project, then import that Construct 2 project in Construct 3. Finally, copy the Spriter files to my main Construct 3 project.

    Spriter Team tried implementing the import same in Construct 3 as Construct 2. However, the Addon SDK is just that awkward.

  • _FlameSlayed_, press OK and F12 on the editor, screenshot the log, then upload it here, and I'll try to debug it.

    Whenever I get file corruption like this, I always get it repaired. In the worst-case scenario, though, as long as you have at least one backup within the month, it would only be an issue with swapping missing or corrupted files, so you would still be able to recover most of your progress.

    However, even if you don't have a backup, as long as the file size didn't significantly change, chances are it is still salvageable, depending on the log.

  • I can reproduce; I don't know what causes it. The steps to reproduce vary, however, and sometimes resolve themselves.

    For your reference:

    1. https://github.com/Scirra/Construct-bugs/issues?q=getModifierState
    2. https://github.com/Scirra/Construct-bugs/issues/7464
    3. https://github.com/Scirra/Construct-bugs/issues/7456
    4. https://github.com/Scirra/Construct-bugs/issues/7455

    The common error message is Uncaught TypeError: d.getModifierState is not a function. The Construct Team closes all issues regarding this since it's not reproducible from a project but rather the editor itself.

    To note, this issue started months ago, with the export not working if you don't preview first. However, now even that remedy doesn't work anymore. Then, the next remedy is to restart the editor. Now, that remedy also doesn't work anymore. It's practically random to me now when it will work.

    I myself am stuck with this and have to call it a day from time to time when this happens.

    My best guess is that some files aren't loaded properly in the editor while exporting, and this happens. I would like to dig into what's causing the issue to file a report, but the engine is so obfuscated that it's like an insult to anyone who does try to investigate, like our time doesn't matter.

    Ashley, if you want us to investigate issues ourselves, at least help us and not make it hard.

  • > > > > I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

    > > >

    > > > You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

    > > >

    > > > I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

    > >

    > > Ohh, okay.. and what do you think about these actions? Perhaps they can help?

    > >

    > >

    >

    > Those are only for COPPA, which are one of the requisites.

    Yes, but judging by this window we can treat all users as children. It also mentions the GDPR window, which is why there is a problem, because when it wasn’t there, everything was fine. The window requires mandatory data collection.

    Can you understand this? Google has introduced a mandatory requirement to illuminate the window, but it is prohibited for children. Haha, sur.

    They themselves cannot understand their decisions, it’s the same network, like Admob, like Google, they shouldn’t have problems. I can't remove the GDPR window because it's mandatory. Why should I bypass some strange methods and new plugins and write something in the manifest... Hide something.. Is it really not possible to just track whether it is a child or not, and show a window depending on the age.. Maybe there is an action "Tag for under age of consent" is exactly it.

    I apologize for so much text, but I want to figure it out once and for all. I removed children from the app and lost most of my audience. I won't be able to continue to receive such a stable income, and develop an update... It's a nightmare.

    It would also be a good idea for the Construct developers to look at this whole situation, because as you write, they “dialog is hardcoded”... I am surprised by the silence of many, because this is clearly a problem.

    If you are trying to vent, I understand. But, if you are asking me what's the issue, then to elucidate what's happening based on your provided Google rejection response:

    1. It's not an issue with your event sheet.
    2. Rather, it's an issue with your SDK integration and Android Manifest.
    3. You shouldn't have anything in your project that identifies your users since it's targeted only for children.
    4. In your case, your project's build integration.
    5. Assuming you only have the Mobile Advert plugin, you need to remove those identifiers.
    6. No, you do not need a consent dialog. Quite the opposite actually, it's preferably removed, if not required.
    7. Strictly remove the AD_ID permission.

    When writing for this compliance for my own projects and plugin collections (a quick solution). I used this as my guide: support.google.com/googleplay/android-developer/answer/9893335

  • > > I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

    >

    > You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

    >

    > I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

    Ohh, okay.. and what do you think about these actions? Perhaps they can help?

    Those are only for COPPA, which are one of the requisites.

  • I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?

    You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.

    I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs

  • You need every trace of tracking in projects in the Google Play's Design Apps for Families Programs removed, also you need a plugin like this to remove those listed identifiers: constructcollection.com/documentations/mobile/mobile-advert-families-programs

  • Construct 3 is just too broken, too slow and too inefficient to even compete with competitive engines out there.

    1. Too many engine bugs, and we only have one or two developers maintaining it.
    2. Lack of so many features an engine should have.
    3. Plugins and behaviors are made to look attractive, not functional.
    4. Even the simplest of issues do not get fixed, it's either lack of interest or lack of skill.
    5. The developers aren't game developers!
    6. The event sheet is a dead-end design.
    7. The engine is so restrictive.
    8. Most plugin developers hate the Plugin SDK.
    9. The engine isn't extensive, the Plugin SDK is only predefined.
    10. The event sheet being a dead-end design and the Plugin SDK being too limited looks to be a reason scripting was introduced.
    11. Scripting is too limited.
    12. So many bugs in scripting since barely no one uses it.
    13. The users are expected to investigate engine bugs, but are not allowed to fix it themselves.
    14. The community cannot extend built-in plugins/behaviors.
    15. The Construct Team invested more in hiding their code rather than fixing or improving their engine.
    16. If a plugin or behavior is limited or broken, you are on your own.
    17. The Construct Team won't divulge their code or even allow the community to fix their code on their stead.
    18. Performance benchmarks are for web games, not mobile or desktop.
    19. Performance on desktop is alright.
    20. Performance on mobile is horrible, makes desktop performance look like a huge feat.
    21. The Steam plugin is literally only 2 actions.
    22. The Construct Team expects us to write C++ to expand the Steam plugin ourselves.
    23. The Construct 3 expects the community to do all the work while being super restrictive.
    24. We are expected to write native code to extend Construct 3 features for browser-level performance.
    25. The Construct 3 Build Service is too restrictive.
    26. Even if it means fixing crucial issues.
    27. Whitelisting takes 2 weeks to 2 months.
    28. The Construct Team likes to support and experiment on future features we will need in 5 years, but forget features we need now.
    29. The Construct Team also seem to use the engine to experiment on Web Technology rather than for game development.
    30. The Construct Team likes to create experimental features until they get bored and abandon it unfinished or incomplete.
    31. There is no roadmap.
    32. New features, fixes or updates are usually already finalized prior to release.
    33. The Multiplayer plugin is broken for nearly a decade.
    34. The Construct Team talked about improving Multiplayer when the lead developer was excited about it, but eventually left it again without fixing any. Just adding features for his experimental 'game', which is subsequently abandoned, like the others.
    35. The Pathfinding behavior makes you think it's enough to make an RTS game, until you try.
    36. There's a reason why Ashley only tried to make Command in Construct in JavaScript.
    37. The engine doesn't support collaboration.
    38. The animations editor is too simple.
    39. The engine still expects us to do frame-by-frame animations.
    40. The engine still uses puzzle functions. (Worse than Construct 2)
    41. Tilemaps are still static and simple.
    42. Tiles are still static and simple.
    43. Spritesheeting
    44. Memory management
    45. The engine still has no UI features.
    46. The engine's introduction to HTML Elements as UI replacement is so awkward.
    47. The Platform behavior can easily get bugs and regression and we cannot control or extend it.
    48. Expect 3rd party to make them, yet treat them horribly.
    49. Small community due to reasons above.
    50. Lack of plugin developers due to reasons above.
    51. Lack of 3rd party services support; the Construct Team doesn't care about publishing, you're on your own.
    52. Lack of offline support.
    53. No desktop version.

  • Monetization Collection

    Hi everyone, the Monetization Collection for web and mobile monetization has been released. I will continuously work on adding more plugins here as well.

    It is a sub-package of the full package, Construct Master Collection, released with selected basic monetization packages for your Construct 3 and Construct 2.

    Mobile IAP (Pro)

    1. Mobile IAP (Pro)

    Google Admob Collection

    1. Google Admob
    2. AdColony Ads
    3. AppLovin Ads
    4. Chartboost Ads
    5. Fyber Ads
    6. i-mobile Ads
    7. InMobi Ads
    8. ironSource Ads
    9. Maio Ads
    10. Meta Audience Network (Facebook Ads)
    11. myTarget Ads
    12. nend Ads
    13. Pangle Ads (TikTok)
    14. Tapjoy Ads
    15. Unity Ads
    16. Verizon Ads
    17. Vungle Ads
    18. Mobile Consent
    19. Mobile Advert Families Programs

    Web Monetization Collection

    1. Google Ads

    Features list

    Construct 3

    1. Mobile IAP (Pro)
    2. In-app purchases
    3. In-app billing
    4. In-app subscriptions
    5. Server validation
    6. In-app billing
    7. In-app purchases
    8. In-app subscriptions
    9. Local validation
    10. In-app billing
    11. In-app purchases
    12. In-app subscriptions (local validation is experimental)
    13. Google Admob Collection
    14. Google Admob
    15. Ad-network mediation plugins
    16. Meta Audience Network
    17. AdColony Ads
    18. AppLovin Ads
    19. Chartboost Ads
    20. Fyber Ads
    21. i-mobile Ads
    22. inMobi Ads
    23. ironSource Ads
    24. maio Ads
    25. myTarget Ads
    26. nend Ads
    27. Pangle Ads (Tiktok Ads)
    28. Tapjoy Ads
    29. Unity Ads
    30. Verizon Ads
    31. Vungle Ads
    32. Feature plugins
    33. Mobile Consent
    34. Consent dialog
    35. IDFA
    36. Mobile Advert Families Programs
    37. Google Play Designed Apps for Families Program
    38. Google Ads (Web and Web Mobile)
    39. Preroll Ads
    40. Interstitial Ads
    41. Rewarded Ads

    Construct 2

    1. Mobile IAP (Pro)
    2. In-app purchases
    3. In-app billing
    4. In-app subscriptions
    5. Server validation
    6. In-app billing
    7. In-app purchases
    8. In-app subscriptions
    9. Local validation
    10. In-app billing
    11. In-app purchases
    12. In-app subscriptions (local validation is experimental)
    13. Google Admob Collection
    14. Google Admob
    15. Consent dialog
    16. IDFA
    17. Information
    18. This is a basic version of the Construct 3 version's Google Admob Collection.

    Store listing

    1. Official Store
    2. Construct Store

    Thank you.