Okay, so right now I'm gonna cover what I think is an important topic; Encryption of your files. This topic was requested by 
glerikud and a few other people on the Construct 3 official thread
Before I start I want to be clear: I could not care less about protecting my assets from being stolen. If I make a successful game, I would LOVE to see people modding it or reusing part of it to make fan games or games using some of its mechanics as long as they don't make money out of it without my permission.
We discussed it on the C3 Official Thread with 
newt 
Eisenhans and 
X3M — 
Bleenx and a few other people
Construct 2 suffers a big problem, assets are absolutely not protected in the exported product.
Just to illustrate how big of a problem this has become.. the following quote is taken right from the steam community forum of a (relatively) known C2 game published there:
[quote:2dfy6lzy]"How to get the soundtrack for free + view sound clips/sprites/sheets.
Go to the directory of your folder and open "package.nw" with winrar. Then extract it to a custom folder and you are done. Save yourself 5 bucks, only if you want to.
You can probably customize the game and put it back as a nw file"
The main question is: Do Construct (2 or 3) really need to feature some sort of DRM or encryption?
Ashley and newt defended that it would add a lot of loading time to your game without even preventing people to steal your assets.
I personally think that loading time isn't a problem if most of the important assets are decrypted on start. Plus decrypting times on images will clearly not be as huge as decrypting an audio file. And most people are concerned about protecting their visual content. Plus many people don't really care if loading times are increased if their assets are protected:
I don't really care if loading times slow down if I can protect my assets from the majority of the users.
Talking about protection, YES it's not perfect and YES you will always be able to steal data by some dark mean BUT:
1) It won't be as easy as unzipping a rar file, so most of auto proclaimed 12 year old hacker won't be able to do much
2) Yes people will always be able to take screenshots and record audio in order to steal data, but again, it will be much harder
3) If they manage to crack encryption, then it means that they worked quite a bit to get there, and at this point, just let them take some of your assets as a reward of their time spent stealing them, and if they ever use them in a manner you don't like, just strike them. They'd have spent several hours to steal assets to get blocked in the end. Most people would give up at this point.
It is NOT useless as Newt and Ashley tend to say and even if it's far from perfect it's still like having a wall instead of a sheet of paper protecting you and your assets.
Newt made an interesting point about how it was necessary to get a new editor in order to have that encryption feature:
[quote:2dfy6lzy]I would point out that one of the reasons why we needed a new editor was to make it easier to add things like asset protection.
[quote:2dfy6lzy]Secondly the engine would have to be altered to decrypt them every time, on top of load time. As I said the C2 editor made the first part complicated.
[quote:2dfy6lzy]Then as to the issues with the C2 editor, just remember the issues we had getting additional features to tilemaps.
To which I replied that no, we didn't need one because RPG Maker MV a software running on OpenGL (like Construct) and exporting HTML5 games (like Construct) on NW.js for desktop builds (like Construct) featured encryption as part of their 1.3 update:
[quote:2dfy6lzy]
RPG Maker 1.3 Update! [...]
You can now Encrypt your games, both images AND audio using a simple encryption built into the Engine!
The only editor-side add that is needed is literally adding a checkbox with encrypt audio and encrypt images as well as having a textbox where we can enter an ecrypt key.
This is how RPG Maker MV did it:
This where it could be added in C2:
I'm pretty sure C2 can handle this change
So. This topic is open for you to discuss this. Please don't repeat yourselves and try to build actually good arguments in order to have a good respectful discussion.