Problems

Every issue in the Problems pane has a code that links to its explanation below. Errors prevent the mod from generating, while warnings highlight behavior that may not work as expected or could hurt server performance.

Project and target

MM101 Owner handle

Error. The project is missing an owner handle, or its handle isn’t valid in a Java package name. Reopen the project from the Projects page so makemods.app can assign it automatically.

MM102 Mod ID

Error. The mod ID must be 2 to 64 characters long, start with a lowercase letter, use only lowercase letters, digits, and _, and avoid Java keywords or reserved names like minecraft and forge. Choose a different mod ID in Project Settings.

MM103 Mod version

Error. The mod version must start with a digit and contain only letters, digits, ., +, _, and - (for example, 1.0.0).

MM104 Target

Error. The project targets an unsupported Minecraft version or mod loader. Select one of the supported targets in Project Settings.

MM105 Not supported on this target

Error. This node type isn’t available on the project’s current target (for example, Java code on Bedrock Edition). Remove the node or switch to a target that supports it.

MM106 Fallback on older release

Warning. The selected Minecraft version or loader doesn’t support a feature used by this node, so the generator falls back to the alternative mentioned in the message. Switch to a newer target if you need the full behavior. Java code nodes aren’t converted automatically across versions or loaders: make sure your custom code uses the class and method names for the selected target.

MM107 Biome not in release

Error. A referenced biome or biome tag doesn’t exist in the target Minecraft version. For example, Fabric versions before 1.21 don’t include c: biome tags; use minecraft: tags or individual biome IDs instead.

MM108 Bedrock Edition limitation

Warning. Bedrock Edition doesn’t support part of what this node configures, such as modifying vanilla chest loot, adding drops to vanilla mobs without replacing their loot table, applying the glowing effect, showing item lore, using non-cube block shapes, or canceling events other than hits, block breaks, clicks, and item uses. Adjust or remove the unsupported setting.

Properties

MM201 Missing required property

Error. A required property (marked !) is empty, such as a recipe’s result or an event’s target list. Fill in the property, or wire the corresponding input port where supported (such as on Give item or a creative tab icon).

MM202 Wrong value type

Error. A property holds the wrong type of value, such as text where a number is expected. Enter a value matching the expected type.

MM203 Invalid ID

Error. An ID property must start with a lowercase letter and contain only lowercase letters, digits, and _ (for example, ruby_sword).

MM204 Invalid color

Error. Color values must use six-digit hex format, such as #ff8800.

MM205 Value out of range

Error. A number falls outside the allowed range for that property (such as a max stack size of 100). Set a value within the range shown in the message.

MM206 Missing texture

Error. An image property points to a texture that isn’t in the project or isn’t a valid PNG. Choose an existing texture from the project or clear the property.

MM207 Invalid option

Error. A dropdown property is set to an unrecognized option. Choose one of the available options.

MM208 Invalid list entries

Error. A list property has too many rows, or one of its rows contains an out-of-range value or invalid option. Remove extra rows or fix the row mentioned in the message.

MM209 Invalid reference

Error. A property references an incompatible node type, an unknown vanilla ID, or lists the same entry more than once. Choose valid nodes or vanilla IDs without duplicates.

MM210 Invalid tag

Error. Tags must be written in lowercase namespace:path format without a leading # (for example, c:gems/ruby) and listed only once.

MM211 Invalid biomes

Error. A biome list (on a mob spawn, ore block, or Biome is node) is empty, contains an unknown biome, or mixes biome tags with individual biome IDs. Specify either a single biome tag like #minecraft:is_forest or one or more vanilla biome IDs like plains, forest.

MM212 Minimum above maximum

Error. A minimum value is higher than its corresponding maximum (such as block XP, ore generation height, drop counts, or mob group size). Make sure the minimum is less than or equal to the maximum.

MM213 Duplicate ID

Error. Two nodes share the same ID within the same registry. Items, blocks, and mob spawn eggs (<id>_spawn_egg) share one namespace, while creative tabs, mobs, and materials each have their own. Similarly, only one Translations node may target a given language; merge duplicate language entries into a single node or rename one of the conflicting IDs.

Wires and flow

MM301 Required input not wired

Error. A required input port (marked !), such as the condition on If, has nothing wired into it. Connect a compatible output port.

MM302 Too many wires

Error. Multiple wires connect to a single-value input port. Keep only one wire.

MM303 Invalid connection

Error. A wire connects nonexistent or incompatible ports, creates a flow loop, or makes a value depend on itself. Remove the wire or connect matching port types.

MM304 Ignored input

Warning. An input port is wired up, but the node’s current settings ignore it (for example, wiring Player on Send message when To is set to Everyone). Remove the wire or change the setting so the input is used.

MM305 Unreachable step

Warning. No event or function leads to this action, so it will never run. Connect an event’s then port to it (directly or through earlier steps), or delete the node.

MM306 Value from a different event

Error. A step reads a value output from an event that doesn’t trigger that step. Only wire event values into steps that run inside that event’s flow.

MM307 Missing context input

Error. A Player, Entity, World, or Position input is left unwired, and the triggering event or function doesn’t provide one automatically (such as a Position input under When player joins). Wire a value into the port.

MM308 Dynamic value wired into static content

Error. A runtime value node (such as Select or Java code) is wired into a static content or recipe node. Value nodes can only connect to steps and other value nodes.

MM309 Identical branches

Warning. Every branch of an If, Java code, or function call leads to the same steps, making the branch redundant. Wire each branch to different steps, or bypass the branch node.

MM310 Unused value or counter

Warning. A value node’s output isn’t connected to anything, or a Counter is read without any Change counter node ever updating it (so it stays 0). Connect or update it, or remove the unused node.

MM311 Event cannot be canceled

Error. Cancel event is wired to an event that doesn’t support cancellation, such as When player joins, Every N ticks, or When player steps on block. Remove Cancel event or move it under a cancelable event.

MM312 No active hit to modify

Error. Change damage is wired to an event without an active hit. Use it inside When entity is hurt, When player hits, or When mob hits; see Hits and damage.

MM313 Step after a Wait

Error. Cancel event or Change damage runs after a Wait. By the time the steps after a Wait run, the event is over, so there is nothing left to cancel or change. Move the step before the Wait.

Content

MM401 Too many shapeless ingredients

Error. A shapeless recipe requires more than 9 total ingredients, which won’t fit on a crafting grid. Reduce the ingredient counts.

MM402 Exceeds max stack size

Error. A recipe or villager trade uses or produces more items in one slot than that item can stack to (for example, tools and armor stack to 1, and smelting outputs 1). Lower the item count.

MM403 Invalid texture dimensions

Error. Item and block textures must be square, and worn armor textures must have a 2:1 aspect ratio (such as 64x32). Resize the texture image.

MM404 Wrong mob skin dimensions

Error. A custom mob texture doesn’t match the UV dimensions expected by its chosen body model. Clear the texture to use the default vanilla skin, or upload an image matching the dimensions shown in the message.

MM407 Invalid mob AI goals

Error. A mob lists the same AI goal more than once, includes the tempt goal without specifying Tempted by items, or sets Tempted by items without the tempt goal. Remove duplicate goals, and configure both tempt and Tempted by together.

MM408 Empty or invalid tag node

Error. A Tag node has an invalid tag name (expected namespace:path, such as c:gems/ruby) or lists no items or blocks. Fix the tag name and add at least one entry.

MM409 Vanilla loot node has no effect

Error. A Vanilla loot node adds no drops and leaves Replaces vanilla loot turned off, so it changes nothing. Add at least one drop, or enable Replaces vanilla loot if you want to clear the default drops.

MM410 Missing from creative tabs

Warning. An item, block, or fluid isn’t listed in any creative tab, so players won’t find it in the Creative inventory. Add it to a creative tab.

MM411 Block family conflict

Warning. A Block family assigns a block with the wrong shape for a slot, uses the same block in multiple slots, or includes both a wall and a trapdoor (which share the same crafting recipe pattern). Assign distinct blocks with matching shapes.

MM412 Advancement parent cycle

Error. An advancement sets itself as its own parent, or its parent chain loops back to itself. Choose a parent chain that leads cleanly to a root advancement.

MM413 Invalid or conflicting command

Error. A custom command collides with a built-in Minecraft command or another When command is run node, or has an invalid or duplicate argument name. Choose a unique command name, and name arguments starting with a lowercase letter followed by lowercase letters, digits, and _.

MM414 Enchantment has no effect

Warning. An enchantment defines no built-in effects and isn’t checked by any Enchantment level node, so applying it in-game does nothing. Add built-in effects or read its level with Enchantment level in an event flow.

MM415 Key name or key taken

Error. A When key is pressed node’s Name has no letter or digit, or another key node already has the same name or the same Key. Controls lists each key by its name, so give each key node a different one, such as Dash or Open map, and its own key: Controls marks a key bound twice as a conflict, and older releases send its presses to only one of them.

Items and blocks in events

MM501 Item use settings never triggered

Warning. An item sets Use up one, a cooldown, or durability, but no When item is used event handles it, so those settings never take effect. Connect the item to a When item is used event or clear those settings. (Food items are consumed by eating and don’t trigger this warning.)

MM502 Repeatable click without a cooldown

Warning. A reusable item in When item is used has no cooldown or durability, or When block is right-clicked has no cooldown (firing up to 5 times per second while right-click is held). Add a cooldown or durability so players can’t spam the effect; see Right-clicks.

MM504 Own use replaced

Warning. Some mod items have a built-in right-click action (armor equips, a bow or crossbow draws, storage opens, or a bucket pours), and listing one in When item is used replaces that action by default. Set the event’s Item’s own use to Keep to run both, or remove the item from the event. See Right-clicks.

MM505 Given or dropped count exceeds stack size

Error. Give item or Drop item tries to create more items than fit in a single stack (or more than 1 of an item with durability). Lower the count.

MM506 Impossible item match count

Warning. Is holding or wearing requires At least more matching items than are listed on the node, so it can never be true. Lower At least or add more items to the list.

MM507 Block already ticks natively

Error. Every N ticks for blocks lists a button, pressure plate, door, leaves, or falling block. Those block shapes use their own internal block ticks and can’t run custom interval ticks; remove them from the event.

MM508 Spawn event spawns its own mob

Warning. When mob spawns can reach Spawn mob for a mob it runs for: a mob it lists, any mob when it lists none, or one of the game’s mobs when it lists a tag, which may hold it. The step can be in a function it calls, or behind another When mob spawns whose mob runs this one. Each new mob runs the event again, without end, until the game crashes. List other mobs on the event, or spawn a different mob.

Modules and functions

MM601 Large module

Warning. A module (other than the built-in Content and Recipes views) contains more than 60 nodes. Consider splitting it into smaller feature modules so the graph stays easy to read.

MM602 Event split across modules

Warning. Multiple event nodes in separate modules handle the same event for the same item, block, or mob. Combine that logic into a single module so everything that happens on that trigger stays in one place.

MM603 Ambiguous step order across modules

Warning. Steps wired to the same flow output run from top to bottom based on canvas position, but two modules arrange those steps in different vertical orders (or split them across canvases). Keep those steps in one module, or match their top-to-bottom order across modules.

MM604 Disallowed node inside function

Error. Functions can only contain actions, value nodes, If branches, Java code, and calls to other functions. Move events, content nodes, recipes, and Cancel event out of the function.

MM605 Function path misses Output

Error. In a function that returns values or defines multiple flow outputs, every execution path must reach the Output node. Connect any dead-end branches to Output.

MM606 Unused function

Warning. Nothing in the mod calls this function. Call it from an event or another function, or remove it.

MM607 Function output read before call runs

Error. A node reads a value output from a function call along a flow path where that call hasn’t run yet. Only wire a call’s outputs into steps that execute after the call.

MM608 Invalid function ports

Error. A function must have between 1 and 12 inputs or outputs, unique camelCase port names starting with a lowercase letter (letters and digits only), no explicit flow inputs, and matching types for reserved parameter names (player, entity, level, pos). Rename or retype the port flagged in the message.

MM609 Missing or duplicate Input/Output node

Error. Every function must have one Input node and one Output node.

MM610 Loop or Wait inside a value or multi-exit function

Error. A function that returns values or has multiple flow exits cannot contain For each nearby or Wait, because returning from inside the loop would exit on the first entity, and the steps after a Wait run after the function has returned. Move the loop body, or the steps after the Wait, into a helper function with a single flow exit and call it from there.

MM611 Recursive function call

Error. Functions cannot call themselves, either directly or through a chain of other functions. Break the call cycle.

Java code

See Java code for details on ports, return types, and built-in imports.

MM701 Invalid Java code ports

Error. A Java code node’s method name or port names must start with a lowercase letter, contain only letters and digits, and be unique, and its outputs cannot mix flow with value types.

MM702 Invalid Java imports

Error. Every line in Imports must be a single fully qualified class name (such as java.util.Map) that doesn’t collide with pre-imported classes or another imported class of the same short name.

MM703 Java syntax error

Error. Code must parse as the body of a Java method (no package, import, or nested method declarations, no unclosed strings or brackets, no missing ;, and appropriate return statements for the node’s outputs). Fix the syntax error highlighted in the message.

MM704 Unresolved Java identifier

Warning. Code references an undeclared variable or an unimported class. Check that variable names match the node’s input ports, and add external classes to Imports (or reference them with their full package name).

Performance

These warnings catch patterns that do unnecessary work on the server thread; see Performance for details.

MM801 Per-player scan for mod blocks

Warning. Every N ticks is scanning around every online player for blocks added by your mod. Switch to Every N ticks for blocks on those blocks paired with For each nearby players so searches only run around placed blocks.

MM802 High-frequency search

Warning. A block or entity search (Block is with Within above 0, Count nearby, or For each nearby) runs unguarded inside Every N ticks faster than 10 ticks, or inside a step-on event that fires every tick. Increase Ticks to 10 or higher, or guard the search behind a cheaper If check first.

MM803 Expensive value computed multiple times

Warning. Inside a repeating flow, a search, Looked-at block, Java code value, or function call output is wired directly to multiple inputs, causing it to run once per wire. Insert Keep value into the flow beforehand and wire those inputs from Keep value.

MM804 Expensive condition checked first

Warning. Inside a repeating flow, an And or Or node evaluates a search or Looked-at block in A before a cheaper check in B. Swap A and B so the fast check short-circuits first.