crashed after running a while

[jingfengsama]

version:1.3.2
mc server version: 1.19.3

log:

crashed after running a while （at most 1 hour ）

settings:
{
"bot-account": {
"username": "silenpen_jf",
"password": "",
"type": "mojang"
},

"server": {
"ip": "dx.coreages.com",
"port": 25565,
"version": "1.19.3"
},

"position": {
"enabled": false,
"x": 0,
"y": 0,
"z": 0
},

"utils": {
"auto-auth": {
"enabled": true,
"password": "whitealbum2"
},

"anti-afk": {
  "enabled": true,
  "sneak": false,
  "jump": false,
  "rotate": false,

  "hit": {
    "enabled": true,
    "delay": 1000,
    "attack-mobs": true
  },

  "circle-walk": {
    "enabled": false,
    "radius": 2
  }
},

"chat-messages": {
  "enabled": false,
  "repeat": false,
  "repeat-delay": 60,

  "messages": [
    "I'm an afk bot",
    "My owner is jf",
    "I want be alone "
  ]
},

"chat-log": false,
"auto-reconnect": true,
"auto-reconnect-delay": 5000

}
}

crashed on cloud server too. (The only difference is that "hit" is not enabled)

[jingfengsama]

1.2 version not crash

[urFate]

Did you use it on AFK farm or something else? It's very difficult to say what is the root of your problem. If it's applicable, you can just disable mob hit feature.

It would be great if you sent a list/screenshot of the nearest mobs to the bot within a radius of 6 blocks, but I don't think this is already possible.

[jingfengsama]

one used but another just stay at home 

…

------------------ 原始邮件 ------------------ 发件人: "George ***@***.***>; 发送时间: 2023年2月3日(星期五) 凌晨2:28 收件人: ***@***.***>; 抄送: "Azure ***@***.***>; ***@***.***>; 主题: Re: [urFate/Afk-Bot] crashed after running a while (Issue #62) Did you use it on AFK farm or something else? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jingfengsama]

Did you use it on AFK farm or something else? It's very difficult to say what is the root of your problem. If it's applicable, you can just disable mob hit feature.

It would be great if you sent a list/screenshot of the nearest mobs to the bot within a radius of 6 blocks, but I don't think this is already possible.

one used on afk farm but another just stay at home

[jingfengsama]

i mean both of them crashed with the same crash log.

[jingfengsama]

{
"bot-account": {
"username": "jfmiao",
"password": "",
"type": "mojang"
},

"server": {
"ip": "dx.coreages.com",
"port": 25565,
"version": "1.19.3"
},

"position": {
"enabled": false,
"x": 0,
"y": 0,
"z": 0
},

"utils": {
"auto-auth": {
"enabled": true,
"password": "whitealbum2"
},

"anti-afk": {
  "enabled": false,
  "sneak": false,
  "jump": false,
  "rotate": false,

  "hit": {
    "enabled": false,
    "delay": 1000,
    "attack-mobs": false 
  },

  "circle-walk": {
    "enabled": false,
    "radius": 2
  }
},

"chat-messages": {
  "enabled": false,
  "repeat": false,
  "repeat-delay": 60,

  "messages": [
    "I'm a regular player ",
    "My owner is urFate_ ",
    "I want be alone ",
    "Visit my GitHub page! (urFate/Afk-Bot)"
  ]
},

"chat-log": false ,
"auto-reconnect": true,
"auto-reconnect-delay": 5000

}
}

cloud server 's setting ,crashed too

[Minionguyjpro]

I think I got the same error, the bot was working first but since a few days it randomly leaves after like 8 hours.

[Minionguyjpro]

I think it is an issue with the Node.js modules, and not the repo itself. But I am not sure...

[urFate]

I think it is an issue with the Node.js modules, and not the repo itself. But I am not sure...

Seems like it is. I'm really can't figure out what happened from this logs. E.g. somewhere in mineflayer, some entity is null, and blah, blah, blah...

So i've recommend to create new issue in mineflayer repo, idk...

[jingfengsama]

I think it is an issue with the Node.js modules, and not the repo itself. But I am not sure...

Seems like it is. I'm really can't figure out what happened from this logs. E.g. somewhere in mineflayer, some entity is null, and blah, blah, blah...

So i've recommend to create new issue in mineflayer repo, idk...

some clues here:
crash periodically whether hit mobs is on nor off.

certainly not work while rebirth in the main town

I have not joined other servers to find if the afk bot runs well.

bot of 1.2 version do not crash while 1.3 crashes no matter what configuration.

[jingfengsama]

find that two bots crashed at the same time on different windows servers.
may related to the data transmission between certain mc server and users.

you could check these by login this server(only need to regist).

[urFate]

I think it is an issue with the Node.js modules, and not the repo itself. But I am not sure...

Seems like it is. I'm really can't figure out what happened from this logs. E.g. somewhere in mineflayer, some entity is null, and blah, blah, blah...
So i've recommend to create new issue in mineflayer repo, idk...

some clues here: crash periodically whether hit mobs is on nor off.

certainly not work while rebirth in the main town

I have not joined other servers to find if the afk bot runs well.

bot of 1.2 version do not crash while 1.3 crashes no matter what configuration.

1.2 Version have outdated mineflayer, and outdated dependencies. So this bug could appear in latest releases of mineflayer. As temporary solution you can downgrade mineflayer in package.json to 4.1.0 which is used in 1.2 release. But you will lose 1.19.3 support.

[jingfengsama]

I think it is an issue with the Node.js modules, and not the repo itself. But I am not sure...

Seems like it is. I'm really can't figure out what happened from this logs. E.g. somewhere in mineflayer, some entity is null, and blah, blah, blah...
So i've recommend to create new issue in mineflayer repo, idk...

some clues here: crash periodically whether hit mobs is on nor off.
certainly not work while rebirth in the main town
I have not joined other servers to find if the afk bot runs well.
bot of 1.2 version do not crash while 1.3 crashes no matter what configuration.

1.2 Version have outdated mineflayer, and outdated dependencies. So this bug could appear in latest releases of mineflayer. As temporary solution you can downgrade mineflayer in package.json to 4.1.0 which is used in 1.2 release. But you will lose 1.19.3 support.

thx, that do ues

[urFate]

Updated mineflayer to 4.8.1 which can fix this issue.