dgw

There isn't anything standardized for ACTION as far as I know, just the CTCP type we all know and love. It was also the only defined intent that I was...

Sopel definitely could have a way to send tags, but let's leave that as a separate feature discussion. It doesn't affect this deprecation at all, which only matters for incoming...

A revision of that idea: What if we add `@plugin.ctcp` and _drop_ `@plugin.intent`, since (once again) we have the perfect excuse in the form of deprecating `sopel.module`? We're already leaving...

@Exirel Added a task list to the OP as follow-up to review/discussion in #1975 and IRC. I think the `Trigger` one is the only thing that needs doing for 7.1.

Noted the updated status, and added an optional item for later (8.x) to flag use of the deprecated `trigger.tags['intent']` key if we so choose. (It'd be useful, but IMO not...

#2253 handles all the 8.0 stuff **except** for (as of writing) emitting some warning/error when a plugin tries to access the now-unpopulated `trigger.tags['intent']` field.

The point is, there won't be any `intent` tag. _Any_ access of that key is by definition trying to use obsolete behavior, so just emit a deprecation warning?

The big question, then, is whether you still think it's possible to make reloading work reasonably well for other plugin types after we start on 8.x dev and drop all...

We will worry about this in 8.0 and beyond. Reloading has been semi-broken ever since plugin types beyond single-file were introduced, well before either of us got involved with Sopel....

I'm still going to do this, but not between now and the release of 7.0. The patch won't break the current `/`-based usage, so there's no reason to rush it...