Reproduce player workflows
Add behavior that exercises the system you actually want to measure.
Choose a workflow that matches the question in your run manifest. Keep the idle login test as a baseline.
Chat and commands
Use scoped commands to send a message from one bot first. For repeatable behavior, use a visual script or SDK chat recipe. Record message frequency and Minecraft permissions.
Movement and chunk loading
Use pathfinding or movement nodes to follow a known route. Repeat the same coordinates for comparison runs. Separate movement through existing chunks from new chunk generation. A random route changes the workload between runs.
Inventories and world actions
Use inventory workflows or the item-transfer recipe. Prepare the same container, items, and permissions before each run. Check the final inventory state as well as the action result.
Use a disposable world copy for block collection or excavation. Record the blocks and search radius. Restore the same fixture between comparisons.
Authentication and reconnects
Exercise one login path at a time: offline account, Microsoft account, or a server authentication plugin. Use auto-register only for the target plugin that needs it. Record the disconnect reason and time to reconnect. Do not mix duplicate-name disconnects with network recovery measurements.
Automate the scenario
Choose visual scripting, SDK, or plugins based on the required behavior. Export the script or save the complete SDK program with the run notes. Record any server-owned task IDs so you can cancel them during cleanup.
How is this page?
Last updated on