Crackaces -> RE: Patch 07 - Unofficial Public Beta - 1123a updated 22 January 2013 (1/24/2013 3:03:16 PM)
|
quote:
ORIGINAL: JocMeister quote:
ORIGINAL: DOCUP Playing stock Scen 1 Allied patch 22a Mar 43. My fighter sweeps are going in piecemeal. 25 operational plans with good CO's, good CO in Air HQ, great supply, Lv 8 AF, weather hasn't been a problem. They go in 12 or 13 plane groups. Before the patch they went in with ether all 25 or 20 and 3 or something close to it. Not saying anything is broken am I missing something? This has been in BETA the two times Erik and I tried it. When I reported the issue I was told a bug was found and fixed and that is what is causing this behavior. So I guess this is how its supposed to be. I realize that certain algorithums and the results of these algorithums adds to the fog of war. However, there is also the problem of identifying eroors with these algorithums when code changes. In one example, the LCU occupying a hex with LI/HI, a behaivor change happend with nobody realizing it .. until the Moose spoke up .. I am not sure that leaving the morale checks and other "fixable" variables hidden from the players is a good idea as opposed to the random variables being hidden. What if the code breaks and a skill/morale or whatever check fails and it should not have failed ... How would I know if the code was broken to report the error? Thus a balance between FOW and the fact this this game is the result of software code and software is inherrently full of faults. Maybe a combat message .. "Lt Dan fails air skill check groups fail to link up" .. or "Lt Bob fails morale check group fails to fly mission," even a message "the game has decided to randomly dispurse the mission so you will get frustrated and realize the stuff happends in war" would be helpful in identifying aberrant vs. expected software behavior. On the other hand most games do not have such a dedicated indivudal to maintain the game long after its publication. For that the community must be grateful. Just a thought . if you do want to catch more errors .. then plugging in some descriptive messages for the most controversial behaviors might be helpful in id'ing errors. .... and these messages would be helpful to the community to understand when the game is acting as designed -- lowering the number of false "bug" reports ...
|
|
|
|