Chadori's Forum Posts

  • jkh0208

    Does Construct 2 have the issue where you have to connect to the internet every 7 days to verify? I can't use Construct 3 since I'm without internet 6-8 months out of the year on average.

    No. Construct 2 is an offline application, so you don't have to update or re-login every 7 days unlike Construct 3.

    The benefit of Construct 3's online subscription is that you have constant update and support for new features, bug fixes, 3rd party compatibility, technology updates and etc. This is very essential for developers who commercialize their games.

    If you don't have internet for that long period of time and maybe constantly travel and/or are on remote places. Then, I assume you don't make commercial games and do this mainly as a hobby. Then, I do think and recommend you go with Construct 2.

    I remind you though that Construct 2 is 1.6x more expensive than it was before. And also, it is outdated and Construct 3 was made to replace Construct 2.

    Construct 3 :: $99.00 per year.

    Construct 2 Before :: $120.00. One-time payment.

    Construct 2 Now :: $199.00. One-time payment.

  • This seems great. Does this support c3runtime?

  • I use Firebase Authentication for Construct 3 but for you to use it, wouldn't that just be like using spare parts in building a car.

    Unfortunately, we don't have a Google Plus plugin for Construct 3. And I'm not even sure if there's one for Construct 2 either.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Ashley

    - we don't mind discussion of competitors, but telling people to go and use different software on our own forum is a step too far. Please refrain from making such posts.

    Ohh, sorry about that. Construct 3 is excellent for startups though.

    And all of that are true.

  • Admin: removed part of post telling people to use other software

    The features there is way better and Construct 3 is an incomplete product especially with the current SDK limitation, trust me!

    But if you are a startup and have low in funds... Then I guess Construct 3 is fine.

    But don't buy Construct 2 anymore, for it is outdated and currently overpriced after the price raise to encourage new users to subscribe to Construct 3 instead.

  • In the past other users have asked us to remove such warnings because they're annoying, especially when there are no references to the thing being deleted in the project.

    On Construct 2, it still has the warning.

    He means, on Construct 3, even when there are instances, the layer still gets deleted.

  • I think this is suited more as a bug. This is kind of dangerous.

    github.com/Scirra/Construct-bugs/issues

  • Ashley

    That's the wrong solution, and uses an extremely coarse measurement anyway. You probably should use something like requestIdleCallback instead.

    Okay. I'll look that up.

    Besides in the C3 runtime layout loading is now asynchronous so may not jank the game any more while loading. Also the whole idea of preloading an entire other layout will spike the memory usage high, significantly increasing the risk of out-of-memory crashes... it kind of defeats the point of the layout-by-layout memory management that aims to keep peak memory usage low.

    Well, I'm not sure about that. But I surely haven't encountered that in c2runtime on Construct 3 at least.

    Although, aside from the conventional usage of that addon, there is an exclusive use for that addon that the normal layout-by-layout loading can't do.

    Imagine having 100 Spriter Character objects / 100 Sprite objects.

    You have to preload only 10 of those characters per game. As you only use 10 Players per battle match.

    You can't do that with normal layout-by-layout loading as you will have to load image memory that isn't even used.

    With this, it ensures that images that are only needed are the ones only loaded.

    Plus, you can add custom initializations per layout.

    I'm not sure why this needs to have anything to do with loadingprogress either - why not just give the plugin its own expression? The more you hack in to the runtime code, the more brittle it is in the face of future changes. The best architecture is to keep as much code as possible entirely independent of the runtime.

    It needs to. For example, you are on the loader layout. Before going to the main layout, you need to preload the main layout to only load the images needed and also for some custom initializations. But, you need to wait for the Construct Engine to load first or at least finish.

    I hope that explains it all.

  • Why do you need them for a preloader addon? What does it do and why can't you do it without these? In particular requiring the FPS for this seems particularly weird.

    Given we are obligated to permanently support all APIs we document with backwards-compatibility forever, I'd prefer to keep the SDK to the essential minimum.

    construct.net/en

    TobyR made some preloader addon that a lot of us agreed useful on Construct 2. To make it stable, taking FPS into account is important and the loading progress to integrate the Construct Loader Layout loading progress with the preloader layout to extend the Layout-by-Layout loading.

    I actually asked this from you guys but you guys seem to have your hands full at the moment with the c3runtime and I don't want to disturb that. I only ask this so I can finally port to the c3runtime. Thank You.

  • Ashley

    Why do you need them?

    I want to port, or at least, make a basic preloader addon. I really need it for my project. I need those references to stabilize the preload and also to integrate the Construct 3 Loading. I hope you understand.

  • Ashley

    Can I request for these runtime references. Thanks.

    1. fps
    2. loadingprogress
  • This looks great! If this is a collection of Cordova Plugins, wouldn't it suppose to work for IOS too?.

    It's a surprise that you packed all those features in a single plugin. I think it would have been better if it were separated by modules through separate plugins. Although I can't blame you, by the looks of it, it seems as it was a custom plugin originally for your personalized use, you just made public . Thanks for sharing to the community.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Ashley said in 2014, when introducing the new Multiplayer Objet;

    -We have plans to add even more features, ranging from persistent logins with player data storage, to geolocation-based matchmaking to help improve the connection quality.

    is it me or the persistent logins with data storage was never a thing?

    imo it makes multi limited if we cannot store things for every player... like in a rpg for instance.

    Thanks guys.

    Since not a lot were using it and demanding for it. It didn't get improved.

    Then again, there was a time it was in demand and failed but it was Construct 2, it didn't have as good support unlike now with subscriptions. But now with Construct 3, people mostly gave up on the multiplayer plugin and went for the alternatives like customized plugin, customized back-end, WebSocket System or 3rd party plugins like Colyseus or Photon Cloud / Server.

    To be honest though, if you plan to have Multiplayer for your games,

    I suggest making your custom backend + client plugin for massive CCU per room games like IO games and use Photon for Battle Arena Games.

    For online data storage, I don't think relying on the Construct Team or Scirra is recommended. I'd use Firebase for that or a Custom Server Database.

    If you don't have any programming background:

    For Realtime Multiplayer::

    Battle Arena :: Photon

    For IO Games::

    I guess you can use the Socket.IO plugin, I think there are some free ones here. Or better yet, buy a utilization license or hire someone to make you one.

    For Online Storage Database::

    You can use the Firebase Plugin by Rexrainbow.

    If you have some programming background:

    You can make your customized backend + plugin client and mix in with other 3rd party plugins. It makes things easier in the long run and you have more control and flexibility for performance, storage, bandwidth etc...