Moodle plugin types: which one does your idea need?
Moodle has more than 50 plugin types. Which one fits your feature, what each can and can't touch, the usual wrong picks, and the newer AI, SMS and payment types.
Short answer: Moodle lists more than 50 plugin types, but almost every custom request we get lands in one of about ten. Pick by where the feature shows up and what it has to change. A thing students do in a course is an activity module. A box on a page is a block. A rule about who can open what is an availability condition. Anything that runs behind the scenes or adds its own pages is usually a local plugin.
Getting the type right matters more than it looks. It decides what the plugin can touch, how much it costs, and how much breaks on the next Moodle upgrade.
What is a Moodle plugin type?
Every Moodle plugin belongs to exactly one type, and the type is fixed by the folder it lives in. A block lives in /blocks, an activity in /mod, an availability condition in /availability/condition. The type gives the plugin its prefix (block_, mod_, availability_), the hooks Moodle calls, and the screens it can appear on.1
You can’t move a plugin from one type to another later without rewriting it. That is why the choice belongs at the start, before anyone writes code.
Which type fits which idea?
| You want to… | Plugin type | Example of what it does |
|---|---|---|
| Give students something to do in a course, with grades and completion | Activity module (mod) | A live seminar with session dates, group work with peer feedback |
| Show information in a box on the Dashboard or a course page | Block (block) | Work waiting to be graded, parent contacts and conduct records |
| Lock an activity until a rule is met | Availability condition (availability) | Open the next activity only after the previous one was passed, not just completed |
| Store extra facts about each user | Profile field (profilefield) | A company structure tree, a learning plan picker |
| Add a report with its own filters and exports | Report (report) | Students at risk, final grades waiting for approval |
| Run jobs, add pages, react to events, connect to another system | Local plugin (local) | Reminders after completion, a student portal sync, SMS campaigns |
| Give site admins a tool | Admin tool (tool) | A cron heartbeat alert, login time windows, workflow automation |
| Change how people log in | Authentication (auth) | Single sign-on with a university or company account |
| Change how people get into courses | Enrolment (enrol) | Enrol after an application is approved, or after payment |
| Send submissions to a checking service | Plagiarism (plagiarism) | Similarity reports shown next to each submission |
| Take payments | Payment gateway (paygw) | A card provider for paid enrolment |
| Change the look | Theme (theme) | Your colours, layout and login page |
Some types live inside other plugins. The Assignment activity takes submission plugins (assignsubmission) and feedback plugins (assignfeedback). The Quiz activity takes access rules (quizaccess) and reports. If your idea is “Assignment, but with one more step”, one of these is usually cheaper and safer than a new activity.
What are the most common wrong picks?
A new activity when a block would do. An activity module is the biggest type: it brings settings, backup and restore, grades, completion, privacy and its own tables. If the feature only shows something, a block is a fraction of the work.
A local plugin as the answer to everything. Local plugins can do almost anything, which is exactly the problem. A local plugin that changes how a course page looks is fighting Moodle instead of using the right extension point, and it tends to break on upgrades.
Theme changes for logic. We still see themes that hide buttons to stop people doing things. Hidden is not blocked. Permissions and rules belong in capabilities or an availability condition, not in CSS.
Editing core. Changing Moodle’s own files works until the next update wipes it or a security release can’t be applied. Almost every core edit we’ve been asked to make had a plugin type that does the same job.
Which plugin types are new?
Moodle keeps adding types as it grows new subsystems. The recent ones worth knowing:
- Payment gateways (
paygw), since Moodle 3.10, for paid enrolment and anything else sold through Moodle’s payment API. - TinyMCE plugins (
tiny), since 4.1, when TinyMCE replaced Atto as the default editor. Old Atto buttons need a rewrite, not a port. - Communication providers, still marked experimental, which give a course a room on an outside chat service such as Matrix and keep its members in step with the course.
- AI providers and AI placements, since 4.5. A provider connects Moodle to a model, a placement decides where the AI feature shows up for users.2
- SMS gateways, since 4.5, so any plugin can send text messages through one configured provider instead of each plugin bringing its own.3
If your idea involves AI or text messages, check these first. Before 4.5, each plugin had to carry its own API keys and its own sending code. Now a plugin can use the site’s configured provider, which is less code and one place for admins to manage keys.
How do you decide, in three questions?
- Where will people see it? Inside a course as something to do (activity), in a box (block), on its own page (local or report), in the login or enrolment flow (auth or enrol).
- Does it change a rule or just show information? Rules go in availability conditions, capabilities or enrolment. Information goes in blocks and reports.
- Does it extend something Moodle already has? Then look for a sub-plugin type first: assignment submission, quiz access rule, question type, gradebook export.
If the answers point to two types, the feature is often two small plugins, not one big one. That is normal: a report plus a block that links to it, or a local plugin that does the work plus an admin tool to configure it.
What have we built?
Across client projects since 2016 we’ve built activity modules, blocks, availability conditions, profile fields, plagiarism plugins, reports, admin tools, themes, integrations and command line scripts for moving users and grades between sites. Our public plugins are on our work page, with the code and test reports online, and the private client work is listed there by type.
Our price list shows what each type costs to build. If you’re not sure which type your idea needs, describe it in the quote form below and we’ll tell you before you pay anything.
Sources
-
Moodle developer docs, Plugin types. ↑
-
Moodle developer docs, AI subsystem. ↑
Need a Moodle plugin built or rescued?
Tell the scoping assistant what you need. You get a fixed price and a timeline in a few minutes, and an engineer reviews it within one business day.
Get a fixed quote