Create a system that allows stacking and executing tasks in order, enabling behavior like building automation flows.
Example usage:
.queue .come 100 65 200
.queue .mine area 4
.queue .throwall
.run
Context & Approach Guidance
This issue is more about software architecture than Minecraft.
Think about:
Creating a queue structure (FIFO)
Storing commands as functions or objects
Running tasks asynchronously one after another
Providing progress updates
Handling errors without breaking the whole queue
Suggested design questions:
What information should a task contain?
How will .run trigger processing?
What happens if one task fails — skip or stop?
How do we communicate progress to the user?
Acceptance Criteria
.queue stores tasks
.run executes tasks in sequence
.stop cancels execution and clears queue
Friendly console + chat logging
Labels: hard, architecture, feature
Create a system that allows stacking and executing tasks in order, enabling behavior like building automation flows.
Example usage:
.queue .come 100 65 200
.queue .mine area 4
.queue .throwall
.run
Context & Approach Guidance
This issue is more about software architecture than Minecraft.
Think about:
Creating a queue structure (FIFO)
Storing commands as functions or objects
Running tasks asynchronously one after another
Providing progress updates
Handling errors without breaking the whole queue
Suggested design questions:
What information should a task contain?
How will .run trigger processing?
What happens if one task fails — skip or stop?
How do we communicate progress to the user?
Acceptance Criteria
.queue stores tasks
.run executes tasks in sequence
.stop cancels execution and clears queue
Friendly console + chat logging
Labels: hard, architecture, feature