Explicit Command Option Not working #150

New Issue

2026-10-05T01:26:02+02:00

adam commented

2026-10-05 01:26:02 +02:00

Looking at the configuration of the explicit command:

require explicit command, the message will only be processed if it starts with a command word

explicitCmd = True

If that is set to true then the message must begin with a command. What I have been finding that I can embed any command in the middle of the message text and it will respond to it. Even though this setting is True. I think there is a bug here. I had to switch to using "!" prefix option for the time being..

Looking at the configuration of the explicit command: # require explicit command, the message will only be processed if it starts with a command word explicitCmd = True If that is set to true then the message must begin with a command. What I have been finding that I can embed any command in the middle of the message text and it will respond to it. Even though this setting is True. I think there is a bug here. I had to switch to using "!" prefix option for the time being..

adam closed this issue

2026-10-05 01:26:02 +02:00

adam commented

2026-10-05 01:26:03 +02:00

I don't have this same experience, interestingly, I tested this bit on mine today.

I don't have this same experience, interestingly, I tested this bit on mine today.

adam commented

2026-10-05 01:26:04 +02:00

Yes very strange. I followed the install to the letter using the script and using venv. I am running this under a proxmox LXC but shouldn't be an issue everything installs clean and runs just like a bare linux image. I had a bunch of folks test all day today and a simple statement of "I will ping you later" would cause the parser to send a response even is explicitCmd = True was set. Since I have the option set right now to prefix commands with "!" I will have to schedule more testing into the weekend when I have some free time.

Thanks for the response.

Yes very strange. I followed the install to the letter using the script and using venv. I am running this under a proxmox LXC but shouldn't be an issue everything installs clean and runs just like a bare linux image. I had a bunch of folks test all day today and a simple statement of "I will ping you later" would cause the parser to send a response even is explicitCmd = True was set. Since I have the option set right now to prefix commands with "!" I will have to schedule more testing into the weekend when I have some free time. Thanks for the response.

adam commented

2026-10-05 01:26:04 +02:00

The default behavior is to be explicit.

I did verify this is working as expected. (Could be some combo of settings but I don't expect a problem with this function it's not new code.

The default behavior is to be explicit. I did verify this is working as expected. (Could be some combo of settings but I don't expect a problem with this function it's not new code.

adam commented

2026-10-05 01:26:05 +02:00

.Ok doesn't make any sense I configured back to starts with command word, stopped and restarted the service and it's working now. I am scratching my head on this because all day when I first posted here I bounced between settings and no matter what I did the command word anywhere in the message would send a DM unless I configured !command. Oh well thanks for looking into this and replying. This is a fun project for my local area.

.Ok doesn't make any sense I configured back to starts with command word, stopped and restarted the service and it's working now. I am scratching my head on this because all day when I first posted here I bounced between settings and no matter what I did the command word anywhere in the message would send a DM unless I configured !command. Oh well thanks for looking into this and replying. This is a fun project for my local area.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshing-around#150