https://github.com/Pupitar/RDMAss/issues/17 Add support for Auto Events. Needs testing.

To get started, you have to populate config.json with:

"auto_event": {
    "enabled": true,
    "quest_instances": ["your_quest_instances_group"],  // list of quest assignment groups to run
    "iv_instances": ["your_iv_instances_group"],  // optional list of iv assignment groups to run. If provided, those will run after provided `execution_time`.
    "execution_time": 240,  // time in minutes you want to run `iv_instances` after starting reQuest (in my case reQuest takes 4h so after 240 minutes script will auto run IV instances back)
    "time_range": [9, 10]  // only include events which start/end between those hours (including)
}

Optional options: https://github.com/Pupitar/RDMAss/blob/auto_events/default.json#L38-L65

FEATURES

• Add detailed messages for tech and user sides https://github.com/Pupitar/RDMAss/issues/6
• Use new API arg https://github.com/Pupitar/RDMAss/issues/12
• Ability to select minutes in scheduled starts.

BREAKING CHANGES

• Renamed output_channel to tech_channel in config.
• ~~All JOBS have to be re-added after a PR is merged.~~ - resvoled

User channel could be enabled by user_channel key. Messages are configurable in config tree message. Variables action, type, assignments_groups are available for all configurable messages:

• tech_channel_message_success
• tech_channel_message_fail
• user_channel_message_request
• user_channel_message_start

        let instanceName = request.param(name: "instance_name") // MARK: remove this later, use 'instance' instead
        let instance = request.param(name: "instance") ?? instanceName

Add detailed messages for tech and user sides.

BREAKING CHANGES

• Renamed output_channel to tech_channel in config.
• All JOBS have to be re-added after a PR is merged.

User channel could be enabled by user_channel key. Messages are configurable in config tree message. Variables action, type, assignments_groups are available for all configurable messages:

• tech_channel_message_success
• tech_channel_message_fail
• user_channel_message_request
• user_channel_message_start

Solves https://github.com/Pupitar/RDMAss/issues/6

I run my scans for 3 communities. Now rdmass allow me to send user_messages to 1 guilds discord users_channel. I would like the bot to be in multiple Guilds and then send the user_messages to multiple channels, spread over those different Guilds.

Hello,

As in tittle, it would be cool to display event with has_quests false so in the future we can review the event if there are any mistakes in report that event got new quests or not.

If you wanted to allow a certain discord role from a guild to be able to issue commands to rescan. Only allow certain discord roles, the ability to reQuest only specfic assignment groups ?

Example: If assignment name = xyz, allow role 12345 to issue the command Thus, If assignment name = xyz, role 0987665 can not issue the command

Or to display only certain assignments based on a role for the user issuing the command, like a role/guild check before response?

As discussed: For now I use only one restriction based on roles who can fire commands. For the thing you need you might have to create additional layer of security for commands. I would go with advanced_permissions or something where you could specify that role_id is allowed to use specified commands and list only specified assignments from them. For example:

{
    "instance": {
        "discord": {
            "enabled_roles": [1234, 2345],
            "advanced_permissions": [
                {"role_id": "2345", "enabled_methods": ["status", ...], "allowed_assignmentgroups": ["quests_one", ...]},
            ]
        }
    }
}

Differentiate between a quest assignement and a pokemon scan assignment.?

For example, if you have an assignment to start a pokemon scan and not quests, you are presented with the ReQuest button when its not needed, jut the Start is needed.

Not sure if we could add a check in there for a name varaible and show buttons based on assignment name?