Features
Task context keys
How ModularJobs identifies action targets in task definitions.
Task contexts identify the Minecraft object or state associated with an action. They are serialized as namespaced keys in MySQL records and editor payloads so both use the same task contract.
Examples
| Context | Example key |
|---|---|
| Block material | minecraft:stone |
| Entity type | minecraft:zombie |
| Item material | minecraft:diamond |
| World | minecraft:the_nether |
| Biome | minecraft:plains |
| Plugin-owned target | myplugin:first_quest |
Built-in actions use the action and context keys accepted by the current Paper
release. A dependent plugin can register a custom action and report an arbitrary
plugin-owned context key through ActionService; the reported key must exactly
match the task record. See the API contracts
for the registration and reporting flow.