URL:
<http://gna.org/bugs/?19120>
Summary: Bug in calculation of % of expected damage done
Project: Battle for Wesnoth
Submitted by: None
Submitted on: Mon 05 Dec 2011 09:08:18 PM UTC
Category: Bug
Severity: 2 - Minor
Priority: 5 - Normal
Item Group: None of the others
Status: None
Privacy: Public
Assigned to: None
Originator Email: [email protected]
Open/Closed: Open
Discussion Lock: Any
Release: 1.9.9/1.9.11
Operating System: OS X 10.5.8
_______________________________________________________
Details:
Note: Max has replied to my original thread on this topic
http://forums.wesnoth.org/viewtopic.php?f=4&t=35585&p=514939#p514939
He provides links to other posts mentioning this same bug, and his first link
goes to a place that links to a couple more. This has been around awhile, but
apparently it sometimes appears spontaneously (meaning without having to go
through the save-and-reload sequence I mention below).
This bug appeared three times while using Wesnoth version 1.9.9 to play the
Dead Water campaign, and once so far while using 1.9.11 to play the Hammer of
Thursagan campaign, which I've not yet completed. My computer is running Max
OS X version 10.5.8.
As you check the Statistics function while playing an official campaign, it
tells you how your actual damage inflicted compares to expected damage
inflicted. This yields four results: Your damage for the current turn;
Opponent's damage for the current turn; Your damage for the campaign to date;
and Opponent's damage for the campaign to date.
The problem is occurring in the 'Your damage for the campaign to date'
category. It starts out fine, but if you go through an intensive series of
save-and-reloads, it starts adding to the actual damage done, and the results
become meaningless. I've tried to keep track, but I really don't know how much
it adds when it goes haywire. It's certainly in excess of 1000 damage, and
might be as high as whatever the actual damage to date should have been.
There's probably a better way to explain that, but I'm not sure I can do it.
As an example, let's say I was playing Hammer of Thursagan and wanted to build
some new recruits in the third scenario, but I wanted them to have specific
attributes (fast/strong scouts and intelligent/strong thunderers). I recruit a
scout, check his attributes, discover that they don't match what I wanted,
reload and try again. At the end of filling my castle I check Statistics, and
I discover that my Damage Inflicted in the Campaign percentage has soared from
-3% to +97% without my having engaged in any combats since the last time I
checked.
The reason for the save-and-reload isn't important. I could be doing it
because I only have 30% to hit an enemy unit, and I need to hit it with all
four strikes to get past this scenario. A few save-and-reload cycles won't do
it, but when the numbers creep up toward forty or fifty, I start getting this
bad feeling. I check Statistics, and sure enough, it's happened again. Because
I only check sporadically, I have no idea exactly how many cycles are required
to trigger the bug.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?19120>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
