search

CactusDev / CactusBot

An open source, community-written service-agnostic chat bot
MIT License
30 stars 5 forks source link

v0.3.2 to develop #19

Closed RPiAwesomeness closed 8 years ago

RPiAwesomeness commented 8 years ago

v0.3.2

Alkali-Metal commented 8 years ago

So, you can no longer actually do /cry anymore due to it needing to be whispered. Well, you can do it but it will be returned in a whisper? Ooh, or make it so that /cry is the only whispered command that returns in normal chat. (If possible?)

Innectic commented 8 years ago

@Alkali-Metal: /cry responds normally already.

Alkali-Metal commented 8 years ago

But isn't there a part of the code that says whispered commands will have a whispered response. I thought I read that in the very top list thing.

2Cubed commented 8 years ago

@Alkali-Metal Yeah... /cry We could do that... and might, TBH, if Beam doesn't fix it. https://feedback.beam.pro/forums/382521-lazers-and-shiny-things/suggestions/15218871-beginning-a-non-command-message-with-a-forward-sla

2Cubed commented 8 years ago

@Innectic @Alkali-Metal: Beam currently limits /<anything> to valid /commands. You can whisper /cry to the bot and get a correct response, though.

Alkali-Metal commented 8 years ago

@2Cubed yeah, but, correct me if I'm wrong, wouldn't the part of the code that is affecting the other whispered commands also affect /cry ?

2Cubed commented 8 years ago

@Alkali-Metal Yes. If Beam keeps their current system, we can manually force that to send in public chat, even when whispered. :smile:

Alkali-Metal commented 8 years ago

@2Cubed yay! :D

Innectic commented 8 years ago

There we go. All compliant and wonderful.

2Cubed commented 8 years ago

Looks like we're good to merge. :+1: from @Innectic and @RPiAwesomeness?

Innectic commented 8 years ago

Let's get this release going :sunglasses: