14.05.2011, 12:36:21
If you've followed our news for a while, you should be familiar enough with our posting pattern to recognize this will be one of those "the latest release-affecting annoyance in Ares development" posts.
A while ago, a mysterious guest submitted a mysterious patch mysteriously implementing issue #617, PowersUnit= logic for more than one vehicle a side..
The Mysterious Guest was even nice enough to provide a patch to the patch to address some issues.
Back then, I already voiced concerns about tacking on yet another activation-related feature, rather than re-designing the whole system, but due to time concerns, I scrapped the alternative branch and merged the Mystery Patch into trunk.
And people were happy.
Alas, as is often the case, there are more bugs. There seem to be special cases related to harvesters, and I'm sure the more we look, the more we'll find. I checked if the Mysterious Guest was still around, but it doesn't look like it.
What does that mean?
It means we have three choices:
A while ago, a mysterious guest submitted a mysterious patch mysteriously implementing issue #617, PowersUnit= logic for more than one vehicle a side..
The Mysterious Guest was even nice enough to provide a patch to the patch to address some issues.
Back then, I already voiced concerns about tacking on yet another activation-related feature, rather than re-designing the whole system, but due to time concerns, I scrapped the alternative branch and merged the Mystery Patch into trunk.
And people were happy.
Alas, as is often the case, there are more bugs. There seem to be special cases related to harvesters, and I'm sure the more we look, the more we'll find. I checked if the Mysterious Guest was still around, but it doesn't look like it.
What does that mean?
It means we have three choices:
- Scrap the feature. Disable it, and, should 0.3 happen, fix it up for that. That would hurt since it's a community submission and mostly done, but would require little further work before 0.2's release.
- Leave it as-is. We could just drop the feature on the community as it is, with a list of unsupported cases and known issues in the documentation. That would be the easiest and quickest solution, but also the sloppiest.
- Invest the time to fix it. Which means delaying Ares 0.2's release.
Forum Rules
(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!
(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.