[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[SigurdFireDragon]

URL:
  

 Summary: MP campaign underyling_id collision
 Project: Battle for Wesnoth
Submitted by: sigurdfdragon
Submitted on: Wed 26 Mar 2014 04:19:38 PM UTC
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
  Item Group: Multiplayer
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Release: 1.11.12+dev
Operating System: Win 7 x64

___

Details:

In an MP campaign, this bug can cause units to not appear on the right-click
recall list, though they will still be present on the menu bar actions->recall
list.

This bug can be reproduced in the Legend of Wesmere multiplayer campaign by
doing the following:

1. Make sure shuffle sides is off. (for ease of testing)
2. Start at chapter 3 (for ease of testing)

Now in scenario Bounty Hunters
3. Recruit 3 archers
4. use debug unit moves=99 on Kalenz to get to the signpost and finish the
level.

Now in Scenario Cliffs of Thoria.
5. Recruit 3 fighters
6. Use unit moves=99 on Kalenz to immediately get to the signpost and finish
the level.

Now in scenario Battle of the Book.
7. Then look at right-click recruit and compare with menu bar actions->recruit




___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[anonymous]

Follow-up Comment #1, bug #21866 (project wesnoth):

i can reproduce this bug. In networked mp games and in local mp games.

___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[Chris Beck]

Update of bug #21866 (project wesnoth):

Severity:  3 - Normal => 5 - Blocker
  Status:None => Confirmed  

___

Follow-up Comment #2:

Since it is confirmed (I also confirmed it, Linux Mint 16 on 1.13-dev), and
since underlying_id collisions can cause big problems in unit_map and other
areas of the engine (in my limited understanding), I'm marking it "confirmed"
and upgrading to blocker. If you think this isn't serious enough to be a
blocker then feel free to downgrade.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[Daniel]

Update of bug #21866 (project wesnoth):

  Status:   Confirmed => Ready For Test 

___

Follow-up Comment #3:

fixed in 7ee5a2e074db910022075cb38cf927a54ba98d69 (1.11.12+dev). But i only
tested in local mp games.


___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[Fabian Müller]

Update of bug #21866 (project wesnoth):

 Assigned to:None => fendrin


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[Daniel]

Update of bug #21866 (project wesnoth):

  Status:  Ready For Test => Fixed  


___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #21866] MP campaign underyling_id collision

[Ignacio R. Morelle]

Update of bug #21866 (project wesnoth):

 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs