URL:
<http://gna.org/bugs/?20186>
Summary: [store_unit] / [unstore_unit] bug/absurdity
Project: Battle for Wesnoth
Submitted by: mrdarkunknown
Submitted on: Wed 19 Sep 2012 09:00:55 PM GMT
Category: Bug
Severity: 2 - Minor
Priority: 5 - Normal
Item Group: WML
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: All
Operating System: all
_______________________________________________________
Details:
[store_unit] absolutely uselessly stores the unit with all [advancement]s, but
when it is unstored, the unit gets all [advancements] from the [unit_type].
Therefore, there is either no reason to store [advancement]s (if you have a
lot of them, the save files may get really huge; and anyway, why would be the
[advancement]s stored inside the save file, when they are always taken from
the [unit_type]?), or [unstore_unit] is bugged. I would actually prefer if
[unstore_unit] unstored also the advancements, because editing [advancement]s
might be an useful thing. I know they can be edited by editing them in the
variable and placing the unit with [insert_tag] into the game as a new unit,
but that is not very useful, because creating a new unit cannot do a few
things [unstore_unit] can, and there is too many lua-based tags and other
things that are based on [unstore_unit]. If you decided to make [store_unit]
unable to store [advancement]s, can you please make/leave [store_unit_type] do
it?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?20186>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
