[Wesnoth-bugs] [bug #23600] sighted events still unsafe (can cause OOS)

Follow-up Comment #3, bug #23600 (project wesnoth): fixed in 1.12: https://github.com/wesnoth/wesnoth/commit/00068c55b09bcaf6f63960c5a88a46f8cec49bb9 ___ Reply to this item at: __

[Wesnoth-bugs] [bug #23600] sighted events still unsafe (can cause OOS)

Update of bug #23600 (project wesnoth): Assigned to:None => gfgtdf ___ Reply to this item at: ___ Message sent

[Wesnoth-bugs] [bug #23600] sighted events still unsafe (can cause OOS)

Update of bug #23600 (project wesnoth): Open/Closed:Open => Closed ___ Reply to this item at: ___ Message sent

[Wesnoth-bugs] [bug #23600] sighted events still unsafe (can cause OOS)

Update of bug #23600 (project wesnoth): Status:None => Fixed ___ Follow-up Comment #2: Fixed in master in https://github.com/wesnoth/wesnoth/commit/5ecc629c2c3e5cd15d68e70025edeffb95f

[Wesnoth-bugs] [bug #23600] sighted events still unsafe (can cause OOS)

Follow-up Comment #1, bug #23600 (project wesnoth): Note, that there is no redoing involvd in this bug, so i think the only way to fix this bug is to forbid undoing actions before the last update shroud even if they did not uncover anything. An alternative would be to allow undoing that by default

[Wesnoth-bugs] [bug #23600] sighted events still unsafe (can cause OOS)

URL: Summary: sighted events still unsafe (can cause OOS) Project: Battle for Wesnoth Submitted by: None Submitted on: Di 19 Mai 2015 00:16:57 UTC Category: Bug Severity: 3 - No