Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

The Betas are slowly getting worse for some reason....

55 replies · 10,500 views · Started 10 February 2007

Assuming that all the Devs agree with introducing a CM, I volunteer. :gavel:

:computer:

:highfive:

But do you understand the situation? Like Eliwood said: "The Community Manager takes cues from the development team and presents them to the public in a way that is understandable, and goes out of his/her way to make sure the public knows what's going on development-wise." You are the one that made this thread because you didn't understand the process. So the Community Manager would have to be someone that understands that. No offense really, just explaining.

The problem stems from the fact that we don't totally know what the devs are doing, and they can't take the time to totally explain every action they make. Perhaps it's best if we simply accept the fact that the dev's are working hard, and trust them to be doing the stuff we can't directly see. I'm currently good with the alpha update box. Now that I've heard what Koopa and DD have said, I'm satisfied.

Shoelace wrote:But do you understand the situation? Like Eliwood said: "The Community Manager takes cues from the development team and presents them to the public in a way that is understandable, and goes out of his/her way to make sure the public knows what's going on development-wise." You are the one that made this thread because you didn't understand the process. So the Community Manager would have to be someone that understands that. No offense really, just explaining.

None taken, besides, you have a point. What I COULD do (again, all my suggestions are in a scenario where all the devs agree for me to... help? Can't think of a better word, other than "assist"😉 would be to gather info i.e who's working on what, any new bugs etc. If I was a CM, every week (with a 2 day margin, so every 5-9 days) I would release the status of ZC, like the changelog, but more detailed and specific, including minor stuff (not too many, mind you.)

I think that a community manager would need to have the same level of access to information that the Devs have. I have come to understand that there is a Developers only forum, the would need to have read-only access at the very least so that they can see for themselves whats going on. What they disclose will be between up to the Devs ofcourse.

Well, why not make the CM be someone who truly understands what all this is like? In my opinion, it should be Eliwood. He's been making his own program for a while now, so you KNOW he understands it all. He's the perfect candidate.

I'm far too busy to take up anything more than I am already. I was thinking of someone like ShadowTiger to take this up or possibly even jman. Who's better to do this than someone who worked on this before and is no longer working on it?

Eliwood wrote:I'm far too busy to take up anything more than I am already. I was thinking of someone like ShadowTiger to take this up or possibly even jman. Who's better to do this than someone who worked on this before and is no longer working on it?

Good point.... But you DO know what it's like. You've said so yourself.

If he is willing then Jman would be an ideal canidate, as a developer he was one of the best when it came to letting the people know what's going on...

The problem stems from the fact that we don't totally know what the devs are doing, and they can't take the time to totally explain every action they make.
That's one problem of several. Although they can, it's difficult to find reason to elaborate on what they know to be a given, and can't tell what the general public cannot. Someone who loves beer can't see why someone who has never had a beer wouldn't love it. Such a concept can be difficult to grasp for them.

Additionally, the public themselves have to do their part and have a bit of faith in the developers. Keeping a positive attitude is a must, regardless of the situation. I've heard many an analogy and complaint saying that ZC lacks direction, and that a stable version is too few and far between. I've heard it many times before, and I know you'd love nothing more than to snap it right back at me one more time, and as many times as it takes to prove your point.

It's a valid point, sure, but it's also irrelevant to ZC's progress. I've heard things like "Shadowtiger why did you stir it up again :-z" upon reinforcing the fact that we can neither see what's in the Developer forum to see its actual progress, nor the actual ratio of new additions to bug fixes.

Add that to DarkDragon's wonderful explanation of the bug-creation process (For lack of a better word. :blah: ) and Koopa's on-par reassuring words, and you've got a pretty good summary of the situation.

I think jman would be a good CM. Koopa might be the very best though. He lacks my barbed tongue and jman's cruelly mysterious attitude, (lol. We love you man. :highfive: ) and is easily one of the ... well, ... ... He's Koopa. :shrug: What else do I have to say. He's Koopa.

er, i just hope the devs have given up on the nasty surprises like the new script engine and stuff.... it was pretty annoying when during the development that they had secret stuff they where adding in that ended up being really buggy.

most secret stuff was added after beta 10b 😞

I love the betas. I love scripting, now we're not limited to what devs give us for items and the like. I like the subscreen editor, again, not just stuck with the same defaults. But there are some things that seem to have gotten out of hand. For one, what the heck happened to the string editor? It seems that it was to be improved on, when the tried and true method worked, and now we can't use it at all.

I understand what my role is as a beta tester, to test and try to find all of the bugs in order to improve the system. But can we cap the new features? I love what you've done to Zelda Classic so far. Let's not mess with a good thing.

I understand that these bugs aren't nessesarily new, they were dormant until something aggrivated them. But if we're adding things just to find the bugs, let's not, please. I feel that ZC had been improved on enough as of now. Can we please cap the new features and focus solely on fixing previous problems and bugs? There are several of us who are content with the new features. So far, there are 3 quest creators making big quests in this topic who, for some reason or another, are at a standstill. Please. Just focus on the bugs, let's leave new features alone.

Seconded. I would like to mention the Idea of the Dev forum available to the rest of us as

READ ONLY
[SIZE=2][COLOR=Black](or at least parts of it)


Read only! So the rest of us have an understanding of the stuff that goes on in more detail. That's obviously up to the Devs to decide, but I think it would prevent threads like this in the future.

[/COLOR][/SIZE]

There is absolutely no need to open up the Developer forum. Mostly there's just nothing in there of any interest to the general public, and plenty of security reasons (of the code repository, of custom quests, etc) to keep it private.

As for the CM/PR guy, you guys'll have to ask DN. My immediate thoughts though are that if public knowledge of current bugs causes this many problems, it would perhaps be best to return to private testing...

... or at least return to the beta way of releasing this. I can't hold onto B16c forever!

I see these alpha releases as a good thing. It's much easier to see that progress is being made with the faster releases. But for the people complaining, just remember, more people are NOT complaining. 😊 I enjoy access to the beta forums and don't want the 4-5 people complaining to ruin it for everyone else.

I see these alpha releases as a good thing. It's much easier to see that progress is being made with the faster releases. But for the people complaining, just remember, more people are NOT complaining. I enjoy access to the beta forums and don't want the 4-5 people complaining to ruin it for everyone else.

Seconded.........

I post bugs, not complaints, I too like seeing the current status of ZC, I like
things I can see..all the sitting and waiting drives me nuts, but now I can see
what is going on and being done. there is no need for any mediator, read the
changelog, that's what it's there for, and by the looks of things.... things are
being done. so stop complaining, and have patience 2.5 will be here
and we can all get back to work.

and I too am really involved in ZC, but really it is just a game guys...
I am too old and at times too busy to worry about such things as trivial as
complaining when something is clearly getting done.

I have been a big player of Zelda since '86 when LOZ was new, and I was
10 years old, I have played almost every Zelda almost when they came out,
and no one was probably happier than me when I discovered ZC, as I have
always wanted to update LOZ, and finally I could. and now I am waiting for
2.5 to work on my latest quest and like before I can have patience.

majoras_wrath wrote:Seconded. I would like to mention the Idea of the Dev forum available to the rest of us as

READ ONLY
[SIZE=2][COLOR=Black](or at least parts of it)


Read only! So the rest of us have an understanding of the stuff that goes on in more detail. That's obviously up to the Devs to decide, but I think it would prevent threads like this in the future.

[/COLOR][/SIZE]

in a mere minute i could easily think of problems with this approach to the developers forum.

I don't know, what would opening the Dev Forum do that the Build Box doesnt now? All you prevent is like a couple hour delay until someone updates it. Although I guess you could see the dev thought process....Oh, I don't know.

Well, in any case, if DD says that there are security reasons, keep it Dev only. The last thing any one needs right now is paranoia, and more problems.

alfinchkid wrote:I love the betas. I love scripting, now we're not limited to what devs give us for items and the like. I like the subscreen editor, again, not just stuck with the same defaults. But there are some things that seem to have gotten out of hand. For one, what the heck happened to the string editor? It seems that it was to be improved on, when the tried and true method worked, and now we can't use it at all.

I understand what my role is as a beta tester, to test and try to find all of the bugs in order to improve the system. But can we cap the new features? I love what you've done to Zelda Classic so far. Let's not mess with a good thing.

I understand that these bugs aren't nessesarily new, they were dormant until something aggrivated them. But if we're adding things just to find the bugs, let's not, please. I feel that ZC had been improved on enough as of now. Can we please cap the new features and focus solely on fixing previous problems and bugs? There are several of us who are content with the new features. So far, there are 3 quest creators making big quests in this topic who, for some reason or another, are at a standstill. Please. Just focus on the bugs, let's leave new features alone.

Times this kind of post has been made in the last month: 509

I've been counting.

I, personally, can wait as long as I need to for a stable version. I have an infinite number of things left on my list of things I can do with the tileset, and I can always just lay down combos when I get bored. I have no life otherwise, so it doesn't matter.

Petoe wrote:Whoa there Pineconn... we? When did you become a developer? O_o

Back in January. Don't you remember, the contest? With the sheep? Then I delivered the milk to the Queen of England? Hm, you must have been gone that week.

No, no, no, it's only a suggestion if and only if the most recent betas become corrupt and bad. Actually, the more I think about it, the more I hate it. 😛

DFW wrote:well as stated in many posts before: if you are making tilesets, give me graphics and I'll give you quests! XD

Amen.