DateTrigger

DateTrigger

Original source: GitHub by N1ghtTheF0x. DateTrigger animates game objects based on local system time or VRChat server time, which makes it useful for seasonal decorations, event displays, date-gated effects, and time-aware world changes.

Check the original listing and publisher documentation for package files, install instructions, and current compatibility details. Publisher notes: UdonSharp Required.

Original Listing: GitHub SDK Note: SDK3 World, UdonSharp Documentation: DateTrigger setup notes Demo / Preview: https://vrchat.com/home/world/wrld_f842fa97-4907-43ff-8633-626beee5f92e Submitted by: N1ghtTheF0x

Category: Utility Tools

What It Does

• Uses a DateProvider component to read local or VRChat server time.
• Uses DateTrigger components to check configured date or time ranges.
• Drives an Animator parameter when the configured range is active.
• Supports local system time or networking/server time depending on the world behavior you need.
• Helps automate decorations, signs, event states, or time-based game objects.

Good Uses

Setup Review

The publisher's documentation describes a provider-and-trigger setup:

1. Create an empty GameObject for the DateProvider.
2. Add the DateProvider component and choose the time source.
3. Create another GameObject for the DateTrigger.
4. Add the DateTrigger component.
5. Assign the DateProvider object.
6. Assign the Animator and parameter that should be controlled.
7. Choose the range-check method and date/time values.
8. Test the behavior in a small scene before using it in a production world.

The publisher also notes that one DateProvider is usually enough. Avoid setups where the Animator disables the provider or trigger objects that the system needs in order to keep running.

Timing Notes

Inclusive and exclusive range checks matter for boundary times. If a range starts at 6, an inclusive check can include 6, while an exclusive check can ignore that boundary. Test the exact start and end values you plan to use, especially for event-day transitions.

Use server or networking time when players should see the same world state. Local system time can be useful for specific experiments, but it can vary between players.

Related Content

• Utility Tools
• VRC Simple String Loader
• Data Debugger
• VRChat World Creation Guide

Prefab Setup Notes

Import the prefab or script into a throwaway test scene before adding it to a live world. Confirm inspector references, ownership behavior, sync, triggers, UI hooks, and audio or object links before moving it into the production scene.

Testing Checklist

• Test once as a local player and again with a second client or late joiner if the behavior can affect more than one player.
• Confirm ownership, sync, trigger zones, UI references, and audio or object references are assigned intentionally.
• Test the exact inclusive or exclusive date/time boundaries.
• Confirm server-time behavior with a private upload when all players should see the same state.
• Check desktop and VR interaction distance so players can actually use the feature in context.
• Keep a backup of the scene before changing prefabs, UdonBehaviours, or serialized references.

Related Pages

• Utility Tools
• VRChat Prefab Hub
• UdonSharp Guide

Official References

• DateTrigger on GitHub
• DateTrigger publisher documentation
• VRChat Udon