And before people wade in, no I am not advocating software piracy I am just asking would it be morally wrong?
Also am I alone in wishing icuurd12b42 would stop suggesting people install steam, not everybody wants to create more accounts and have more software connected to the net running in the backround.
Not morally wrong (Moral correctness is subjective), but also not intelligent. You do know that many cracks have viruses and some cracks hack the verification routine, yeah? You also should know that using a crack to access a pirated copy could install fake licenses and other persistent changes to your system and you can bet YoYo Games Support will not help you recover from utilizing a third party stolen copy of their software (That is not part of their job, and it would waste their time to analyze cracked software to see what it did).
No, you are not the only one wishing the "free" route would stop being suggested, but if you are a new user from Humble Bundle I see full well why icuurd is giving the recommendation as it will not affect your use of the program in any way since you have not used professional features yet (And probably will not encounter them before this blows over unless you actively seek to encounter them.) The only reason I wish the suggestion would go away is because I paid the Master Collection fee a long time ago and as I use professional features quite often the free version is of no use to me. I also refuse to comment out well designed code for a product I intend to sell just to cater to a free edition of a product I shelled out good cash for. I assume our reasons are different. I have been with GameMaker for over 10 years and paid each and every time for a license so that I would not need to deal with the restrictions of the free version.
icuurd, no malice towards you at all. I see the reasoning in the offer you give, it is just not valid for me (but is very valid for newcomers). So take my opinion not as a personal attack, but a defense for my stance in not using the free version and a defense for newcomers to realize, "Hey, I never used this before. I have to learn the ropes first anyway, so I might as well make my mistakes on non-production code in the free version."
I see where you are coming from but, just looking at the facts, what can really be done at this point? Your engine isn't working for you anymore. That stuff happens, not often, but it happens. Now, you have said yourself that you have been with this group for 10 years and have bought all of the licenses...so you have put in a good amount of investment into this product. I can understand your frustration easily. Still, in hindsight, with production deadlines approaching for plenty of members here, wouldn't it be wise to have a backup plan because of this sort of thing? Given your experience, I imagine that you should have come across this issue at some point. I know that in the past, at least with production cycles that I have had to deal with, my teams and I would often have LKGs not just for game files we were working on but also LKGs for the actual game engine (because even engine devs make mistakes). In a worst case scenario, we could continue being productive in an offline environment and then update to a fix once it was made. As much as I will fault YYG for what's going on, if you're a dev with something in the works, you should have done your due diligence by taking certain precautions to avoid matters like this. In my short time here, I have talked to a few devs that had backup plans in place in case this would happen. I also know that this practice was firmly ingrained in me when I first started my path to game developer-hood.
I'm not trying to play the blame game here but if you truly got the short end of the stick here, it could have been avoided. And if you find yourself having to pull a couple of all nighters to play catch up because of this, again, I understand your plight but I can't really feel bad for you. For the guys who have done any sort of professional development, this shouldn't really be a surprise. As a game developer, you need to be ready for this sort of thing because getting f***'d on a daily basis is very much the life of a game developer, even when everything you're doing is in-house. I can provide plenty of horror stories of my own along with 10x as many horror stories from my own colleagues.
tl;dr: Tough luck but what can you really do but request a refund and move onto another engine or, better yet, just practice better production STANDARDs for something that is your livelihood? Don't mean to be That Guy but that's simply the nature of the beast.
And now...here comes the flaming. I've been burned enough in this business so I'm not even going to bother putting up the flame shield for this post.