Category talk:Coding Ambiguity
RE: Bug or Not Bug
- Please have the discussion here rather than spread over seperate pages.
But why not add to this section?:
- You can't use Voxels=yes on building and infantry
- You can't make air-to-air combat
Well the reason I don't do that is because those aren't cases of coding ambiguity. That's why I don't do it.
But things, which you already posted here, too?
game engine not support it only, not more.
Re: What would you prefer to label it as?
C&C game engine 2 UnSupported things - or -C&C game engine 2 conflicting things
I have to admit that, when I first saw the Mobile Factory stuff, and put it into context with the (very fitting) category name "Coding Ambiguity", I kinda thought it was good to have it written down, available for newbs, and marked it patrolled. But I also have to admit that, after reading the Bunker Barracks text, my thoughts were more into the direction of "Soooo? That's logical game behavior? Where's that a bug?".
I think the whole problem is not the description of the problems occuring, but rather their labeling as bugs. The name "Coding Ambiguity", imo, was selected very well. It's just that most of these ambiguities (like VK said similarly) appear because the game is coded to do what it does. In other words: It's the exact opposite of a bug. It's exactly the behavior intended for the functions involved, only in a situation Westwood's originally rules never created, and therefore wasn't taken into account.
Since the information given is valuable nonetheless, my suggestion is to simply remove the "bug" label. Put "Coding Ambiguity" down as a seperate kind of "code result", next to normal behavior, bugs, and crashes. Make Category:Coding Ambiguity a subcategory to Category:General Editing Information. Or Category:Miscellaneous. Since the only problem for everybody who does have a problem with these category is the "bug" description, I think that'd solve it.
Then again, as you can see from the fact that I didn't do anything "godly" yet, I'd like you guys to sort this out. Vinifera created the cat and the pages, VK disputed it, I think you guys are perfectly able to figure this one out on your own. So see this just as my two cents, not as "death from above".
~ Renegade (SysOp) 00:37, 22 August 2006 (CEST)
- Re: I'll remove the "bug" label, as in retrospect it really isn't a bug so much as it is a product of normal coding that the engine wasn't meant to handle. However, the bugs in the Weird Bugs category are very similar, since they are the result of "...seemingly normal code...". The Weird Bugs are different than coding ambiguities though, so I'd like to leave those with the bug label. As for the coding ambiguities, I will remove the bug label and move them to Category:General Editing Information, since that seems more suitable. Thanks everyone for the input! -V7
- The difference between Coding Ambiguities and Weird Bugs is, that, while both use (seemingly) normal code, in the case of Coding Ambiguities, the game does what it should do, only with an effect the modder didn't intend, while in the case of a Weird Bug, the normal code leads to inexplicable, simply "wrong" results.
- As such, there is no portion of "good will" or "liking" needed to classify Weird Bugs as bugs. If a unit starts to shoot around when deployed just because it's immune to radiation, that's a bug. Plain and simple. If a mobile factory leaves its position because the "gathering point" and the "pack up and move" command independently from each other have been coded to use the same mouse button, that's shit happening, but not a bug.