wolph42 wrote:i have this system embedded in my framework and i know that there are other FW applying the same principle. The issue with this is that you cannot make this system agnostic.
True, but the int panel in MT isn't 100% system agnostic. That doesn't mean we shouldn't have gotten one.
In fact, it's a feature in MT that I really could not live without and it's flexible enough that most people can bend it to their will with the exception of a few really wonky systems out there.
Cause *when* would the state time counter decrease by one step?
(here one turn consists out of multiple (n)pc rounds)
- at the start of the turn
- at the end of the turn
- at the start of the initiators round
- at the end of the initiators round
- at the start of the receivers round
- at the end of the receivers round
and im probably missing a couple...
Ok, even better, add another flag.
Using my example above:
Code: Select all
[setState(state, value, id, duration, increment, execution)]
Increment Event (events that already exist in MT): On Init, On Round.
Execution: 0 for the beginning of the increment event or a 1 for the end of the increment event.
Heck, even opening up the setState TOGGLE-ON to be open-ended would make it more useful. That is, 0 would be still be off, but anything > 0 would be ON. Then we could use the ON state as a counter (wouldn't even need a duration field.) That said, once we did that, going into the expanded system I mentioned above would still be very temping.