It's a nice idea, but the event code for your DNS is ruggish.
[Loop]
Trigger Operation: 002: Daylight is OFF
Common Event: Wolf
Tint screen: -87, -87, -87, transition frames: 40
Trigger Operation: 002: Nighttime is ON
Wait: 999 frames.
Trigger Operation: 002: Daylight is ON
Common Event: Human
Tint Screen: 0, 0, 0, transition frames: 40
Trigger Operation: 002: Nighttime is OFF
[End Loop]
If I wait 990 frames and change the map the counter will go from the beginning again. Sorry, but I don't think this is a good tutorial, because it's not sophisticated.
@J-Crew: My DDNS was once common-event-based. It had like 10 times more commands and that in 3 different common events (so 30 times more event code) and it didn't lag. Right now I have quite a few common events and quite some scripts working during the map scene and I don't have lag. Of course I am also using an Event-Anti-Lag System.