glerikud's Forum Posts

    Idea #1:

    - 30 minutes a day

    - Time resets every day

    - Unused time is not accumulated

    Idea #2:

    - About 10 hours a month

    - Time resets every month

    - 20 minutes a day is accumulated until the end of the month.

    An other issue with this idea (next to the ones mentioned before this post) is that some bugs take more time to fix than 30 minutes (obviously). When a developer is in a flow state, you don't want to break that by locking them out while they're thinking hard about a problem and trying different approaches to solve it. I would be so furious to be locked out because of time limits while I'm on the right track of fixing something and I would have to come back the next day.

    Subscription for updates is very open to abuse. Let's say one user on yearly subscription gets his 12 updates (1 a month), and user 2 who hasn't subbed in the last 12 months, pays 1 month sub and grabs the latest version then unsubs again. Getting the same end result as guy 1 but not really paying enough to support further development

    In that case the yearly subscription would be the only sensible idea. I think pirated copies could pose more of a problem. But Scirra seemed to take of this issue with C2 quite efficiently, so I think they could do it as well with C3.

    Why not make C3 a one time payment.... with no subscription. Plan to release C4 in exactly one year along with a major new feature, and drop any support for C3 and all further updates for it, only offer downloadable last stable for people who wanna cling to it, once the new C4 version is released.

    Make a plan to release major new version release on a yearly basis. Make it clear that no further updates and support to old versions will be available once the next version is released. Only a downloadable last stable will be available for old C3 once C4 is released.

    If people try to access C3 online once c4 is released, they will get a download link or an option to upgrade to c4.

    Maybe even Make the build service a seperate service for C2, C3, C4 users alike for those who wish to use it?

    Problem solved?

    That's not a bad idea at all. I'm sure it has downsides as well, but it might worth the consideration.

  • Check that WebGL is enabled or not in your browser.

    How serious people are is not measured by their coding ability. C2\C3 is just a tool like any other, just specialized for those who don't know any traditional coding language.

    I might add: .. or don't have time to develop using traditional coding, since the event system is way faster.

    Single project= pay per event, billed at the end of each month for additional events, exports cost extra.

    It's like paying for minutes using telephone services. Or if you'd pay per minute (or level) in World of Warcraft. A terrible idea in my humble opinion for a development environment.

    I think some people are trying to say you're locked out of your project entirely. That's not the case. You mainly have edit and export access taken away.

    As I've said before, we're looking in to adding a special option for people who have had exported projects in the past, so they won't have to sign up for another full year just to export again or make a few quick changes. Assuming we have something like that in place, I don't think it's fair to say any work is "held hostage" either.

    That should ease users who want to patch, tinker old projects. I'm looking forward what you'll come up with.

    So what's stopping them from still using C2 then? Nobody is forcing anyone to buy C3. C2 would be the equivalent of CS6. And C3 would be the equivalent of CC. C2 is still a viable option for people who don't want to pay subscriptions. Why do you have to use C3? If someone really need or want the features in c3 why not just pay up if they feel it's worth it, if not stick with c2.

    I agree with your argument. But I think the main problem here is that serious developers want to have full control over their project. And Scirra needs those serious developers to keep the engine rising. I'll hope the solution Ashley posted above will solve this issue.

  • Yeah, that's the frustrating part. I've got something really odd happening in a game I'm building (I made another post about it), and it's most likely something I did wrong, but I'm following a tutorial and can't figure out where I went wrong. So it's that question of not knowing if it's my fault (probably since I'm figuring it all out as I go) or a bug that I can't do anything about right now that's killing me.

    Because the obvious temptation is to say, "well, I did this right so it must be a bug." But chances are I did something wrong, and that's no way to learn.

    Then just grab C2 from the website and learn the engine using that editor. Since C3 is very similar to C2 currently, you won't have a problem to switch if you decide to purchase it after you get the hang of it. Also I believe the offer still stands that if you buy C2 before the release of C3, you'll get 1 year of subscription for C3 (https://www.scirra.com/blog/183/announcing-construct-3)

  • Thanks for the advice. I decided to dive in to C3. I'm following a YouTube tutorial for C2 and it's very easy to follow. I was worried the UI might have changed a lot, but I'm pleased to see it's basically the same as it was before.

    Just keep in mind that it's still beta. So bugs are expected.

  • This was just added for r20.

    Great, thank you.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This question might have been asked before, but I couldn't find it searching the forums, so here it is:

    Is there any reason why we can't duplicate objects in the project tree? In C2 right clicking an object would provide this option, but it's not there in C3.

  • Hi there!

    Thanks for the suggestion. We were planning on allowing the teacher to manage accounts, either one of two ways:

    - Create username/password for students

    - Create timelimited codes teacher can create so entire class can login quickly with same code for short durations (eg 2 hours)

    RE the Google accounts, it's an interesting suggestion I'll have a think about!

    We're hoping to release standalone version by end of May.

    Great news. That would simplify the usage in classrooms.

  • Remote preview can do that - but it depends on WebRTC, so just Firefox at first (it's coming to other browsers). It's not actually that easy to add in the desktop build, since we don't run a HTTP server any more, but we could look in to it.

    It's an interesting question. Since C3 works offline as well, how do users preview their work in different browsers if they don't have access to the Scirra servers generating the link? Also, if those servers are down by accident or maintenance, how do the users preview in other browsers?

    Thank you for clearing that. I'm looking forward to digging through some suggestions.

  • I agree. Finally, the forums are a pleasant place again.

  • We are also doing private testing of the full version which is helping iron out bugs, and the Newgrounds jam is intended to flush out any last ones that slipped through the net.

    Let's just hope that one week will be enough for that. You might want to consider expanding the beta (or delaying the release) if something unexpected happens during the jam.