Renegade
19.12.2009, 20:34:27
We are most certainly not going to work VK style. Definitely not. Ares is supposed to be an extension of the possibilities a modder has, not a new source of bugs and IEs.
While software is never bug-free, modders need to be able to rely on Ares being relatively stable, so they can tell their users to download it in good conscience.
Remember, end-users often don't really have a concept of code ownership, software modularization, etc. If they use a mod, and the game crashes, as far as they're concerned, it's the modder's fault and the mod sucks. It doesn't matter if that IE was Ares-induced, the modder gets the blame - because it's his mod. And the people will not stop playing "mods with Ares", they will stop playing that particular mod, because "it crashes".
So the modder needs to be relatively sure that that's not gonna happen. He has to be able to trust that Ares is not going to cause problems, sabotage his work and enrage his users.
As such, the VK code cowboy approach is an absolute no-no.
@Black Shadow 750: You are supposed to report when things work as well - so we can be sure we're done with that and close the issue. Whenever something is marked as resolved, that means we think it's resolved. It stays listed for the very reason that we need confirmation that it's actually solved and there are no problems.
Again, Operator= is a good example. That was marked as resolved, because the code in general should've worked, and then reopened because problems surfaced. We just don't have enough data so far to resolve it completely.
And it's not just reporting stuff. It's also following up and re-checking. Just because a bug is already reported doesn't mean it's not important to know if others have it as well or not. Or whether it happens under different circumstances as well. For example, if a mod reports problems with IFVs, and you have the same problem with Hover Transports, that's important to know. It makes the difference between us looking into the game's IFV handling, and us looking into general Passenger= handling.
Again, knowledge is power - the more we know about a bug, the easier it is to identify the cause and come up with a solution.
A simple "I can confirm this happens for me as well" might seem superfluous to you, but to us, it rules out that the problem is due to a local issue on the reporter's computer. (It's not a coincidence "confirmed" is a valid bug status in the tracker.)
And mt., a few times a week would already be a big help. I'll poke the man with the capital D.
Plus...as D said before, a public release isn't tooooo far away. We just can't finish the issues remaining if we don't know what's really done already and what remains, you know?
While software is never bug-free, modders need to be able to rely on Ares being relatively stable, so they can tell their users to download it in good conscience.
Remember, end-users often don't really have a concept of code ownership, software modularization, etc. If they use a mod, and the game crashes, as far as they're concerned, it's the modder's fault and the mod sucks. It doesn't matter if that IE was Ares-induced, the modder gets the blame - because it's his mod. And the people will not stop playing "mods with Ares", they will stop playing that particular mod, because "it crashes".
So the modder needs to be relatively sure that that's not gonna happen. He has to be able to trust that Ares is not going to cause problems, sabotage his work and enrage his users.
As such, the VK code cowboy approach is an absolute no-no.
@Black Shadow 750: You are supposed to report when things work as well - so we can be sure we're done with that and close the issue. Whenever something is marked as resolved, that means we think it's resolved. It stays listed for the very reason that we need confirmation that it's actually solved and there are no problems.
Again, Operator= is a good example. That was marked as resolved, because the code in general should've worked, and then reopened because problems surfaced. We just don't have enough data so far to resolve it completely.
And it's not just reporting stuff. It's also following up and re-checking. Just because a bug is already reported doesn't mean it's not important to know if others have it as well or not. Or whether it happens under different circumstances as well. For example, if a mod reports problems with IFVs, and you have the same problem with Hover Transports, that's important to know. It makes the difference between us looking into the game's IFV handling, and us looking into general Passenger= handling.
Again, knowledge is power - the more we know about a bug, the easier it is to identify the cause and come up with a solution.
A simple "I can confirm this happens for me as well" might seem superfluous to you, but to us, it rules out that the problem is due to a local issue on the reporter's computer. (It's not a coincidence "confirmed" is a valid bug status in the tracker.)
And mt., a few times a week would already be a big help. I'll poke the man with the capital D.
Plus...as D said before, a public release isn't tooooo far away. We just can't finish the issues remaining if we don't know what's really done already and what remains, you know?
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.