It may be the case they can use steam data for polling - in which case it is flawed as I open both classic and studio by file association so steam is never running, had both about a year, many many hours on each, yet steam states 29 mins for studio and 8 hours for classic...I actually do use studio more. If it is "end of lifed" then maybe they should consider some form of reduction for classic owners prior to a certain date who do not own studio, while ending sale of classic/make it free.

I own both steam versions and both TGC versions but I only use the TGC version of Classic. They are still selling Classic on Steam and it is currently in a Humble Bundle deal so it would be quite annoying for someone buying Classic now to find it's on the verge of being discontinued.

Perhaps a low-cost annual subscription could be an option for updates?

I've been using the VSCode extension this week and it really is a nice programming environment. I'm hoping that export options and help will be added, it would then be a possible option to replace Classic, well for me anyway.

Seeing as most people just want to code myself included end of lifing AppGameKit Classic would be a bad move. Yes its difficult maintaining two code bases but i would open source it instead of killing it off in favour of studio

I think it would be a bad move as well. Let's hope TGC listen to their customers.

hi

I use Classic version (I have both classic and studio, and buy classic two times ^^).
I have tried and It seems for windows, I can compile with studio (I have tried my big game with 75000 lines and it work fine ^^).
I don't know for android if we can compiled easily like with AppGameKit classic.

But it seems studio lake some features :
- folding (ctrl+F4)
- F1 information
- ctrl+I/Ctrl+U (increase decrease indentation)

But I could continue to code with classic (the last version) and compile for windows and android in studio.

And what about an AppGameKit classic v3 ?

Unfortunately its posts like this that hurt sales of a product as immediately people think its gonna be canned so look elsewhere, i have looked at Studio but dont need all the bells and whistles.

I hope AppGameKit continues to be updated and fixed as required as android moves at such a pace that if it doesnt it will loose relevance in a short while.

The idea of coding with the last version of Classic and then compiling with Studio would only work for so long. If new commands are added to Studio that you want to use then you would no longer be able to use Classic.

I have 4 games currently going through closed testing on Google play. I have decided not to continue publishing these games as I don't want to be in a position where to support them in the future I would have to use Studio, it just isn't a product I would choose to use in its current form. I'll continue to use Classic but anything I write will only be for personal use and for family and friends.

@zaxxan, I hope they will support classic version at least with the new android sdk updates, they have to do that for apps which are already released and listed on Google Play Store.
I hope...

I think that they will just expect everyone to 'upgrade' to Studio. It would be good to get clarification from TGC as to what their intentions are with regards to Classic.

Like Zaxxan i am looking at other options, its unfortunate that a company release wasnt put out about this instead of a nention in the last update.

Coming to this post late. I'm a Studio user so the loss of Classic doesn't affect me. It also stopped working for me on the Mac ages ago, so I stopped trying each update.

However, I'm really confused with the statements made in the very first post about it being double the work to maintain for the Mac, and that the VSCode extenion is available.

The thing is, Rick has confirmed on Discord for the last 2 updates at least that the VS Code extension isn't available/working for the Mac yet. So perhaps it's worth fixing that before scrapping Classic.

I haven't used the extension yet (I'm a Mac user) but I have a feeling if it was complete I'd probably be happy if that replaced Studio too if it meant it was easier for TGC to improve on the one product.

To be fair being a windows and linux user i didnt realise the mac version was broken, maybe finding a more robust solution that fixes it for all would be better than firing off ideas about scrapping it. After all said and done its still for sale so would leave a bad taste if it got cancelled quickly.

I really like Studios feature updates like supporting Vulkan, in fact, the only reason I still use AppGameKit Classic is for its IDE. It is simple and gives me a lot of screen space for code, and it has nice color schemes (I prefer AppGameKit Dark). I also prefer the help file system from AppGameKit Classic over the help file inside AppGameKit Studio IDE, also, I once made a tool that converted all the local files to links to the online help instead. So if you had all the nice "under the hood" stuff from AppGameKit Studio and the IDE from AppGameKit Classic, that would be really nice!

I agree with everything you have said about Classic and that's why a lot of people prefer it over Studio. I've no idea what's going on now though after Paul's announcement about discontinuing Classic. It would be good to get some official clarity on this from TGC. A new update is due any day now so perhaps things will become clearer once the update is released. At the moment I've got my fingers crossed for improvements with the VScode extension. The Studio IDE is a no go for me as a really really don't like it.

TGC should clarify that announcement fast, this is what killed BRL as a company was the lack of information and updates from the team

It's like everything and anything, we all have to move on to better things, new technologies come out all the time, this is why it's probably not supportive on Mac cause they are moving on with the times and Vulcan (the new openGl).

Same as Microsoft, windows, how many of us still use windows 98 or even 7 - it's certainly not supportive to Microsoft's Windows updates. Think of it like that. TGC doing the same thing with their software.

I know it can be difficult for many of us moving from an IDE pure code to the studio style. Without seeing it to the full. I'm sure it is backward compatible to compile our classic code but has the vulkan support plus other features. like faster running of commands.

Just frustrating to have all the additional visible features which would annoy me but won't be disheartened to at least give it a try

TGC has probably decided it's time to move on like the rest of the big software companies. They probably don't talk about their plans cause they may not feel it's necessary to do so. News travels fast and competition can be fierce if news gets into the wrong hands.

My thoughts anyway

I have always preferred Classic over Studio but this last few months I have been using VSCode and only using Studio to export to android. VScode is a really nice editor. If TGC could add an help feature and an export option it would be a good replacement for Classic.

"With AppGameKit Studio getting the VSCode extension, and the Geany IDE being open source, I'm going to recommend end of lifing AppGameKit Classic. It is getting increasingly difficult to build on Mac and basically doubles the amount of work when doing AppGameKit Studio as well."

Not sure how I missed this all this year, but it shows how often I read the update posts.

It looks like I finally need to break down and move over from Classic to Studio. As long as it supports the classic code so i can continue to play with memblock bytes, then I should be good to go.

Thanks Paul for the wonderful time I've had using Classic, and all of your hard work continually adding to the commands on top of the required third party changes. I look forward to using Studio in the near future. You rock! So, keep doing you and keep rocking with AppGameKit! We appreciate you.