Basic Initial GGRequetsz Integration - Current Features:
- If enabled, requests get sent to GGRequestz for management.
- Requests that are detected during a scan are automatically marked as fulfilled in GGRequestz and users are notified in Discord the same as before.
- Manual fulfillments and rejections made in Discord are synced to GGRequestz, users are notified in Discord the same as before.
- Requests fulfilled or rejected in GGRequestz are synced to Discord when an admin runs /request_admin or a user runs /my_requests, request status is always accurate when checked.
- Requests in GGRequestz are only synced back to Discord if they originated from a Discord user.
- Requests in GGRequestz from Discord are "Requested By" the GGRequestz user that you login as in the bot env variables, Discord user is listed in request details.
Enable the following env variables:
GGREQUESTZ_ENABLED=true
GGREQUESTZ_URL=http://ip:port
GGREQUESTZ_USERNAME=your_username
GGREQUESTZ_PASSWORD=your_password
Recently Added Notification Improvements:
- Recently added game notifications now only post truly new games, even if a full scan is done in Romm or new metadata is fetched for games.
- The game's
created_atfield in Romm is checked against the scan initiation time and any game created before the current scan is ignored for notifications. - Added command to refresh recently added game notification metadata/covers, in case Romm pulls incorrect metadata or you want to upload custom metadata.
- Usage:
/refresh_recent_metadata count:nwhere n is the number of messages you want to go back and refresh, from the most recent. Default is 1, which is the most recently posted notification. - If only text is changed, the notification is edited. If covers change, the original message is deleted and a new message is posted with the new cover. This due to a Discord file attachment limitation.
Other changes:
- Logo!