The command from the instructions on github: dotnet restore produces the following error:
PS C:\Users\rykli\Python Projects\2025-Zooscape-main> dotnet restore
Determining projects to restore…
Could not execute because the specified command or file was not found.
Could not execute because the specified command or file was not found.
Could not execute because the specified command or file was not found.
Could not execute because the specified command or file was not found.
Could not execute because the specified command or file was not found.
C:\Users\rykli\Python Projects\2025-Zooscape-main\Domain\Zooscape.Domain.csproj(9,5): error MSB3073: The command “dotne
t husky install” exited with code 1.
C:\Users\rykli\Python Projects\2025-Zooscape-main\Zooscape\Zooscape.csproj(52,5): error MSB3073: The command “dotnet hu
sky install” exited with code 1.
C:\Users\rykli\Python Projects\2025-Zooscape-main\SignalRHub\Zooscape.Infrastructure.SignalRHub.csproj(16,5): error MSB
3073: The command “dotnet husky install” exited with code 1.
C:\Users\rykli\Python Projects\2025-Zooscape-main\CloudIntegration\Zooscape.Infrastructure.CloudIntegration.csproj(19,5
): error MSB3073: The command “dotnet husky install” exited with code 1.
C:\Users\rykli\Python Projects\2025-Zooscape-main\Application\Zooscape.Application.csproj(16,5): error MSB3073: The com
mand “dotnet husky install” exited with code 1.
Also tried in Zooscape directory, same result. I however can run.bat and successfuly build the project.
Hey guys, I seem to have run into the same issue and just skipped the dotnet restore step. I also have just run the run.bat and then ran the JavaBot from the StarterBots folder. It worked fine initially (although I had to just slightly change the code to generate my own UUID for the registration token), but everytime after the first run it seems to automatically connect a JavaBot without me having to start up my java code once the engine is running. Anyone able to assist if possible? Thanks in advance!
Thanks for the feedback! We use husky for internal development, but it seems it didn’t carry over nicely on the deployment. We will investigate for the next release
The run.sh and run.bat commands build and run on docker, with husky disabled, so please use those for the time being. If you want to build and run without docker, you should be able to set HUSKY=0 in your shell’s environment using the following:
# Bash/Zsh
export HUSKY=0
# Fish
set -x HUSKY 0
# PowerShell
$Env:HUSKY = "0"
# Cmd
set HUSKY=0
We have just released version 2025.0.1 that should address this issue. Please pull the latest changes, and try again
If you have any other issues, we welcome your feedback!