i can`t start bot

[kasyanko]

node main.js [ './andy.json' ] SES_UNCAUGHT_EXCEPTION: {} Agent process exited with code 4294967295 and signal null Agent process ./andy.json exited too quickly and will not be restarted. All agent processes have ended. Exiting.

[hackdefendr]

What version of NodeJS are you using? Which OS? Needs more info.

[Tascok]

I have the same problem, I'm using Ubuntu, and the latest js

[Tascok]

[hackdefendr]

You may have to create a specific API key for OpenAI and assign it to the models you want to use. Simply using the default settings in andy.json probably won't work out of box. See below, I configured my API key to use chatgpt-4o-latest instead of the default.

My system:

Distributor ID: Ubuntu
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble

The bot:

~/devel/mindcraft$ node main.js
[ './andy.json' ]
Starting agent with profile: ./andy.json
Starting agent initialization with profile: ./andy.json
Initializing action manager...
Initializing prompter...
Using chat settings: { model: 'chatgpt-4o-latest', api: 'openai' }
Using embedding settings: { api: 'openai' }
Initializing history...
Initializing coder...
Initializing npc controller...
Initializing memory bank...
Initializing self prompter...
Initializing examples...
Error with embedding model, using word overlap instead.
Error with embedding model, using word overlap instead.
Logging into minecraft...
Loaded memory: Base: forest biome (2320.7, -51, 1441.3); current savanna. Goals: survival, upgrade tools, efficient crafting. ClearLag affects items. Issues: crafting command error ('Player not found') persists; retry fixes or !restart. Task: gather table materials, make wooden pickaxe, mine stone. Nearby: stone, dirt, ores, etc. Attempted incorrect !mine command; corrected to !collectBlocks. Focus: adapt commands, resolve glitches, optimize tasks. Use !rememberHere for key spots.
Logged in!
Prismarine viewer web server running on *:3000

Let's start with the whole log to see if something else is happening above what your screenshot shows.

[hackdefendr]

Oh I think I figure this out. It is your version of NodeJS. I tried using the latest version recently for something else and hit the exact same error. Rolling back to the previous LTS version fixed it for me.