Holger, you can add checkbox in the level configuration (level, not levelset if possible) called
Allow more than 1 change at 1 frame?
That will accept the mathematics side, and the CE-programmers side.
EDIT:
You can add this in:
1. level info (emeralds and more there will be)
2. levelset config.
3. Setup menu (not recommended)
Allow more than 1 change at 1 frame - Choice.
Moderators: Flumminator, Zomis
-
- Posts: 143
- Joined: Fri Aug 19, 2005 6:18 am
- Location: Poland
- Contact:
Allow more than 1 change at 1 frame - Choice.
GraphicsPack project: 90%
IconXT project: 100% (version final is ready)
IconXT project: 100% (version final is ready)
-
- Posts: 143
- Joined: Fri Aug 19, 2005 6:18 am
- Location: Poland
- Contact:
...
Or better:
1. Save that and add it to CEs.
2. get it global to any level with number of frames per frame
1. Save that and add it to CEs.
2. get it global to any level with number of frames per frame
GraphicsPack project: 90%
IconXT project: 100% (version final is ready)
IconXT project: 100% (version final is ready)
Well, the solution with maximal flexibility would be to let this be configured for each CE change page, but that's probably a bit too much for most people and purposes.
Besides if this would be done per level, per CE or per change page (and besides how the default behaviour would be), there are a few modes that might make sense to be configured:
- allow only one change per frame (for a CE or a specific page)
- allow more than one change per frame (for a CE or a specific page)
- do not allow any more change after this change (for a specific page)
- allow one more change after this change (for a specific page)
Currently the default is set back to "only one change per frame", but I also added a change that (starting with 3.2.0-7) there may always be two changes per frame if one of the two changes was triggered by the player.
(This is sometimes useful if a change triggered by the player prevents a "normal" non-player triggered change to take place at the same frame, maybe leaving this CE in an "undefined" (or unwanted) state after that player action.)
Besides if this would be done per level, per CE or per change page (and besides how the default behaviour would be), there are a few modes that might make sense to be configured:
- allow only one change per frame (for a CE or a specific page)
- allow more than one change per frame (for a CE or a specific page)
- do not allow any more change after this change (for a specific page)
- allow one more change after this change (for a specific page)
Currently the default is set back to "only one change per frame", but I also added a change that (starting with 3.2.0-7) there may always be two changes per frame if one of the two changes was triggered by the player.
(This is sometimes useful if a change triggered by the player prevents a "normal" non-player triggered change to take place at the same frame, maybe leaving this CE in an "undefined" (or unwanted) state after that player action.)