Hi,

I think I just tracked down another bug for which a bugreport has been filed.
The bug itself is not why I am posting so I am not sure if I am right here.
The point is that I was able to figure this bug out because of the old, fixed moneybug's description which was somewhere around here.
I would suggest making all bugs open for the community after they've been fixed. In my opinion it is really important the testers (we) get a bit of an idea how this engine works and are able to think of new bugs which would be horrible in the final game.
I would have never thought of this bug and how to exploit (read: reproduce and test) it and so it may (not would) not have been found.

hoping that I was able to help; bye, amq

Ahhhh... I got stuck in a wormhole between sectors 5 and 13. Looks like that wasn't fixed either.

amq: It's not the same bug. It's a different bug that has the same result but happens for different reasons.

Arolte: try to get a verbose error.log file to me when you have that problem so that I can track it down more easily, please.

Hi,

I did never point out it was the same bug but the description of the old one was what make me think about a new one, successful.
And in my opinion it's agreat thing when ppl find out new bugs because that's the only way they can be fixed. That's why I suggested to make the old and fixed descriptions open to the public.

bye, amq

I'll try again tonight with verbose 8 logging, but I got a feeling it's more rare than the station stuck bug.

/me crosses fingers

amq:

Of course it's a great thing to find and report bugs. That's the whole point of the Vendetta Test, and of this forum. I hear what you are saying about discussing the bug after it is repaired. This is often done, but not in any organized fashion.

I think what amq is saying is he would like the devs to post, maybe to a sticky or a locked thread that you (FM) keep at the top of this forum, a description and maybe a little commentary about each bug as they are fixed. Not something that is open for discussion but as a reference for us, the testers.

(Correct, amq?)

Hi,

FM and RelayeR, you both are right.
At the moment bugs are discussed but is "not done in any organized fashion".
And as RelayeR said I thought that organizing it in any way that seems appropriate would be great.

Edit: Brrr... horrible english that is ... it's so early in the morning. But I hope you understand what I mean anyway

Yeah, I agree. I mean the only way to make sure a bug is dead is if we know about it after it's been fixed, so we can try to break the game again with the fixes in place. It doesn't really help if the news section or version history of the updater says, "blah blah blah bug fixed." Yeah... but how was it caused in the first place? We need more info!

=)

PS: I've been unable to get stuck in a wormhole again. Maybe it was just the server farting or something. This is gonna be a tough one to track down...

I have a fix for that getting-stuck-in-wormholes thing. I'll try it out in a little bit.

That's good to know, a1k0n!. Can a new thread be started if it works? You can post:
1) "bug"
2) status
3) any commentary you wish

Then, you and FM can keep that thread locked and bumped until you post the next bug/status/commentary.
That way, we don't have to go fishing through all the threads to find them...they'll all be right on top.

Hmm. Sure. Really, there should be a bugzilla or something like that, and then all that tracking could be accessed easily by anyone, or at least, any Vendetta tester.

Tracking bugs and tracking bugs down takes up a lot of our time, which is fine when we're actively focused on stabilizing a release but not when we're focused on a new version and maintaining two separate branches of code. Bugs which affect the production release but not the next release will tend to be ignored unless they have a serious negative impact.

This is why there hasn't been a client release in a while, even though we have had a few client crash bugs plus the "wrong bot identity" bug fixed for weeks. It basically takes up an entire evening to get a client release out the door because something always, always goes wrong.

That said, our old/new code bases aren't so significantly different; we're mainly adding stuff now. Most of the problems found in 3.3 are also problems in 3.4, so it's good to have the reports. I guess we can try to adopt a more semiformal process as RelayeR suggests.

I've seen the new reports and they are just what we need. I've been able to cross off three things on my 'to-do' list because of your posts. Thx. Now, if FM or yourself can lock them, it will prevent dummies like me from making threads out of them :D

Yeah, but I'd rather keep them open for discussion. I can always edit the original posts and delete intermediate replies.