Skip to content

fix(task-init): only skip init when saved state exists#734

Open
Wuodan wants to merge 1 commit intomindcraft-bots:developfrom
Wuodan:fix/load_memory-with-task
Open

fix(task-init): only skip init when saved state exists#734
Wuodan wants to merge 1 commit intomindcraft-bots:developfrom
Wuodan:fix/load_memory-with-task

Conversation

@Wuodan
Copy link
Contributor

@Wuodan Wuodan commented Mar 11, 2026

Use save_data instead of load_mem when deciding whether to run initBotTask().

This fixes the case where load_memory=true but no saved bot state exists: the bot could skip task initialization and start without the configured task setup, such as initial inventory.

Use `save_data` instead of `load_mem` when deciding whether to run `initBotTask()`.

This fixes the case where `load_memory=true` but no saved bot state exists:
the bot could skip task initialization and start without the configured task setup, such as initial inventory.
@Sweaterdog
Copy link
Contributor

Use save_data instead of load_mem when deciding whether to run initBotTask().

This fixes the case where load_memory=true but no saved bot state exists: the bot could skip task initialization and start without the configured task setup, such as initial inventory.

Not sure if this is needed, I have used the load_memory=true flag when making a new agent.

@Wuodan
Copy link
Contributor Author

Wuodan commented Mar 12, 2026

When using a contruction task with an initial_inventory, then load_memory=true prevents the inventory from every being filled.

@Sweaterdog
Copy link
Contributor

When using a contruction task with an initial_inventory, then load_memory=true prevents the inventory from every being filled.

You mean with Minecollab? I'll have to test it then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants