Why are anti-C3 comments not allowed on the forums?

Why are the C3 mods "locking threads" where PAYING CUSTOMERS are expressing their disappointment with C3s pricing structure? We PAID for a C2 license and have a right to be heard - just as much as the 'fan club' has a right to be heard too.

For example:

"This thread, like the others has run it's course. Locking. If you don't want to pay $99 p/y for Construct 3, my suggestion is don't! Construct 2 continues to be maintained as promised."

This practice is hardly professional, and certainly does not reflect the actions of how a company charging hundreds of dollars (per annum) should behave. Scirra, act more professional.

We're upset at the new pricing structure, and our voices should not be stifled.

Completely disagree with you. A lot of these threads have gone on for a long time and repeat themselves so many times. So in my opinion they are very professional, they let all voices get heard. There does reach a point where the thread is so long and just repeats itself over and over again that it makes sense to lock it. They don't remove it, just lock it.

Producing and maintaining software is expensive and almost every vendor has gone to a subscription model. Most people complained at that time also. What it comes down to is if it has value to you, then it's worth it.

It's because it's not constructive. The people begin repeating themselves, and don't raise any new arguments. Everyone isn't going to be satisfied with every decision made.

It's because it's not constructive. The people begin repeating themselves, and don't raise any new arguments. Everyone isn't going to be satisfied with every decision made.

Then, to be fair, Scirra needs to start locking threads that contain "C3 is awesome" type comments. They are not constructive and very repetitive.

Constructive discussion around C3 is allowed. The thread linked to ended up not being constructive. Locking this thread as there's nothing more to say on the matter. Feel free to email me personally if you have issue with this instead of opening more threads.