> 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.

Saying you haven't locked an engine when you have not released C3 which has new security features is not exactly answering the question.

Can you lock a specific engine on C3?

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?

I am interested only because an internet based model of design is going to open up security and privacy issues.

> Tom is here and does not need you to answer or run interference for him Bleenx.

>

I'm not answering for him. I'm asking you questions.

> 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?

>

Dig yourself that hole. This is making you come across as if it's something you plan to do, not something hypothetical. Is this why you're worried about security?

No you are trying to attack me personally for asking questions to Tom about security while running interference. That is obvious to anyone reading this thread.

End of discussion with you.

> ....

>

You've asked about security several times already and Tom has to repeat himself. What is it you're so worried about that hasn't been addressed? No one is looking through your capx files. No one is stealing your "code" on the cloud. And no you can't make a side business helping to export people's files.

You don't like the sub. You're not going to sub. But you're just rehashing the same security stuff because you're looking out for the interests of others who might buy it, who are more than capable of reading the T&C regarding security? Come on.

On topic of this thread: The point of C3 is an upgrade to C2. Different look, some new features, different support. It's not a demand to upgrade. Many of us kept using Unity 4.6 long after Unity 5. You don't have to upgrade, but if you do, you do it because you want the features that C3 has which may not be in C2.

Tom is here and does not need you to answer or run interference for him Bleenx.

Kindly stay out of that conversation and do not use my name in a quote using your own words or distorting what I said.

> 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?

Well I thought I made that 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 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?

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 and that raises privacy concerns over who is vieweing and possibly copying our capx projects.

> I just said a lot of stuff.

>

Can't tell if you're being sneaky or overly paranoid.

Just getting to the stuff not being discussed that should be before considering purchasing the new C3 engine.

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.

Also DO NOT put my name next to things I did not say in the future!

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

Well, the way you handle security will be a determining factor for some people in deciding if they want to buy C3.

Sounds like you have some built in code to tell what a person is exporting which raises privacy concerns over our projects.

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

Yes, I believe we already have T&C covering that and will be part of the C3 T&C.

Ok but once a project is exported to a platform how is anyone going to trace it back to who exported it and how can Scirra go after people in other countries if they just ignore the license?

Do you have some built in code to lock a specific users engine in C3?

I don't think people doing that are going to openly advertise who they are.

Tom

I have a hypothetical:

What is to keep someone from setting up a little side business with a licensed copy of C3 so people with the free version can send them their capx and get it exported to whatever platform they want?

Is there anything written in the license that prevents someone from doing that or any programming that prevents importing other people's capx?

Not that I would do something like that but I am sure other people will think of doing it.

https://www.scirra.com/tutorials/5343/h ... -game-capx

Hi,

the equivalent in pseudo code would be something like:

> method a
{
    if (trigger)
    {
      return;
    }

    (...)Do something funky
}

method b
{
    if (trigger)
    {
      return;
    }
    
    (...)Do something funky
}
[/code:3fay70jv]

This would be called "bad coding style" I guess. There must be a better way...

Ok well good luck with that and using global variables is not bad coding style.

I won't bother myself helping you in the future.

Look here:

You have the Wait command or On Every Seconds command. You will need a couple of global variables. DoSomething is a trigger and Timer holds the time.

On Object1 Collides with Object2: Set DoSomething= 1

Every 1 Second: Add 1 to Timer

DoSomething=1