Follow-up Comment #4, bug #18877 (project wesnoth):
"Any time someone stores units in persisent variables and unstores them in
another game."
Yes, this makes sense.
When a camnpaign is started, the engine gives units the first time they are
created ([unit], wesnoth.put_unit, [side] leader definition) underlying_ids.
The id counter is increased by one for each new unit created and this is kept
over the course of the complete campaign so that underlying_ids are unique
(see the next_underlying_unit_id attribute in savegames) When
storing/unstoring with persistent vars from/to the same campaign there's no
problem but doing that with different campaigns lets of course the
underlying_ids collide if the counter of the other campaign is higher....
Apparently nobody thought of this usecase yet when implementing the
persistent variables and there should be no difference MP vs SP for the
matter.
Please report if you find it under ither circumstances as well.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?18877>
_______________________________________________
Nachricht geschickt von/durch Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
