O Ilusionista
Captain 80K
With all respect I have for you, I have to disagree with your 2 points.
This is why I suggested you to post any bugs you find at the GutHub. Its the best option. I think the devs had worked over 90% of the bugs I've reported there.
Not quite true. First, the person who posts at Facebook (in both ChronoCrash and OpenBOR pages) it's me - and I do this when I see substantial change or important fix. So the "guilt' should rest over my shoulders, not Dev's shoulders.
Second, every update comes with some explanation of what was changed and when we had work in progress/unstable additions, the devs informs this. Don't take me wrong, but I don't get your point.
About the other thing you said:
This is half true. There were some builds which more bugs than others, but if you follow the development, you will notice that some very old bugs where discovered, like HERE, HERE and HERE and some of them required a big workaround to be fixed (specially the last case). And even the 8bit support drop resulted on a serious bug, which was finally resolved.
While White Dragon was working on Damage On Landing bug, he has found some bugs on the damageonlading routine which comes from prehistoric eras and other stuff, like the wall control by script, which had an error on the core code.
Those thinigs takes time to fix, because somere very complex (dunno if you followed the Damage On Landing saga. White Dragon almost went crazy trying to fix it).
So, when I announce a release at the FB, its because that build is ready to be used. I understand your feeling, because I was waiting to upgrade my version (4432) to a newer one and it took many time. But finally they fixed it.
We have limited man power here. So I think we, more experienced users, should try to help the devs testing all the builds they made. I've even learned to complie the windows version to test and help the devs as much as I can.
People won't remember of all bugs, or to look in every post for bugs. Plus (not your case), some people doesn't knows the difference between a bug and a bad behaviour, which is caused by themselves, and tend to flood bug posts with those questions.About the new Openbor builds themself now, are two more this wrong i believe:
1. The Devs have ingnored fixing a lot of old known bugs for a long tine and instead they are adding more and more new features and new bugs. As much as i like the new features, i think that the newer Openbor builds after 4153 are more messed up than Openbor has ever been!
This is why I suggested you to post any bugs you find at the GutHub. Its the best option. I think the devs had worked over 90% of the bugs I've reported there.
2. Normally any new Openbor build should never be promoted and recommended everyware on the web for normal people when it's just released! This is wrong! Instead it should be promoted and recommended as" for developers only"(game modders) with a warrning for bugs to be expected! As for the for normal audience we should promote and recommend a well known/tested most stable Openbor build instead!
Not quite true. First, the person who posts at Facebook (in both ChronoCrash and OpenBOR pages) it's me - and I do this when I see substantial change or important fix. So the "guilt' should rest over my shoulders, not Dev's shoulders.
Second, every update comes with some explanation of what was changed and when we had work in progress/unstable additions, the devs informs this. Don't take me wrong, but I don't get your point.
About the other thing you said:
As far as i remember this was an very easy thing to fix but after that, on each new Openbor build release, there are so many more things brocken in the game plus the tons of the new Engine bugs itself!
This is half true. There were some builds which more bugs than others, but if you follow the development, you will notice that some very old bugs where discovered, like HERE, HERE and HERE and some of them required a big workaround to be fixed (specially the last case). And even the 8bit support drop resulted on a serious bug, which was finally resolved.
While White Dragon was working on Damage On Landing bug, he has found some bugs on the damageonlading routine which comes from prehistoric eras and other stuff, like the wall control by script, which had an error on the core code.
Those thinigs takes time to fix, because somere very complex (dunno if you followed the Damage On Landing saga. White Dragon almost went crazy trying to fix it).
So, when I announce a release at the FB, its because that build is ready to be used. I understand your feeling, because I was waiting to upgrade my version (4432) to a newer one and it took many time. But finally they fixed it.
We have limited man power here. So I think we, more experienced users, should try to help the devs testing all the builds they made. I've even learned to complie the windows version to test and help the devs as much as I can.