Repository navigation
Replies: 32 comments 35 replies
|
A plugin that allows for dynamic filtering & highlighting of messages. This can be more extensible than we currently allow in Chatterino, applying your own logic and storing previous messages from the specific user etc |
This could be relatively easy since libcommuni defines |
|
A look into how possible Message Received event could be exposed to plugins can be found here: https://github.com/hemirt/chatterino2/tree/plugin_message_received_basic, this could be used as a starting point if anyone wants to take a look at this and implement this. Imo the best way would be to implement this first at the Irc message part (1), though this showcases possible events at building part (2). This should be in my opinion implemented first and soon, as it enables a very large portion of new possibilities.
There was not much thought put into this exact implementation (especially the lua c++ binding part), so this should be viewed only as example and to spark ideas. I just figured getting the ball rolling on usable plugin feature would be nice. An example of replacing message content is below, although something else could be done instead, e.g. custom commands such as timing out users based on messages, or highlighting messages from special users, or logic and data based ignores, timeouts, or highlights, or automatic translation of foreign languages, playing special highlight sounds...
function onMessage(message)
local content = message.content
local changed = {
content = "",
}
changed.content = "This message was replaced by the plugin"
return changed
end
c2.register_callback(c2.EventType.MessageReceived, onMessage){
"name": "Test message plugin",
"description": "Test message",
"authors": [
"hemirt"
],
"homepage": "",
"tags": [
"test",
"message"
],
"version": "0.0.1",
"license": "NO LICENSE",
"permissions": [
]
} |
Maybe. My concern is that we're tied to IRC by doing this. At some point, I can see us supporting EventSub. If we add this, we should make it very clear that users are hooking into IRC, not some generic message-received event. Furthermore, users probably want to have a way to filter messages by their channel.
That's a nice example, unfortunately, it doesn't work if the message has emotes and could throw our logic for replies off.
Although we copy left and right when building messages, we should put some thought into message APIs. The main problem I see with the current approach is that we need to copy (and transcode) the content of every incoming message. I'm no Lua expert, but from what I can tell from the Sol2 docs, usertypes allow us to define properties. By making messages a usertype, we can avoid copying stuff to Lua unless necessary. A message type could be backed by a |
That is an issue that I believe I made a mention in code, that I did not take care of this, which is why I would advocate that the easiest solution is to catch the message at the earliest, i.e. before the IRCMessage is started being further processed. content = getApp()->getPlugins()->handleMessage(content);
// what about tags or other possible things
// twitch emotes could also bug out
I don't think copying stuff hurts much, but yeah could be looked into, though if this takes long time to figure out or engineer out or takes too much code - I think it should not be prematurely overoptimized, and imo the plugins would most likely either read the message (const&) or replace the message, so maybe there's no need to overcomplicate thing, and make it read only, with some return types, i.e. isChanged, or sth.
TBH I believe rapid prototyping is much better in this instance rather than careful c++ standard committee like planning (modules? networking?). Large changes to this mechanism are going to be behind major release version anyways and there's no problem running an older version of chatterino for your plugin to work before its updated, this is not a online only game that needs to be latest version. Plugins are afterall an optionally compiled-in enabled feature anyways. And by IRC Message, obviously we can choose what parts we want and how, e.g. tags, channel, message, user, is there even anything else? There's no need for extra IRC stuff. We could also want to enable plugins to put in emotes, be they native twitch (though probably only if the user (current? or message-sender? has access to them)), third party (bttv, ffz, 7tv - enabled in chat? or any? user 7tv emotes?), or fourth party (i.e. plugin ones), or badges too - so thats another thing that could be a plugin idea - to enable plugins to register emotes with chatterino. Or disable emotes you dont like or change them, i.e. if you dont celebrate christmas, you might not want to have santa hatted emotes, that some providers change their global emotes to. There could be some thinking about whether to let the plugins register message event globally, or per channel (or even per split?), though the filtering will probably happen anyway, so there's not much difference if we do |
This really depends on what you're trying to do. From the original feature-request: "A plugin that allows for dynamic filtering & highlighting of messages." If you wanted to check whether a BTTV emote was present in the message, you'd be better off looking at the built message. If you want to filter based on IRC tags, you must see the original message. Should we do both? What if we would pass both the built message and the original IRC message to the plugin? That's what this discussion is about.
Your code currently copies the contents into Lua. My comment was that we can use usertypes to avoid copying stuff we don't need (i.e. we'd pass
Yes, we should prototype things. That's what the nightly release is about. But even in the nightly releases, we try to maintain compatibility and not break existing installations. To achieve that, we can make high-level plans on what the interface should look like. This can include prototypes like yours where we can evaluate strengths and weaknesses. We won't get the design right the first time. We have the Lua meta file (it's like TypeScript/JSdoc for Lua). A high-level design can be a snippet from a Lua meta file (maybe with some example code). That's (probably) enough to talk about the general interface and doesn't require any C++ code.
Users do use nightly versions. Not as many, but they exist. Even with major version bumps, we should be careful about compatibility with older versions. "You can just use the old version until the plugin is updated" will inevitably happen, but we should avoid it. For users, this is annoying.
They're enabled by default in CI.
Should probably be a separate comment (...so we can discuss potential designs).
This is far-fetched, but if we know that a plugin is modifying messages in a channel, we could have some visual indicator or other things (e.g. in settings). |
|
summarizing some of the previous ideas: #4885 - add buttons to profile card that can open web links #4449 - read message (tags) and play sound #2091 - replace message content (or add message) #4931 - open a websocket & populate some custom split with system messages |
|
I believe #4449 is essentially just requesting a highlight. |
|
Many of my ideas are related to what I'm missing in Chatterino, because it doesn't use GraphQL. But I think this can be implemented using plugins. Here is my list of ideas:
From the Chatterino API, the following would be required for this:
This is just what recently came to my mind. 🫠 |
|
When it comes to the list of moderators thing, you could make a website that republishes the list of moderators of willing broadcasters and then use that for
This would be nice. Honestly I wouldn't be opposed to making this a Chatterino function instead of a plugin. Modifying message context menus with the ability to tell what element was clicked is would also be nice.
I would like to be able for plugins to be able to generally modify and build messages on the level similar to our internal message elements, maybe even exposing an API for some of them.
I would actually prefer for the plugins to never be able to see the token but instead be able to perform authenticated requests on behalf of the user. This ensures that they won't just take it and send it off to wherever the author pleases.
I would actually prefer that plugins won't be able to modify our existing viewer list but would instead make their own via some kind of GUI API, maybe even using the same class but our implementation probably shouldn't need to worry about choosing a source of the viewer list.
This is probably too niche unless we decide that pseudo-guis with custom messages and abusing splits is the way we want plugins to do GUI (tbh it is quite tempting).
I'm not sure what use cases there are for this apart from getting data you sadly can't get with third-party-accessible APIs. If there are none, this might not get implemented. |
|
I converted this into an idea Adding 7TV / BetterTTV emotes using the context menu on links #5328 and also duplicated the discussion of this topic so that the discussion about the possibility of implementing this as a built-in feature in Chatterino could be continued. |
Just wanted to add, this isn't really feasible unless you're the broadcaster. The bitrate shown in the web player advanced settings comes from the video decoder, and the bitrate/stream health panel shown in the stream manager is only visible to the broadcaster's auth token over GQL. |
|
Possibly move IRC support to a plugin. We already want to have plugins be able to create messages. For this we also would need for plugins to be able to grab a channel like |
|
A few plugin ideas:
|
|
game/title change alerts (e.g., alert me when x streamer switches to y category) |
|
Chat history for a channel in the plugins channel object would be cool |
|
API Feature
Channel-specific commands or text/emote replacements. An example of this would be setting a replacement for
Another plugin feature would be a similar feature, except global replacements but this time matching specific [emoteId, emoteName] and replacing it with [emoteIds...] where emoteIds[0] > emotesId[1] > emotesId[2] > etc.
|
|
QtCreator added a C++ plugin to load Lua plugins (blog article). The source can be found here (permalink). It uses sol3 in C++. It provides the following features (also kinda applicable to Chatterino): Especially for something like GUI, sol3 seems to be easier to use than manually working with the C API of Lua, thus allows more people to contribute. |
Custom completion APIsGoal: I want to create some completion engine, mainly for custom emote completion, but current API has significant limitations
|
|
This would be breaking APIs, so getting it right would be nice.
|
|
#2091 (mentioned in #4999 (comment)) wants to build a chat translator. To do this, plugins need the ability to add rich messages (not just system messages). I'm proposing a minimal API as a start. With this API, plugins can create the same messages as the C++ code. Currently, a few things like links and images are hidden, so only text and linebreaks can be added. Plugins can't introspect or change messages once they're created. These can be future additions. I haven't implemented this in C++ yet. The following should be possible with the proposed API: c2.register_command("/hello-world", function (ctx)
local msg = c2.Message.new({
elements = {
{
type = "text",
text = "Hello,",
color = "#ff0000",
},
{
type = "text",
text = "world",
color = "#00ff00",
trailing_space = false,
},
{
type = "text",
text = "!",
color = "#0000ff",
}
},
id = "my-unique-message",
flags = c2.MessageFlag.System
})
ctx.channel:add_message(msg)
end)Type definitions---@class c2.Message
c2.Message = {}
---@class MessageInit A table to initialize a new message
---@field flags? c2.MessageFlag Message flags (see `c2.MessageFlags`)
---@field id? string The (ideally unique) message ID
---@field parse_time? number Time the message was parsed
---@field search_text? string Text to that is compared when searching for messages
---@field message_text? string The message text (used for filters for example)
---@field login_name? string The login name of the sender
---@field display_name? string The display name of the sender
---@field localized_name? string The localized name of the sender (this is used for CJK names, otherwise it's empty)
---@field username_color? string The color of the username
---@field server_received_time? number The time the server received the message
---@field highlight_color? string|nil The color of the highlight (if any)
---@field elements MessageElementInit[] The elements of the message
---@class MessageElementInitBase A base table to initialize a new message element
---@field flags? c2.MessageElementFlag Message element flags (see `c2.MessageElementFlags`)
---@field tooltip? string Tooltip text
---@field trailing_space? boolean Whether to add a trailing space after the element (default: true)
---@alias MessageColor "text"|"system"|string A color for a text element - "text" and "system" are special values that take the current theme into account
---@class (exact) TextElementInit : MessageElementInitBase A table to initialize a new message text element
---@field type "text" The type of the element
---@field text string The text of this element
---@field color? MessageColor The color of the text
---@field font_style? c2.FontStyle The font style of the text
---@class (exact) SingleLineTextElementInit : MessageElementInitBase A table to initialize a new message single-line text element
---@field type "single-line-text" The type of the element
---@field text string The text of this element
---@field color? MessageColor The color of the text
---@field font_style? c2.FontStyle The font style of the text
---@class (exact) MentionElementInit : MessageElementInitBase A table to initialize a new mention element
---@field type "mention" The type of the element
---@field display_name string The display name of the mentioned user
---@field login_name string The login name of the mentioned user
---@field fallback_color MessageColor The color of the element in case the "Colorize @usernames" is disabled
---@field user_color MessageColor The color of the element in case the "Colorize @usernames" is enabled
---@class (exact) TimestampElementInit : MessageElementInitBase A table to initialize a new timestamp element
---@field type "timestamp" The type of the element
---@field time number? The time of the timestamp (in milliseconds since epoch). If not provided, the current time is used.
---@class (exact) TwitchModerationElementInit : MessageElementInitBase A table to initialize a new Twitch moderation element (all the custom moderation buttons)
---@field type "twitch-moderation" The type of the element
---@class (exact) LinebreakElementInit : MessageElementInitBase A table to initialize a new linebreak element
---@field type "linebreak" The type of the element
---@class (exact) ReplyCurveElementInit : MessageElementInitBase A table to initialize a new reply curve element
---@field type "reply-curve" The type of the element
---@alias MessageElementInit TextElementInit|SingleLineTextElementInit|MentionElementInit|TimestampElementInit|TwitchModerationElementInit|LinebreakElementInit|ReplyCurveElementInit
---@enum c2.MessageFlag
c2.MessageFlag = {
None = 0,
System = 0,
Timeout = 0,
Highlighted = 0,
-- ...
}
---@enum c2.MessageElementFlag
c2.MessageElementFlag = {
None = 0,
Misc = 0,
Text = 0,
Username = 0,
Timestamp = 0,
-- ...
}
---@enum c2.FontStyle
c2.FontStyle = {
Tiny = {}, ---@type c2.FontStyle.Tiny
ChatSmall = {}, ---@type c2.FontStyle.ChatSmall
-- ...
}
--- Creates a new message
---
---@param init MessageInit The message initialization table
---@return c2.Message msg The new message
function c2.Message.new(init) end
---@enum c2.MessageContext Context of the message being added to a channel
c2.MessageContext = {
--- This message is the original
Original = {}, ---@type c2.MessageContext.Original
--- This message is a repost of a message that has already been added in a channel
Repost = {}, ---@type c2.MessageContext.Repost
}
--- Adds a message to the channel
---
---@param message c2.Message The message to add
---@param context? c2.MessageContext The context of the message being added
---@param override_flags? c2.MessageFlag|nil Flags to override the message's flags (some splits might filter for this)
function c2.Channel:add_message(message, context, override_flags) end |
|
I would expect the API for adding a new message element to an existing message to be the same as creating a new message from scratch. Also internally we have helpers like |
|
Since we're giving the ability to change text color dynamically, does QT support stylizing text such as bold, italicizing, underlining, etc.? |
Yes, |
|
Auto !join for Marbles On Stream. |
|
I think this leads into the wider idea of "hooks" for things like a message being received, message send etc. Can definitely see a use for hooks like that. |
|
/nuke command to timeout or ban messages sent in the last X seconds containing specific word |
|
A feed for new livestreams in a given directory/game as a channel. |
|
Now that #5997 is merged where we can allow third party browser extensions to interact with Chatterino, we could allow plugins to add custom handlers for actions (done here right now). With more APIs, plugins could support |
|
The problem is that the native messaging doesn't work on linux and there is a good bunch of code that'd need to be reworked to replace windows' apis with qt or our abstractions |
|
The messaging itself (not the attached window) isn't too platform specific, because we already use Boost.IPC. It's only the manifest location that's different for the platforms. |
|
A broadcast function (global system message) would be useful for feed/event based plugins, similar to #4931. An example use case could be a sports notifications plugin, where you'd want to see updates regardless of your selected tab. This would also be useful for displaying plugin startup messages (successes and or failures) |
|
Alternatively (probably the better option), a way to get a list of opened channels. It would cover more use cases than a global system message function, With that, events for when channels are opened and closed would probably be useful for maintaining this list in realtime without the need to rely on infined loops |
|
A plugin that will automatically refresh your token for you when it's close to expiration either with credentials set via environment variables or directly. Furthermore, it would be nice if the plugin would
|
|
Embed channel points (and its redeems) into chatterino. |
|
Embed VLC inside Chatterino, so you can open it (with streamlink) and have everything in a single window. |
|
Support for modifying to the "channel" context menu (menu where you can open stream in browser/player, etc). Personal use case would be to add similar to our "Execute command" except for messages, it'd be on the channel itself. Specifically, I would like to make a command to open a URL such as |
|
Not really a plugin idea, but I want to check if my plugin is out of date. For this, I would think of reading the Tl;dr: Support reading |
|
I would prefer if Chatterino handles version checking if that's the goal |
|
There are a few suggestions here already. To make a small overview, I made a dependency graph of the ideas and the current efforts: Graph
Sourcedigraph G {
rankdir = LR;
node [shape = box;];
subgraph cluster_emotes {
label = "Emotes"
emote [label = "c2.Emote\n(#6930)";style = filled;fillcolor = "lightgreen";];
emotemap [label = "c2.EmoteMap";];
cemoteacc [label = "Channel Emote Access";];
gemoteacc [label = "Global Emote Access";];
custom_emotes [label = "Custom Emote Providers";];
emoteintf [label = "Consolidating Emote Providers\n(#6570+)";style = filled;fillcolor = "lightgreen";];
emotemap -> cemoteacc;
emotemap -> gemoteacc;
emotemap -> custom_emotes;
emoteintf -> cemoteacc;
emoteintf -> gemoteacc;
emoteintf -> custom_emotes;
}
subgraph cluster_badges {
label = "Badges"
badge_provider[label = "Badge Providers\n(generalize how we handle badges)"];
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-14477133
cbadges [label = "Custom Badge Providers"];
emote -> cbadges;
badge_provider -> cbadges;
}
subgraph cluster_messages {
label = "c2.Message"
emoteel [label = "EmoteElement\n(#6930)";style = filled;fillcolor = "lightgreen";];
badgeel [label = "BadgeElement\n(#6930)";style = filled;fillcolor = "lightgreen";];
modbadgeel [label = "ModBadgeElement\n(#6930)";style = filled;fillcolor = "lightgreen";];
vipbadgeel [label = "VipBadgeElement\n(#6930)";style = filled;fillcolor = "lightgreen";];
ffzbadgeel [label = "FfzBadgeElement\n(#6930)";style = filled;fillcolor = "lightgreen";];
ergo_msg [label = "More Ergonomic Message Functions\n(add text with emotes and emojis etc.)";];
emote -> emotemap;
emote -> emoteel;
emote -> badgeel;
emote -> modbadgeel;
emote -> vipbadgeel;
emote -> ffzbadgeel;
}
subgraph cluster_chan_events {
label = "Channels"
# "game/title change alerts"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10116564
chan_on_stream_status_changed [label = "Channel:on_stream_status_changed";];
chan_on_joined [label = "Channel:on_joined";];
chan_on_room_modes_changed [label = "Channel:on_room_modes_changed";];
chan_on_destroyed [label = "Channel:on_destroyed\n(this is probably unsafe)";];
# "get the color of a user"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-14779372
chan_get_user_color [label = "Channel:get_user_color"];
subgraph cluster_custom_channels {
label = "Custom Channels";
# "populate custom split"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-7747236
# "feed for livestreams in directory/game as a channel"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-11988676
chan_prov [label = "Channel Providers\n(declare how a plugin channel is created)\n(#6947)";style = filled;fillcolor = "lightgreen";];
usercard_provider [label = "Usercard Info Providers";];
# "add button to profile card"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-7747236
custom_uc_fields [label = "Custom Usercard fields/menus\n(probably nice for Twitch channels too?)";];
# very loose: "access the list of viewers if not a mod"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-9120630
# very loose: "output the current bitrate in the chat title"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-9120630
chan_info_provider [label = "Channel Info Providers";];
chan_info_events [label = "Channel Info Events"];
usercard_provider -> custom_uc_fields;
chan_info_provider -> chan_info_events;
}
}
subgraph cluster_windows_split {
label = "Windows/Tabs/Splits"
win_scroll_to_msg [label = "c2.windows.scroll_to_message";];
# "savable layouts"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10112187
# "add all followed channels"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-15533398
# very loose: "apply filters to channel view"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10112187
win_modify [label = "Split/Window API (Modify)";];
}
subgraph cluster_ui_ux {
label = "UI/UX Extensions";
# hotkey to paste opened username in input box
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-14329142
hotkeys [label = "Custom Hotkeys";];
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-14025713
split_ctx [label = "SplitHeader Context Menu Items";];
# "adding 7TV / BetterTTV emotes using the context menu on links"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-9120630
# for users: "filter/highlight/hide/block/ignore/follow"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10112187
chanview_on_context_menu [label = "ChannelView Context Menu Items";];
# "dynamic filtering"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-7746245
plugin_filters [label = "Filters";];
# "highlighting of messages"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-7746245
highlights [label = "Custom Highlights";];
}
subgraph cluster_custom_ui {
label = "Custom UI"
gui_msgbox [label = "Message Boxes";];
# "prompting basic user input"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-14329142
gui_forms [label = "Declarative UI Forms\n(basic input)";];
# very loose: "regex creator"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10112187
gui_full [label = "Custom UI/Widgets";];
# "Display ... at the top of the chat as it's done on Twitch"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-9120630
gui_split_header [label = "Display below SplitHeader"];
gui_split [label = "Custom Splits"];
gui_full -> gui_split_header;
gui_full -> gui_split;
}
subgraph cluster_completion {
label = "Input"
# "CompletionRequested" not fired when typing emote with colon
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10912895
inp_completion [label="Control Input Completion Popup\n(when completing with ':')"];
# "entry object that can show icons"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10912895
inp_images [label = "Add Images to Completions"];
# "text/emote replacements"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10173688
inp_replacements [label = "Modify text before sending"];
inp_completion -> inp_images;
}
subgraph cluster_distribution {
label = "Distribution"
Plugin_Packaging [label = "Plugin Packaging";];
Plugin_Hub [label = "Plugin Hub/Repositories";];
Plugin_Packaging -> Plugin_Hub;
}
# "get the current time"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-14779372
datetime [label = "Date and Time API";];
# "read message (tags)"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-7747236
t_irc [label = "Twitch IRC parsing hooks";];
# "and play sound"
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-7747236
play_sound [label = "Play Sound/Notifications";];
# TODO: There are a lot more items at the bottom of the following comment.
# I'm not sure how well we can support this:
# https://github.com/Chatterino/chatterino2/discussions/4999#discussioncomment-10112187
}Nodes without incoming edges don't have any dependencies and could be implemented today. I left out some items where I wasn't sure how we'd go about exposing an API for them (namely VLC/external program embedding and user token refresh). Furthermore, some items need to be broken down further (like GUI). Some items also would benefit from someone proposing a Lua API for them (in a separate discussion). Then we'd have something concrete to discuss. |
|
VLC thing is probably better left to be implemented as an FFI-thing |
|
I'd love an API for prompting for basic user input. It would fill the gap nicely between commands, which can take arguments, and hotkeys which need to hardcode them. My immediate use-case is a command that brings up a text input for a username, then opens their usercard, so you can bind it to a shortcut and execute it without having to go to the message box. An interactive user input API would also compose well with the HTTP API for making more complex integrations. |
|
Hoping for API support for a custom badges plugin. |
|
One of the most frustrating things about the current UX for me is that when hopping between streams or while discovering streams, you need to manually type and open that particular stream in Chatterino. A plugin to automatically switch to a Chatterino tab with the channel that is open in the browser or create a new tab with the channel if it's not open already would be great. This friction causes me to revert back to Twitch's built-in chat for such cases. How does everyone else handle this... is there some other workaround that already exists? |
This already exists in the form of an extension: https://github.com/Chatterino/chatterino-browser-ext and by opening a "Watching tab within C2. If you decide to use this, don't forget to go to your C2 settings and look for Browser Integration, specifically you can search for "extension" and copy and paste the extension ID. I didn't know I had to do that and thought I should let you know too just in case. |
|
I had actually seen this browser extension a long time ago but based on the extension description:
It wasn't really clear what the browser ext actually did. The first point is not valid for me since I'm not on Windows and the second point is a bit technical and vague to make out. BUT, trying it now, it actually fixes the issue! Thanks for pointing me to this extension. Btw, I didn't even need to change anything in Chatterino settings to make it work - in fact, in my settings page, the option you mentioned doesn't even exist. I just installed the Firefox extension and it works without any config required. |
Oh my apologies. Forgot that the settings is there for different/local versions and not prebuilt extensions available on the respective extension stores. Glad you have it working now. |
|
I'd like to see an API to return a Example use: c2.register_command("/logs", function (ctx)
-- Usage: /logs [username] [channelname]
local msg = ("/openurl https://logs.zonian.dev/rdr/%s/%s"):format(
-- fallback to current channel's name
ctx.words[3] or ctx.channel:get_name(),
-- fallback to current user's name
ctx.words[2] or ctx.executor:get_name()
)
ctx.channel:send_message(msg, true)
end)I used Additional ideas (Added 17/11/2025):
|
|
plugin for Streamer.bot integration that makes possible to use commands for execute different actions could be cool (maybe it would be needed to do in the Streamer.bot side, they have a really good API with HTTP, UDP and WebSocket API |
|
Commands, HTTP, and WebSockets are already supported by plugins. I'm not familiar with this bot, but it looks like the UDP API is a subset of the WebSocket API, so we don't need UDP support. |
|
Nice to know, maybe add file watcher that can read a file, see changes, etc could be useful, for example if a plugin needs to read a json they can read it idk if its already supported |
|
an option to automatically add all followed channels |
|
I would love this but they'd need to solve the channel limit first, you can only be connected to so many channels in chatterino. |
|
hey, first of all, thank you for the great tool! i really enjoy using it and im very happy with it. would there perhaps be a way to support multistreaming in the future? for example, could the tiktok or youtube chat also be integrated? :) |
|
This is a use-case I'm planning to address with #6947 (and followups in the future). Idea: Plugins declare a blueprint for a channel and you can then add them in splits like you normally would. Then in the future, we can think about channels that aggregate from multiple sources (e.g. Twitch + YouTube), which was also a requested feature for Twitch alone (#4056). |
|
The plug-in for starting saving chat into the file by a command and stop doing by other command. There is a program called TwitchDownloader which can render chat from the file including emotes and badges, so preferably using compatible file structure (which is JSON by default storing data about chat message + author + emotes of the channel). The TwitchDownloader can download chat itself, but it does not work for live streams with deleted/unlisted VODs. |
and others
Uh oh!
There was an error while loading. Please reload this page.
Got an idea for a plugin that you feel like would be useful in Chatterino, but might not make sense in Chatterino itself?
Post it here - we're looking to see how the API should be designed, so getting some ideas as to what you'd like to be able to do with plugins is useful.
All reactions