Help with common event: Bell striking the hour in a Day/Night system

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
Hello all, I have just done a day/night system. I intended to have a bell strike the hour, so I prepped the SE into a common event and set it to parallel. It works, but I just can't get it to stop. I have enclosed a snap of the event logic so you can help me out.
20211126211512_1.jpg
 

xabileug

Veteran
Veteran
Joined
Jul 1, 2014
Messages
362
Reaction score
101
because you placed 6 or more. make it just equal to 6 and the minutes to 0.
if its parallel, then it runs on the map. you could just make the condition dong dong switch on, then switch it off
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
because you placed 6 or more. make it just equal to 6 and the minutes to 0.
if its parallel, then it runs on the map. you could just make the condition dong dong switch on, then switch it off
Can you provide me with the event logic of your solution?
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
Can you provide me with the event logic of your solution?
Please disregard, I discovered the logic. Thanks for your help. I have enclosed a screenshot of the logic in the hopes that it would help somebody.20211126215226_1.jpg
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
because you placed 6 or more. make it just equal to 6 and the minutes to 0.
if its parallel, then it runs on the map. you could just make the condition dong dong switch on, then switch it off
Two more questions: would logic like this work, and do I copy and paste for every hour, or just three times (6am, noon, and 6pm)?20211126222309_1.jpg
 

Andar

Veteran
Veteran
Joined
Mar 5, 2013
Messages
34,763
Reaction score
8,971
First Language
German
Primarily Uses
RMMV
several things.

first, I would split the event into two. One is a common event with the bell tone only, trigger=none, that is called when the sound is required - because you'll have to call that multiple times and don't want to copy the entire play se/wait sequence every time.

then you need one conditional branch for each hour where you want to call that sound
basically
if hours = 6 call bell
if hours = 7 call bell
if hours = 8 call bell

and so on (with other conditional branches for any other checks required).

and if you have your time evented (as indicated by your first common event name), then you might want to include those checks in that event as well - it will make the logic a bit more complex, but reduce the additional lag from running two parallel events for similar functions.
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
several things.

first, I would split the event into two. One is a common event with the bell tone only, trigger=none, that is called when the sound is required - because you'll have to call that multiple times and don't want to copy the entire play se/wait sequence every time.

then you need one conditional branch for each hour where you want to call that sound
basically
if hours = 6 call bell
if hours = 7 call bell
if hours = 8 call bell

and so on (with other conditional branches for any other checks required).

and if you have your time evented (as indicated by your first common event name), then you might want to include those checks in that event as well - it will make the logic a bit more complex, but reduce the additional lag from running two parallel events for similar functions.
20211127000531_1.jpg
This is the logic for the time system. is this what you mean?
 

Andar

Veteran
Veteran
Joined
Mar 5, 2013
Messages
34,763
Reaction score
8,971
First Language
German
Primarily Uses
RMMV
yes.

you should consider adding a wait(9) and changing the condition of the time count to >60 instead of >600
the wait would skip nine frames of time, resulting in one tick every ten frames instead of one tick every frame - that reduces the lag while still having the same timecount.

and then inside the conditional branch where you set minutes to zero and count up hours, you check for the hours=6 to call the bell - at that place you don't have to check for minutes as that is already done, and only have to check for the bell switch and what hour it is (after counting up the hour)
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
yes.

you should consider adding a wait(9) and changing the condition of the time count to >60 instead of >600
the wait would skip nine frames of time, resulting in one tick every ten frames instead of one tick every frame - that reduces the lag while still having the same timecount.

and then inside the conditional branch where you set minutes to zero and count up hours, you check for the hours=6 to call the bell - at that place you don't have to check for minutes as that is already done, and only have to check for the bell switch and what hour it is (after counting up the hour)
A 120 frame wait is in the common event which calls for the bell.
 

ATT_Turan

Forewarner of the Black Wind
Veteran
Joined
Jul 2, 2014
Messages
3,162
Reaction score
1,868
First Language
English
Primarily Uses
RMMV
A 120 frame wait is in the common event which calls for the bell.
That has no effect on your parallel process in post 7 (which is the point of parallel processes, they don't stop for other events).
Unless you put wait commands in that process, it's getting evaluated by the engine every frame, which is unnecessary and can contribute to the overall performance/lag of your game.
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
That has no effect on your parallel process in post 7 (which is the point of parallel processes, they don't stop for other events).
Unless you put wait commands in that process, it's getting evaluated by the engine every frame, which is unnecessary and can contribute to the overall performance/lag of your game.
wait commands in where? the common event which calls for the bell or somewhere else? if it is the latter, then where in the time system common event?
 

ATT_Turan

Forewarner of the Black Wind
Veteran
Joined
Jul 2, 2014
Messages
3,162
Reaction score
1,868
First Language
English
Primarily Uses
RMMV
wait commands in where? the common event which calls for the bell or somewhere else? if it is the latter, then where in the time system common event?
...exactly as Andar described in post 8. Change the number in your conditional to a lower value and put a wait command at the bottom.
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
...exactly as Andar described in post 8. Change the number in your conditional to a lower value and put a wait command at the bottom.

...like this?
index.php
 

ATT_Turan

Forewarner of the Black Wind
Veteran
Joined
Jul 2, 2014
Messages
3,162
Reaction score
1,868
First Language
English
Primarily Uses
RMMV
Whatever you tried to link there isn't working. Try attaching it to the post.
 

Andar

Veteran
Veteran
Joined
Mar 5, 2013
Messages
34,763
Reaction score
8,971
First Language
German
Primarily Uses
RMMV
wrong place for the wait - the wait has to be on the same level as the control variable for the count, for example as the first command in the event, above all other commands.

at this moment it is inside the count > 60 branch, which means that the branch is only executing the wait once per count - to get the same time as with your previous count of 600, the wait needs to be before the conditional
 

GumpOtaku

Villager
Member
Joined
Nov 10, 2012
Messages
12
Reaction score
2
First Language
English
Primarily Uses
wrong place for the wait - the wait has to be on the same level as the control variable for the count, for example as the first command in the event, above all other commands.

at this moment it is inside the count > 60 branch, which means that the branch is only executing the wait once per count - to get the same time as with your previous count of 600, the wait needs to be before the conditional
20211128010456_1.jpg
done.
 

Latest Threads

Latest Profile Posts

Micro rant. The worst part of working from home when you live with your family is seeing how inconsiderate they are. "Hey, you're sitting in front of your computer, that means you're not doing anything! I want to put the TV at 200 decibels!"

If I was working in the office would you still talking me like that?
It's definitely discouraging when streamers give a try-to-say-it-nicely (i.e. bad) review of your game demo. It's like jumping into a cold pool. Bad initally, but it gets better with time. And you are now more alert and see better.
Some screenshots of the pub and lodging with the beginnings of clutter taking shape
TTp8uCw.png

jtC202e.png

bSXgyVl.png

eRx9PUF.png
Backgrounds are not my strong suit... :kaodes:
DazI8jt.jpg

Just realized I forgot doing the clouds... woops
Went to get some stuff for February 10, the birthday of my favorite ink monster...
I have a little one-person party for Bendy every year, complete with the life-size plushie I made. And yes, I bake a birthday cake!

Forum statistics

Threads
118,503
Messages
1,116,438
Members
155,502
Latest member
Redcode
Top