Re: State of Zelda Classic 2.5
When I first started calling for a stable release, NONE of the problems that exist now were there then.
You've done exactly what I said would happen.
You went in and added and connected way too many pipes to the bowl, and now you've got the bowl stopped up, almost beyond repair and all your pipes are leaking uncontrollably.
Now, when you put a wrench on one pipe to stop it from leaking, the bowl is stressed to the point all the other pipes that you've repaired start leaking again.
It's now a never ending cycle of tightening pipes only to have others work loose when you do.
I hate to say it boys, but I told you so. ;)
Re: State of Zelda Classic 2.5
Oh, yeah, I edited out what I said, because it was kinda convoluted. The metaphor at least gives you an image to go on. Heh.
Re: State of Zelda Classic 2.5
Quote:
Originally Posted by
Freedom
When I first started calling for a stable release, NONE of the problems that exist now were there then.
You've done exactly what I said would happen.
You went in and added and connected way too many pipes to the bowl, and now you've got the bowl stopped up, almost beyond repair and all your pipes are leaking uncontrollably.
Now, when you put a wrench on one pipe to stop it from leaking, the bowl is stressed to the point all the other pipes that you've repaired start leaking again.
It's now a never ending cycle of tightening pipes only to have others work loose when you do.
I hate to say it boys, but I told you so. ;)
+100 for continuing the metaphor.
Re: State of Zelda Classic 2.5
Quote:
Originally Posted by
pkmnfrk
It really could take less time, so long as you had more people to help you, but considering the current activity among the devs, it may actually take longer. Or shorter. _L_'s a mad genius after all.
Perhaps when you get to the rewrite you could just dump NES consistency altogether. And you could refer to and reuse old code, clean it up, port the editor and engine to native GUI, etc...
I mean...
When you make the new bowl, you could forget about making the bowl look the same and worry entirely on all the other functions of it. Then you could take dust from the sieve and reuse it in the ceramic for the new bowl and make it match cosmetically to any table it is put on.
Re: State of Zelda Classic 2.5
A stable enough release is fine. The crashes and anything that would destroy a quest needs to fix of course. So what I mean is the big bugs are a must, but little bugs, we can live with them in my opinion. So the bowl will most likely still have cracks but at least the bowl's big holes are patched.
But the thing is, 2.5 is getting stabler than ZC has ever been. And that is awesome. But what I am worried about and kinda still am, is Large Mode. I am just thinking since Large Mode is still being made, it is going to take a lot time for you guys to finish it. Say for example you finish it in January (Large Mode), well, bugs are going to be coming from the new code so that is more bugs to deal with. I am just saying this, without Large Mode, I see ZC 2.5 being released sooner, because of the few bugs for it at this point. However, with Large Mode, I don't know how much time it is going to take as I don't know when it will be finished and what kind of bugs are going to come out of it.
And I am not saying to cancel Large Mode or anything like that. I am just saying this is the reason for the thread. I wanted a progress on what you think is going to come out of it. And thanks for replying, as I sorta have a better idea. So hopefully, all is going well with Large Mode as I want to help kill the bugs for it as soon as possible.
Also, I am the next Freedom/Peteo? If so, that is a good thing, as I look up to them a lot. XD
PS. pkmnfrk should be a new developer. *runs*
Re: State of Zelda Classic 2.5
Quote:
Originally Posted by
beefster09
It really could take less time, so long as you had more people to help you, but considering the current activity among the devs, it may actually take longer. Or shorter. _L_'s a mad genius after all.
Perhaps when you get to the rewrite you could just dump NES consistency altogether. And you could refer to and reuse old code, clean it up, port the editor and engine to native GUI, etc...
I mean...
When you make the new bowl, you could forget about making the bowl look the same and worry entirely on all the other functions of it. Then you could take dust from the sieve and reuse it in the ceramic for the new bowl and make it match cosmetically to any table it is put on.
Yeah, but the bowls original designer wanted it to be pretty instead of having lots of different compartments and stuff. Now the company he sold it to wants to completely redesign it with lots of compartments, a food processor, a mini fridge, and a back-scratcher to go with it. How do you think the bowls original designer feels? :(
I am, of course, referring to Phantom Menace and his goal of creating a stable, accurate Zelda 1 clone.
Re: State of Zelda Classic 2.5
Isn't that ZC 1.00?
I have honestly never seen such a complex bowl before. I keep thinking "This is truly the mixing bowl from hell." What an analogy... ... oy, lol.
Re: State of Zelda Classic 2.5
At this point I think we already can make a pretty damn close enough clone of The original Zelda. Now it is evolving, and I don't think the future ZC's should keep being so limited by that. If someone would what a stable LoZ clone, I guess that will be 2.5, but beyond that, it is time for something new.
Re: State of Zelda Classic 2.5
Well yeah, but it's still Phantom Menace's program. I think the devs should at least go let him know that we're gonna ditch NES consistancy, ya' know? Or, maybe we could just put 'Zelda Classic' to rest and when we rebuild it from scratch, we could call it 'Zelda Classic, But it's Not so Classic Anymore'. :tongue:
Re: State of Zelda Classic 2.5
Me? I think it may be just a little too late for ZC.
Even if a stable 2.5 could come out tomorrow, what good would it do? Honestly, think about it for a moment. To be fair, I don't keep up with you all enough to make a complete, in-depth analysis of the situation, but as an outside observer one thing is clear, and it has been clear since long before I requested my ban from PureZC: The ZC community has poisoned itself from the inside out.
How many quest projects have been abandoned by the beta wait? Is it even possible to count them all? The general mindset amongst the community of "This is a beta version, so you shouldn't use it yet, even though everything new and exciting you can only get by using this new beta" doesn't help at all either. It's not a very good environment for new ZC users, since they look at this mindset and say "Well, if I use an old version, then my project will look like an outdated piece of crap. But if I use the betas, I'll run the risk of ZC magically corrupting all my hard work and forcing me to start over. I'm just not going to bother." As such, how many users have joined ZC since the beta marathon started? Maybe more than my imagination is guessing, but certainly far less than before.
Not to mention that the community itself has all but torn itself to bits. This was partially due to the "Wait for the stable" mindset, but mostly, it was our fault as a whole. Admittedly, I'm more guilty here than anyone else, but I'm pretty sure the ZC community can't possibly hate me any more than it already does, so I'm alright with that. Above everything else, what happened is that needless, mindless disputes broke out that did nothing but divide the ZC community, and these divided parts all collapsed under their own weight. Remember the whole Z3 Scrolling fiasco? _L_ suggesting to remove Big Link? Lost Isle? All of the other countless things that flared up (Freedom, Peteo, and I all had major parts in this)?
And so what if 2.5 is stable? For most questmakers, the betas were only so interesting because they had fun and exciting new features that they wanted to try out. Well, new features stopped being added long ago, and the "Wait for the stable" mindset has already convinced these people to put their projects away into a dusty attic where they've already been covered with toxic mold and been mostly devoured by rats. The excitement of working with the new features has already faded away from most, and the shiny new label of "Stable!" isn't going to respark any interests. Once more, many people have already left the ZC community almost entirely thanks to the "Wait for the stable" mindset, and their interests have turned to other things, and they probably have things other than ZC to think about now. To them, ZC is just an old hobby that crosses their mind once in a while, and a new "stable" version isn't enough to make them want to come back. I know that I'm not coming back.
A "stable" label on a new release will do hardly anything to rekindle ZC's dying flame, and what good is code if it isn't used? You can patch up that bowl as much as you like, but the table you're going to put it down on to eat dinner is lying in burning pieces on the floor, all the food in your fridge has spoiled, and your wife has already called for Pizza.