Now I'm understandind nothing!
All those new CE actions!
My worst problem:
What means "CE Value"???
I will need lots of time to
understand all new options.
New Version 3.2.0 questions
Moderators: Flumminator, Zomis
New Version 3.2.0 questions
Now I'm understandind nothing!
All those new CE actions!
My worst problem:
What means "CE Value"???
I will need lots of time to
understand all new options.
Every CE in the playfield can now have a value. Example:
CE1
In "config 1": CE value = 10
Change page 1:
- when pressed by player
- change action: set CE value - 1
Change page 2:
- element changes to diamond when
- CE value gets 0
This element changes into diamond when player presses it 10 times. (First, CE value is 10. Each time the player presses it, it decreases by 1, and when it gets to 0, it changes.) You can even put more elements of this type into playfield and each of them will remember its own CE value.
CE1
In "config 1": CE value = 10
Change page 1:
- when pressed by player
- change action: set CE value - 1
Change page 2:
- element changes to diamond when
- CE value gets 0
This element changes into diamond when player presses it 10 times. (First, CE value is 10. Each time the player presses it, it decreases by 1, and when it gets to 0, it changes.) You can even put more elements of this type into playfield and each of them will remember its own CE value.
Yup, good explanation and good example!
A little remark: Try the same with "CE score" instead of "CE value", and you will immediately see the difference: This counter is not used for each single CE, but for all CEs of the same type: After pressing the 10th time, all CEs will change, not only the one that was pressed.
Update: For the above to work, do not use "CE score gets 0", but instead use "CE score gets 0 of <CE1>". Logically it should work with the above settings (as it seems to be logically exactly the same), but I just discovered that it doesn't work that way. This is because change actions in the first setting only work on single CEs, while the second one can affect more than one CE at the same time (triggered by another action). This looks like something that should be fixed, but unfortunately I just discovered that it won't be easy to fix, so you would have to use the alternative, more clumsy solution, until I have found a solution to fix this... :-/
A little remark: Try the same with "CE score" instead of "CE value", and you will immediately see the difference: This counter is not used for each single CE, but for all CEs of the same type: After pressing the 10th time, all CEs will change, not only the one that was pressed.
Update: For the above to work, do not use "CE score gets 0", but instead use "CE score gets 0 of <CE1>". Logically it should work with the above settings (as it seems to be logically exactly the same), but I just discovered that it doesn't work that way. This is because change actions in the first setting only work on single CEs, while the second one can affect more than one CE at the same time (triggered by another action). This looks like something that should be fixed, but unfortunately I just discovered that it won't be easy to fix, so you would have to use the alternative, more clumsy solution, until I have found a solution to fix this... :-/
No, it didn't work.Tomi wrote:This element changes into diamond when player presses it 10 times.
The CE disappears after pressing one times.
But, I still don't understand it:
What are the CE change actions?
What are the numers and the other things
meaning? What about the +, -, /, ...?
short:
How does all that work?
I mean:
When I make a
:-changes to
when player passes element 
I know: I have to pass the red door to get a diamond.
But I don't know what happens, when I make:
-change action: set keys -6
or so...
Maybe it's because I can't speak English very well...
But I understand enough to know, what the basic options
mean.
but more...
*sry*
It didn't work? Make sure you didn't make any mistake. I tested it in 3.2.0-8 and it worked for me.
Oh, maybe I know why pressing it once was enough. "Pressed by player" is a very tricky condition, because it lasts while you press the key, and the computer is so fast that even if you were holding the key very shortly, it will think you pressed it more times. Try using "switched" condition instead.
However, I don't know why it disappeared.
Change actions are things that happen when a changepage "activates". For example:
CE1
- [disabled checkbox] element changes to [leave this empty] when
- pressed by player
- change action: Show envelope 1
This means that when player presses the CE, envelope 1 appears (but if you didn't put any text in it on its own config page, it will be empty). The element doesn't actually change into anything else, so the checkbox next to "element changes to" should be disabled.
There are many various change actions and I think the best way to understand what they do is to try them
but I'll answer your question: "set keys" modifies which keys does the player have. Key 1 is red key, key 2 is yellow key and so on. Here, + means "add key" and - means "remove key", so, for example, "set keys + 4" does the same thing as if the player collected normal blue key.
Another example: "set gems * 2" doubles the number of gems the player needs to collect in order to win the level.
Oh, maybe I know why pressing it once was enough. "Pressed by player" is a very tricky condition, because it lasts while you press the key, and the computer is so fast that even if you were holding the key very shortly, it will think you pressed it more times. Try using "switched" condition instead.
However, I don't know why it disappeared.
Change actions are things that happen when a changepage "activates". For example:
CE1
- [disabled checkbox] element changes to [leave this empty] when
- pressed by player
- change action: Show envelope 1
This means that when player presses the CE, envelope 1 appears (but if you didn't put any text in it on its own config page, it will be empty). The element doesn't actually change into anything else, so the checkbox next to "element changes to" should be disabled.
There are many various change actions and I think the best way to understand what they do is to try them
but I'll answer your question: "set keys" modifies which keys does the player have. Key 1 is red key, key 2 is yellow key and so on. Here, + means "add key" and - means "remove key", so, for example, "set keys + 4" does the same thing as if the player collected normal blue key.
Another example: "set gems * 2" doubles the number of gems the player needs to collect in order to win the level.
I understand it!!
but it worked so:
-CE value: 10
-change page 1:
-changes to
-when value gets 0
-change page 2:
-[disabled checkbox!!!]changes to
-when pressed by player
-CE action: set CE value -1
I pressed it 10 times and it disappeared.
(Maybe myPC is too fast, so I pressed
it ca. 5-6 times only. but with rocks, or other falling
elements it should work fine!
but it worked so:
-CE value: 10
-change page 1:
-changes to
-when value gets 0
-change page 2:
-[disabled checkbox!!!]changes to
-when pressed by player
-CE action: set CE value -1
I pressed it 10 times and it disappeared.
(Maybe myPC is too fast, so I pressed
it ca. 5-6 times only. but with rocks, or other falling
elements it should work fine!
