What's Changed
- Fix backward compat names showing up in command overrides dropdown and add a lazy migration mechanism, by @ashishjh-bst in #2117
- undo willy-nilly filtering on dms. by @ashishjh-bst in #2118
BREAKING CHANGES FOR SELF-HOSTERS
Privacy-affecting defaults are now opt-in
Four configuration changes. Self-hosters who relied on the previous behaviour must now opt in
explicitly; nothing is removed, only the defaults changed.
-
YAGPDB_DISABLE_PREFIX_COMMANDShas been renamed toYAGPDB_ENABLE_PREFIX_COMMANDS, and
the sense is inverted. Running built-in commands through the command prefix is now off by
default; setYAGPDB_ENABLE_PREFIX_COMMANDS=trueto restore it. Custom commands are unaffected,
including those triggered by message content. If you previously set
YAGPDB_DISABLE_PREFIX_COMMANDS, that variable no longer does anything and must be replaced. -
YAGPDB_ENABLE_USERNAME_TRACKINGnow defaults to false. Username and nickname history is no
longer recorded unless you opt in, and theusernames,nicknamesandresetpastnames
commands stay disabled while it is off. ThepastUsernamesandpastNicknamescustom command
template functions return an error while disabled. Existing rows inusername_listingsand
nickname_listingsare left untouched; delete them yourself if you want the data gone. -
YAGPDB_VERIFICATION_TRACK_IPSnow defaults to false. Verification no longer records the IP
a member verified from, which also means shared-IP alt detection and the automatic banning of
alts of a banned user do not run unless you opt in. Existing rows keep their stored IPs. -
YAGPDB_ENABLE_MESSAGE_LOG_PURGEnow defaults to true. Message logs older than 30 days are
deleted automatically. Set it tofalseto retain logs indefinitely as before. If you are
upgrading an instance that has never purged, the first run will delete a large backlog, so take
a backup first if you need that history.
All of these were already as per the defaults mentioned above on yagpdb.xyz for a long long time.
Full Changelog: v2.87.1...v2.88.0