Tom's Forum Posts

  • Hah, glad it got you back into it! Was fun doing that

  • I think most of that list is reasoned fairly, and unlike other criticisms you've given reasoning as well which is much appreciated. If we did it again, I think I'd agree with you on most of those points.

  • What specifically do you find unprofessional and childish about how we've approached the marketing?

  • Calling our marketing childish is a new one, not heard that yet!

    Anyway, regarding features and what's new, the new website will have a comprehensive list. This should be available in time for the public beta by the months end.

  • Interesting idea, has been noted.

  • Understood, and thanks for appreciating our point of view. Every time there is a big change in a business, you will have people that leave, and find new people that join. We fully expected some people to not like our decision, and on the other hand we expect to attract more customers who otherwise could not use Construct 2 (eg Mac and Linux users).

  • I have heard from some educators similar stories RE iPads. The device existing en-masse in US educational institutes is now the Chromebook which there is very limited supply of software that can run on it... Hopefully Construct 3 can fill some of that void.

  • Thanks for the suggestions, ntoed. We agree we've been marketing from the wrong angle in the past. I think when you see the new site you'll agree it's a lot more confident in its approach.

  • > Please both be civil to each other, no need for that.

    >

    > Lamar, any other security related questions or are you satisfied with those answers now? I'd be interested if you had similar concerns with other engines and if you took that into account when choosing Construct 2?

    >

    Yes I read the security and privacy conditions before I ever get into any contract which is what I highly recommend for everyone.

    That is why I have suggested you put those out here in the forum so we can have time to look them over and discuss them before some people rush to purchase C3.

    That is as much to the benefit of Scirra as it is to your users as it shows complete openness and something Scirra should be proud of and is a selling point.

    I commend you on reading security and privacy conditions of any software you buy, more people need to do that! And I'm glad you found Construct 2's agreeable and that was a factor in your buying decision.

    Do you understand that the risk of us publishing our privacy and terms and conditions ahead of them being finalised is not good from our perspective, or your perspective? They will both be able to be reviewed during the public beta by everyone. If we publish them now, and change them between now and the final version we could be accused of misleading customers. And secondly, I don't see any point to publishing them ahead of actually having use of the product. We'll publish them when they are ready, and when the product is ready like everyone else in the world does!

  • [quote:2fbx51ze]Saying you haven't locked an engine when you have not released C3 which has new security features is not exactly answering the question.

    We can't lock people's engines. We can only remove the ability for them to use paid licensing features (eg unlimited events, export options etc). This is exactly how Construct 2 works, and we do on occasion revoke users licenses. Most common circumstance to do that is when the customer does a credit card charge back on their purchase as the payment was fraudulent.

    [quote:2fbx51ze]Can you lock a specific engine on C3?

    We can revoke people's access to paid features and make them fall back to free edition, exactly the same as Construct 2. And I imagine, in a very similar way to how other game engines do it as well.

    [quote:2fbx51ze]If there is no way for Scirra to view a capx or in some way add a tag to the exported projects we produce I sure don't see how you will enforce your license?

    Well, we don't. You're talking about stopping people sharing licenses in some capacity which is very difficult for us to stop. As I mentioned before, we never intend to spoil legitimate paying customers experience of Construct.

    If we look back at Construct 2, there have been a handfull of times when we've revoked paying customers licenses. This specifically happened when we saw the license being used thousands of times over a short period. The way we deal with this is email the customer a new license, then revoke their old one.

    Are you happy with those answers?

  • Please both be civil to each other, no need for that.

    Lamar, any other security related questions or are you satisfied with those answers now? I'd be interested if you had similar concerns with other engines and if you took that into account when choosing Construct 2?

  • Well I thought made clear in my previous post and you basically told me to shut up and stop asking and read the privacy T&C when it comes out?

    I don't believe I've told anyone to shut up, I'm being patient.

    I want to know how C3 is handling security that will allow you to know what a person is publishing to enforce your license?

    For example: If I have a license C3 version and my buddy has a free version and I use my version to upload his capx and export it to a different platform is Scirra going to know of that and will they lock my engine?

    We've never 'locked people's engines'. And I don't think it's reasonable for us to go into our anti piracy measures with you as part of an effective anti piracy strategy is not outlining what exactly we do to combat it as it's a game of cat and mouse. Our policy internally (and we've debated the ins and outs at length) is that we know some level of piracy will happen, but we will always do our best to ensure it never, ever affects legitimate paying customers. As long as you're a legitimate paying customer you do not need to worry.

    I don't know of any other way you could enforce your license without including code that would allow Scirra to internally shut down a specific engine

    We've never shut down a legitimate paying customers engine.

    and that raises privacy concerns over who is vieweing and possibly copying our capx projects.

    It doesn't, as I've explained a few times now we don't have access to your CapX files unless you explicitly decide to upload them as files to our arcade or as forum attachments.

  • Lots of discussions on features and very little on security and built in codes that could end a game designers ability to use the engine which is very important to game developers that make a living from that business.

    Security is a nebulous concept. What aspect of the Construct 3 engine's security are you specifically concerned about? And what security aspects do you think would end a gamedevs ability to use Construct 3?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Read our privacy policy when it's published as it will cover your concerns.

    [quote:20o7a4ai]Like your C3 progam many game designers don't want people looking through their capx which may contain copyrighted and proprietary information.

    We don't look through your Capx files, as mentioned in a previous thread we don't have access to your Capx files.

  • I'm afraid for security reasons can't really go into that sort of information, hope you understand