Hi Craig,
could you give an example of how this script would work? I'm not sure I grasp
the potential the script might have.
I guess as a vote on this… Couldn't you put in a true/false script flag so that
it could affect summoning or not after it worked? That seems the simplest way
to me, while still keeping flexibility.
Al
-----Original Message-----
From: ian-reeds-games-bounce@xxxxxxxxxxxxx
[mailto:ian-reeds-games-bounce@xxxxxxxxxxxxx] On Behalf Of Craig Brett
(Redacted sender "craigbrett17@xxxxxxx" for DMARC)
Sent: Monday, July 20, 2015 7:00 PM
To: ian-reeds-games@xxxxxxxxxxxxx
Subject: [ian-reeds-games] after_movement script behaviour on summoning
Hi all,
One of the things I'm going to be introducing in the next dev update is
an after_movement type script event. Or did I introduce it already. I'm
not sure. Sorry!
I'm not sure how scripters would expect this to behave on a summon,
though. Since, technically, summoning does move the new unit onto the
map, so it's a movement. It's current behaviour is that a summon (or
other things that put a unit on a map) do trigger this event. However,
with it being called after_movement, should it?
Part of me thinks it shouldn't, with the caveat that if unit summons /
creations don't cause after_movement things, scripters will have to
handle those kinds of things themselves in addition to after_movement,
if they want something to happen when the unit is summoned or moves, but
it does ultimately give scripters more control.
Any thoughts?
Craig
