File

mod_compliance_latest: using module:log_status diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua --- a/mod_compliance_latest/mod_compliance_latest.lua +++ b/mod_compliance_latest/mod_compliance_latest.lua @@ -1,6 +1,6 @@ local success, err = pcall(function() module:depends("compliance_2023") end) if not success then - module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?") - return 1, "Error: Couldn't load dependency mod_compliance_2023." +module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" ) +return false end

---
labels:
- Stage-Alpha
summary: Install adhoc command bots in MUCs
---

# Introduction

This module allows you to "install" bots on a MUC service (via config for
now, via adhoc command and on just one MUC to follow). All the adhoc commands
defined on the bot become adhoc commands on the service's MUCs, and the bots
can send XEP-0356 messages to the MUC to send messages as any participant.

# Configuration

List all bots to install. You must specify full JID.

    adhoc_bots = { "some@bot.example.com/bot" }
	
And enable the module on the MUC service as usual

    modules_enabled = { "muc_adhoc_bots" }