lifeisunfair
Expert
Wait, what if I don't have any message
Posts: 108 
|
Post by lifeisunfair on Apr 13, 2014 13:39:54 GMT 1
There is a bug with logic that needs fixing and if fixed, it would solve all of the problems in my game. So imagine you have a button that connects to a time trigger, and the time trigger connects a toggle that locks the button. A button is not supposed to send another pulse if a time trigger is activate. But if a player steps on the time trigger the split second the time trigger ends, it sends another pulse. Even before whatever the time trigger is linked to activates. It's a split second chance for this to happen but I was thinking they could slightly increase the time of allowing no inputs on time triggers to something like (delay + 0.1). If you could implement this, it would totally fix my game. (also a hide tool would be cool- just saying!)
|
|
|
|
Post by Jatsu on Apr 13, 2014 23:38:43 GMT 1
So imagine you have a button that connects to a time trigger, and the time trigger connects a toggle that locks the button. A button is not supposed to send another pulse if a time trigger is activate. Part of your problem there is the Toggle. Assuming that your setup is exactly a Timer to a Toggle that model blocks the Timer's pressure pad, then it would be the same as a once Toggle. The Timer cannot send a new signal because it's now model blocked by the active Toggle's model enabler. But if a player steps on the time trigger the split second the time trigger ends, it sends another pulse. This is intentional. A Timer can't restart its process until both its delay and duration have finished. Also, a logic box can't change state/reactivate until ALL of its inputs have turned off*. Which means, even if a player had sat on a pressure pad for the full delay and duration of the Timer, it would not reactivate until the player had jumped off and back on. *exception with AND, which can't reactivate until at least one condition is off. The fun thing about Kogama's logic system is that it is kinda like a programming language. You can end up putting bugs in your code which cause it to not run as intended. I think that is what is happening here. |
|
lifeisunfair
Expert
Wait, what if I don't have any message
Posts: 108
|
Post by lifeisunfair on Apr 14, 2014 15:04:14 GMT 1
"A Timer can't restart its process until both its delay and duration have finished"
But it is restarting before its' duration is finished. I know this for sure because someone hits it the second the delay ends (this is the moment the cover appears) right before the duration begins.
|
|
