Set CE Value = Element value of current element
Moderators: Flumminator, Zomis
Set CE Value = Element value of current element
There is [Element] Target and [Element] Trigger. But what if my CE has other targets and triggers defined, and I want to set CE value to the current CE's element number? Then there's no option available for me to use.
> But what if my CE has other targets and triggers defined, and I want to set
> CE value to the current CE's element number? Then there's no option
> available for me to use.
Yes; something like "[element] this" seems to be missing and could be useful.
As a workaround, you could also use the "CE delay" value and directly select the CE number there (which is not nice, but works).
> If an element changes to another element, the CE value of the original CE
> should be maintained while it is not existing anymore.
Well, this is something completely different. When a CE changes, the CE value cannot be maintained anymore, because it is not bound to a generic CE or a definition of a CE, but to the _instance_ of a CE. While the CE score is the same for all CEs of that kind, the CE value is always a different one for each instance of that CE on the playfield. If it vanishes, its CE value is lost, too. (The only solution is to store it in a different CE when the first CE changes.)
> CE value to the current CE's element number? Then there's no option
> available for me to use.
Yes; something like "[element] this" seems to be missing and could be useful.
As a workaround, you could also use the "CE delay" value and directly select the CE number there (which is not nice, but works).
> If an element changes to another element, the CE value of the original CE
> should be maintained while it is not existing anymore.
Well, this is something completely different. When a CE changes, the CE value cannot be maintained anymore, because it is not bound to a generic CE or a definition of a CE, but to the _instance_ of a CE. While the CE score is the same for all CEs of that kind, the CE value is always a different one for each instance of that CE on the playfield. If it vanishes, its CE value is lost, too. (The only solution is to store it in a different CE when the first CE changes.)
>As a workaround, you could also use the "CE delay" value and directly
>select the CE number there (which is not nice, but works).
But what if the "CE delay" value also is occupied, by the change condition?
>> If an element changes to another element, the CE value of the original
>> CE
>> should be maintained while it is not existing anymore.
>Well, this is something completely different. When a CE changes, the CE
>value cannot be maintained anymore, because it is not bound to a generic
>CE or a definition of a CE, but to the _instance_ of a CE. While the CE score
> is the same for all CEs of that kind, the CE value is always a different one
>for each instance of that CE on the playfield. If it vanishes, its CE value is
>lost, too. (The only solution is to store it in a different CE when the first CE
>changes.)
The "keep CE value after change" option is also a solution, isn't it?
>select the CE number there (which is not nice, but works).
But what if the "CE delay" value also is occupied, by the change condition?
>> If an element changes to another element, the CE value of the original
>> CE
>> should be maintained while it is not existing anymore.
>Well, this is something completely different. When a CE changes, the CE
>value cannot be maintained anymore, because it is not bound to a generic
>CE or a definition of a CE, but to the _instance_ of a CE. While the CE score
> is the same for all CEs of that kind, the CE value is always a different one
>for each instance of that CE on the playfield. If it vanishes, its CE value is
>lost, too. (The only solution is to store it in a different CE when the first CE
>changes.)
The "keep CE value after change" option is also a solution, isn't it?
> But what if the "CE delay" value also is occupied, by the change condition?
Then there's no solution I know of...
(CE actions probably really need a dedicated number gadget independently from number gadgets used for other purposes.)
> The "keep CE value after change" option is also a solution, isn't it?
Yes, if the new CE should carry over the CE value of the previous CE, than this is how to do it (if this was what Sascha meant).
Then there's no solution I know of...
(CE actions probably really need a dedicated number gadget independently from number gadgets used for other purposes.)
> The "keep CE value after change" option is also a solution, isn't it?
Yes, if the new CE should carry over the CE value of the previous CE, than this is how to do it (if this was what Sascha meant).