intercal/omnibot
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Files
d56c0bf75c9ff2f3ad7b1eed8f9370a8cb159ac6
omnibot/lib/contrib/fortune.ex

32 lines
723 B
Elixir
Raw Normal View History

Initial commit with IRC and bot example. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-12 17:29:35 -04:00
defmodule Omnibot.Contrib.Fortune do
Add Omnibot.Module Modules can easily be defined with `use Omnibot.Module`. Omnibot.Contrib.Fortune has been updated to use this. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-12 18:24:11 -04:00
use Omnibot.Module
Initial commit with IRC and bot example. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-12 17:29:35 -04:00
@fortunes [
"Reply hazy, try again",
"Excellent Luck",
"Good Luck",
"Average Luck",
"Bad Luck",
"Good news will come to you by mail",
"´_ゝ`",
"ﾀ━━━━━━(ﾟ∀ﾟ)━━━━━━ !!!!",
"You will meet a dark handsome stranger",
"Better not tell you now",
"Outlook good",
"Very Bad Luck",
"Godly Luck",
]
Update modules to be more egonomic, add command macro Modules are now defined using on_{msg,channel_msg,join,part,kick}. Additionally, commands can be defined using a convenient macro. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-13 15:20:00 -04:00
command "!fortune", [to] do
fortune = Enum.random(@fortunes)
reply = "#{to}: #{fortune}"
WIP: Move Config.all_channels/0 and Config.channel_modules/1 logic into State; add State.add_loaded_module/2 The problem: When we're going through the list of modules to send messages to based on the channels they're a part of, it was being done so through the config. Since the config doesn't (and shouldn't) list all of the core modules that get included, any core modules that were loaded and running under the ModuleSupervisor would not get included in the router's attempt to send messages to a module. Now, the Config.all_channels and Config.channel_modules functions live in State, and State has a new "add_loaded_module" function where loaded modules are registered. The aforementioned moved functions will use this as the "source of truth" when deciding where to send messages for modules to handle. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-13 17:13:05 -04:00
Irc.send_to(irc, channel, reply)
Initial commit with IRC and bot example. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-12 17:29:35 -04:00
end
Update modules to be more egonomic, add command macro Modules are now defined using on_{msg,channel_msg,join,part,kick}. Additionally, commands can be defined using a convenient macro. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-13 15:20:00 -04:00
command "!fortune" do
fortune = Enum.random(@fortunes)
reply = "#{nick}: #{fortune}"
WIP: Move Config.all_channels/0 and Config.channel_modules/1 logic into State; add State.add_loaded_module/2 The problem: When we're going through the list of modules to send messages to based on the channels they're a part of, it was being done so through the config. Since the config doesn't (and shouldn't) list all of the core modules that get included, any core modules that were loaded and running under the ModuleSupervisor would not get included in the router's attempt to send messages to a module. Now, the Config.all_channels and Config.channel_modules functions live in State, and State has a new "add_loaded_module" function where loaded modules are registered. The aforementioned moved functions will use this as the "source of truth" when deciding where to send messages for modules to handle. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-13 17:13:05 -04:00
Irc.send_to(irc, channel, reply)
Initial commit with IRC and bot example. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2020-06-12 17:29:35 -04:00
end
end
Reference in New Issue Copy Permalink