Mcfunction Debug

Description

This mod eases development of mcfunction by adding debugging tools for mcfunction!

/breakpoint: Stops execution of a function at the line with the breakpoint. During a breakpoint, no tick or load functions will run and execution will be paused at the current command but manually entered and command block entered commands will still run so its easy to debug. You can view the stack trace at the breakpoint.

Conditional breakpoint: Use /execute if ... run breakpoint

/resume: Resume execution after a breakpoint.

/step: After a breakpoint, can run /step to trigger the next line. This can be chained until the entire root function is executed for line by line debugging. You can view the stack trace after the step.

/print: Used for quick and dirty print statements. Automatically broadcasts results to all operators so they can be run in functions and still have the debugger see the output.

    /print context: Prints the context of execution. This consists of the entity executor (execute as), location (execute at), and rotation (execute facing).

    /print score [target(s)] [objective]: Prints the scores of the selected entities or targets in an objective

    /print selector [selector]: Prints all entities targeted by the selector. Similar to say [selector]

    /print data [data target] [optional: path]: Prints the data of the given target, with the option to filter by path. Similar to data get.

Printing entities with commands (i.e. /say) is now much more descriptive. Typing /print selector @e[type=slime] or /say @e[type=slime] will indicate the tags and location of each entity.

 By default, Minecraft's suppressed errors when running functions are unsuppressed. You can disable this in the config. You can view the stacktrace for each of these errors.

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install