You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of this time of writing there is no option in the autobotchk script to start the bot in the venv environment with python support. It would be a nice addition and would make help autobotchk regain it's usefulness again in automating bot start/boot processes.
Just like the new -systemd variable, one could add a variable in the likes of -venv or -python to the scripts options.
Currently its puts a nice line in the crontab or setup systemd but then the bot crashes as the python module requires more then it is getting. See below :
--- Loading eggdrop v1.10.0 (Sat Nov 9 2024)
Tcl error in file 'eggdrop':
invalid command name ELF
CONFIG FILE NOT LOADED (NOT FOUND, OR ERROR)
Thanks for doing all this great work and making eggdrop available to us all. Hoping that it will not take to long to fix this issue /add this feature.
Regards DiMTRX
The text was updated successfully, but these errors were encountered:
As of this time of writing there is no option in the autobotchk script to start the bot in the venv environment with python support. It would be a nice addition and would make help autobotchk regain it's usefulness again in automating bot start/boot processes.
Just like the new -systemd variable, one could add a variable in the likes of -venv or -python to the scripts options.
Currently its puts a nice line in the crontab or setup systemd but then the bot crashes as the python module requires more then it is getting. See below :
--- Loading eggdrop v1.10.0 (Sat Nov 9 2024)
Tcl error in file 'eggdrop':
invalid command name ELF
Thanks for doing all this great work and making eggdrop available to us all. Hoping that it will not take to long to fix this issue /add this feature.
Regards DiMTRX
The text was updated successfully, but these errors were encountered: