Personally, I'm hoping for lock-out of cloud services (to spare Scirra from additional server load from non-paying users) and updates (users will need to update to keep up with the evolving C3 and HTML5, and also for getting bug fixes) till the users renew their subscription, but letting them edit and in some form, export their projects. But that's just my opinion.

I think this would be the most ideal solution (for users anyway), if C3 is built in such a way to accommodate this. If development is as frequent is as hoped most users will stay subscribed anyway, but it's important for us to have that safety net of being able to still open our files if not subscribed, even just for personal reasons. Some of the other proposals such as small fees for quick fixes etc are not appealing and miss the point.

Another approach is to award loyalty: For example, Unity subscribers have the option to own a perpetual license of Unity after two years. This also mitigates the problem of not being able to open your files later.

I call this a "real" subscription - after all, a subscription gives the subscriber something in return to own (even though it might be in the long run).

Adobe's and Scirra's rental models, however, leave you standing with nothing once you stop paying the rent. A marked difference between how Unity treats their customers, and how Scirra would treat theirs.

Aside from the fact that Unity also offers a completely free, fully functional version (well, aside from the dark GUI, I believe ).

I like the loyalty idea. Hell I'd happily sign up for 5 years if it meant that after those 5 years I was guaranteed a perpetual license for the software at the state it was in when my rental ended. My gripe with the subscription isn't the price, I think it's pretty reasonable, even cheap. But I have huge issues with the lockout. It seems unnecessary - if there was a technical reason eg it was tied up in online infrastructure it would be a different story, but from what I can gather it seems to just be a business decision. One that is really bad for users. With a couple of tweaks here and there Scirra could probably make the subscription model work and save a chunk of their clientele and I think what will tip the scales will be whether or not we're locked out of our own projects. There are many companies out there who do subs, or paid updates with some tact and respect for their users.

The problem is that no matter how amazing Construct 3 will be, it isn't worth it if you're going to lock us out of our own projects if we stop subscribing.

Think of it in different terms. An artist buys paints and a canvas and paints a beautiful picture. Because they've paid for the materials they can do whatever they want with the painting, it's theirs. They can hang it on the mantlepiece or sell it, or give it to a friend etc. I see this as kind of how Construct 2 license worked, you pay for something and then you create something with it and then it's up to you what you do with that creation.

With the new system (the way I understand it, and please correct me if I am wrong) it's more like. Scirra goes to the artist - hey I'll rent you a canvas and some paints, and you can paint a beautiful picture - and as long as you keep paying me every year you can do what you want with that. But if you ever stop, we'll take away the paints and the canvas, and we'll lock your painting in a room and you can't get it out again until you start paying us again.

This is very unfair for the users. I realise you have to be firm when you have a vision. And you have to take risks. But you absolutely don't have to remove our rights as CREATORS. It's either a huge oversight or a real dick move. No one is ever going to like the rental scheme, but it could be tailored to be acceptable by protecting users creative rights a little, a little compromise isn't a weakness it's pretty much a necessity if you're going to be successful with this.

Probably a combination of things - one being that after the reveal of it all being web only a few of the other reveals were taken as obvious, so didn't come as any surprise. Also the stigma of a subscription would be enough to put most people off. No one wants to be judged by their facebook friends for being one of the small cogs in the system responsible for the ongoing trend of software rental schemes It's like telling people you're into pyramid marketing.

I too will probably eventually jump ship. As much as I love the Construct workflow, I really think it's the best out there - there is simply no justifying the particularly narrow-minded subscription model they're proposing. If it were tweaked a bit in favour of users rights I would reconsider. But as it stands it appears to have a complete disregard for the user. Really not a good look. There are subscription models out there that protect users rights as well as developers, if Scirra aren't going to entertain these I won't entertain trying C3. I think the slow drip of information may be doing more harm than good. Unless they've got something big up their sleeve that will save it at the end, but by then it might be too late. People are already looking at other engines, myself included.

Be prepared to put in hundreds of hours of practice. A common misconception is that pixel art is "easy" but it's like any other art discipline. It's a long and sometimes frustrating road, but ultimately satisfying. Even fairly simple 16x16 sprites have a real art to them to make them look remotely good. I've found the following has helped me in my quest to become a better pixel artist. I still have a long way to go.

1. Collect a whole range of pixel art that you can look at for techniques/inspiration. Services like Pinterest are great for this as you can easily tag and catalogue any cool art you find and then you have a library to draw from.

2. Try to do a little bit each day, even if you don't feel like it. Join something like #pixeldailies where they set you a task that you have to pixel each day. It's a great way to build up practice and also a library of pixel objects.

3. Look at a lot of old games from the 8 and 16 bit era, download spritesheets of these and see how the animators set up the key frames, colour schemes etc. You can glean a lot of knowledge this way.

4. Use pixel art in instances where you normally might not. Got to do a birthday card for someone? Do it in pixel art. Need to make an animation? Pixel art. Want to paint landscapes? Pixel art.

5. Get feedback. The pixel art community are oddly fanatical, they can get hung up on traditional techniques/limitations etc and it can be frustrating. That said though, if you want to have your work dissected and brutally critiqued you've come to the right place. As hard as it is, it's a good way to get better.

6. Practice with purpose. Don't just draw heaps of things and hope to get better. Try different techniques otherwise you will hit a plateau and not improve over a certain point.

7. This one might be a bit weird, but I found that knowing how much time I've spent doing pixel art to be motivating. I do some of my pixel art in aseprite through Steam which counts the time I've been working. I find this oddly motivating seeing that I'm working more on pixel art than playing games. your mileage may vary.

Hope that helps a bit. It's a long road so just chip away at it slowly. There's no magic bullet to get better over night.

> 'd say though that if the subscription model isn't at least tweaked a bit there might be a bit of an exodus.

>

I don't think people are going to leave because Scirra introduces an engine designed for hardcore mobile game designers.

Dodge makes a Viper that is super fast with lots of frills that I could never afford or want but I still buy and love Dodge vehicles.

As long as Scirra keeps supporting and updating C2 and doesn't throw us out we will still be here and I have tried just about every engine out there and for fast design with good support for beginners and advanced users I don't think any engine beats C2 at this time.

ADDED: I do think Tom and Ashley should make it clear they will continue support and update C2 and relieve some of the fears people have and that could have been handled better with the rollout of C3. There are still issues with C2 and the website, forum and arcade that should also be addressed and fixed before a big rollout and they are working on those issues. I also think it is long past time for a 3D plugin for C2 and that is what I am waiting for.

Not everyone is interested in mobile design though. I couldn't care less about it, but then there are those to which it means everything. Everyone wants something different but they can't cater to everyone. Also, from a business perspective it would make sense to kill off support for C2 pretty quickly because if it's an attractive alternative to C3 people won't migrate. I think the main problem is that many of us who used Construct Classic or Construct 2 are now no longer in the target demographic for construct 3. It will certainly suit small studios who endlessly pump out mobile games every quarter very well so it may attract new users who have that mentality. I'll be keeping an eye on it, but will certainly be looking at other options now too.

>

> > Construct is still nothing more than a prototyping tool. I would never consider paying for a fake Multiplatform software and this insane subscription model. Even with cocoon and intel xdk you can compile you games for free. There are a lot of other alternatives to make games (not prototypes) and compile then without have to upload your files. In my opnion, there is absolutely no reason to stop using Construct 2 yet, even for mac users like me (bootcamp). Still worried about Scirras future and its awesome community anyway...

> >

>

> Yeah the forums great!

>

> We even have users that come here to inform us about other software.

>

I'm actually really impressed by scirra's extremely liberal stance on users freedom of speech around here. Most boards would close and delete if there were any early warning signs of mutiny.

They probably factored in the loss before deciding on such a controversial business model. So any detractors are people who would not have gone for the rental system anyway (probably the majority of the community looking at the posts and opinions), I'm guessing they only need a fraction of the current community to be on subscription for it to be viable. You'll be left with those who don't object to the model, a handful who'll try it out for a bit and a few who'll grumble a bit but put up with it due to customer loyalty etc. I'd say though that if the subscription model isn't at least tweaked a bit there might be a bit of an exodus.

Software comes, and software goes. There are no guarantees that software will be supported long term.

However, a rental model does have the disadvantage that if the company goes under, or decides to discontinue a product, developers run the risk to be stone-walled in the middle of a project.

Point in case: Adobe announced a couple of weeks ago that Director development and support will be ending sometime in March. Existing rentals ("subscriptions") will be cut off at that time as well.

Developers on the Adobe Director forum are not happy about this (understatement) - for example, one developer is in the middle of a project, and it will take him longer than March to finish. Others have projects done for clients (museums, for example) that must be maintained and updated after the March date.

Unfortunately, those developers who rented the software seem to be out of luck. They contacted Adobe, and asked for some lenience. But they will lose access to Director and with it lose access to their projects sometime this year.

Director first entered the market in 1985(!). The oldest surviving 'multimedia' producer is now dead. There are no guarantees for software survival. But Director users with a perpetual license may continue to use the software to open their older projects - renters ("subscribers") are at a distinct disadvantage in these type of situations.

This is a very good example of exactly what I'm afraid of. In a case like this it seems like an unnecessary and artificial limitation that just rubs salt into the wounds of loyal customers. Adobe is a big and ruthless multinational corporation that can do whatever it wants, but the price of progress doesn't need to be so high. Director was superseded long ago, and perhaps you could argue that people developing on it were foolish (although as you mentioned many kiosks in places such as museums still use director programs so it's not always an option). You expect this kind of behaviour in big business but I'm kind of disappointed the smaller guys aren't even fighting for something better.

Hard to tell without looking at what you're doing but there's a couple of things to consider. One is that if you're using multiple tilemaps are you referencing them all in the events or only the first one? Maybe you need to put them into a family and reference that family instead so that it will trigger for all the tilemaps. I just tried a quick test with a textbox outputing the value of Tilemap.PositionToTileX(player.X) and Tilemap.PositionToTileX(player.Y) and the coordinates were returned fine, but I was only using one tilemap.