The Schnibble wrote:
... as part of the onCampaignLoad macro execution.
Or at any other time?
Yes. I was simplifying.
It happens whenever Wiki: setLibProperty()
is called on a Lib: token from a macro that is either (a) on the Campaign panel and the current map is not the one containing the Lib: token, or (b) on a Lib: token on a map that is not the current map and an access is made to a Lib: token on a different map.
In any case, this is fixed in tonight's build. (Wanted to get b81 out last night but RL interfered. It'll be tonight now.)
However, there are other issues. aliasmask said he had similar problems with Wiki: setProperty()
, for example. I created a test campaign in which the onCampaignLoad used Wiki: setProperty()
on an ordinary token. It functioned properly when the token was on the same map (it updated the property), when the token was on another map (it generated an error), and when the token appeared with the same name on two maps (it updated the one on the current map). No duplication occurred. I tested this with the campaign file saved with each map as the current one (since the current one is restored when a campaign is loaded and I wanted to test running oCL when the Lib: token was not on the current map).
If anyone has a campaign which demonstrates the problem for other MTscript functions, I'd like to have a copy. Please post a link where I can download it. Please reduce it to the smallest possible example that demonstrates the problem.