Update of bug #19258 (project wesnoth):
Status: Ready For Test = Fixed
Assigned to:crab = involution
Open/Closed:Open = Closed
Update of bug #19258 (project wesnoth):
Status:None = Ready For Test
___
Follow-up Comment #8:
Proposed fix in 1.12 and master:
Update of bug #19258 (project wesnoth):
Status: Postponed = None
___
Reply to this item at:
http://gna.org/bugs/?19258
___
Message sent
Update of bug #19258 (project wesnoth):
Status:None = Confirmed
Assigned to:None = crab
___
Reply to this item at:
Update of bug #19258 (project wesnoth):
Status: Confirmed = Postponed
___
Follow-up Comment #6:
as an easy way to test:
add to Den of Onis MP scenario:
[event]
name = side 1 turn 2
Follow-up Comment #7, bug #19258 (project wesnoth):
a workaround for the easy case:
just add [variables] disable_replay_corruption=yes [/variables] to the
[scenario]
(if there is at least one variable defined in scenario, the variables block
won't be overwritten by save/load/save)
Follow-up Comment #5, bug #19258 (project wesnoth):
SlowThinker wrote:
If you want to test then use Conquest Minus 3.0.14 and lower. The new
version 3.0.15 prevents the bug to take any effect.
There is another issue with 3.0.14, so please for testing use Conquest Minus
3.0.13:
Follow-up Comment #4, bug #19258 (project wesnoth):
SlowThinker wrote:
You can also test the full procedure (start a
game...save...load...save...replay) with any Conquest Minus map if you
download Conquest Minus from the 1.8 add-on server
If you want to test then use Conquest Minus 3.0.14 and
URL:
http://gna.org/bugs/?19258
Summary: Errors in replays of reloaded games - a superfluous
container
Project: Battle for Wesnoth
Submitted by: slowthinker
Submitted on: Mon Jan 9 11:30:41 2012
Category: Bug
Update of bug #19258 (project wesnoth):
Severity: 3 - Normal = 4 - Important
___
Follow-up Comment #1:
Can you nail down the how-to-reproduce a bit further please.
-If you load a replay it means you
Follow-up Comment #2, bug #19258 (project wesnoth):
I mostly tested SaveGame+MainMenu/Load/ShowReplay_checked, but the problem
seems to be identical also with SaveReplay: again the file contains the
replay_start.variables container and OOSes are reported.
how-to-reproduce:
1) Load any game,
Follow-up Comment #3, bug #19258 (project wesnoth):
By Which scenarios are affected
I mean Which scenarios have a real impact on the replay.
(It looks ANY scenario creates the replay_start.variables tag and then tries
to use these variables on the replay start.)
In case I didn't explain clearly
12 matches
Mail list logo
