Night mode — Defendy

Set up in the Mini App

Open Settings in your private chat with @defendy_bot, select the group under My groups and check its name at the top.

Check General settings → Group time zone first.
Open Night mode and enable it. Run the first trial in a test group: enabling a saved schedule can make an existing window active immediately.
Set a start time, an end time and at least one day of the week. The current interface edits one time window.

Switches and selectors save when changed. In a separate form with a Save button, save before leaving. If a request fails, reopen the section to check its actual values.

Tip: change one option at a time and verify both closing and restoration of the group’s previous permissions.

In short

Night mode temporarily restricts sending messages according to weekly windows. It is useful for support chats, schools and scheduled communities.

How it works

Defendy interprets the current time using the timezone from General settings.
On selected weekdays it compares that time with the configured start and end.
The scheduler requests restriction inside the window and restoration of the saved permissions afterward. A saved setting or command acknowledgement does not prove that Telegram has already changed permissions; verify both transitions.

Night mode restricts messages, media, polls, reactions and member invitations. It does not control Telegram slow mode or lift separate personal mutes when the group reopens.

Every setting explained

Enable night mode

Default: Off.

Turns scheduled permission changes on.

The current WebApp reads the group-wide timezone from General settings. Its picker offers whole-hour offsets from UTC−12 through UTC+12. A fixed offset does not follow seasonal clock changes automatically; review it when your region changes clocks. Use the group’s agreed time rather than the administrator’s current device location.

Windows

Default: Mon-Sun 23:00-07:00.

The current WebApp edits one weekly window with start and end times in HH:MM. A start later than the end means the window crosses midnight; equal times are rejected.

Days

Default: All days.

Weekdays on which a window starts. For example, Friday 23:00–07:00 runs into Saturday morning. The editor requires at least one selected day.

Practical example

For a local community, select the real group timezone and set Monday–Sunday, 23:00–07:00. Test once with a short nearby window before relying on the overnight schedule.

Recommendations

Only one window is currently editable in the WebApp; multiple-window scheduling is not exposed.
Use the group's real local timezone; otherwise the mode will feel random to members.

Troubleshooting

Check that Defendy is still an administrator in the group.
Refresh the settings panel and make sure you are editing the correct group.
If a setting is saved but does not work, check the bot permissions in Telegram.
Test with an ordinary member without administrator privileges or configured boost-based exemptions.
Compare permissions before closing and after reopening. Preserve any pre-existing content restrictions.
Review relevant events if you configured logging for them. A missing log entry does not establish that the transition succeeded.

For a safe new cycle, the current implementation checks the bot’s rights to change group information, invite users, pin messages and restrict members. Managing topics is also required when that ability is enabled in the state being preserved. Address the specific missing rights reported by the bot rather than granting every permission indiscriminately. Recheck whether the module remains enabled afterward: missing required rights can disable new cycles.

Stop the schedule

Turn the module off in settings or use /nightmode off with the required authority. The command disables scheduling and requests permission restoration; it will not enable itself tomorrow. Verify that permissions actually return.

If restoration fails, an authorized administrator can restore the recorded permissions manually in Telegram. Coordinate the team and watch for deferred restoration, which can also change permissions. See the group opening-hours guide for a test and fallback plan.

Checked on 5 October 2026 against the interface and current implementation. Scheduling is implemented; this page does not report a live test of a particular production group.