Scripts

Scripts/bat/buildAllDebug.bat

@@ -0,0 +1,6 @@
+@echo off
+cd ../../
+call python RUN_THIS.py
+call git submodule update --init --recursive
+call dotnet build -c Debug
+pause

Scripts/bat/buildAllRelease.bat

@@ -0,0 +1,6 @@
+@echo off
+cd ../../
+call python RUN_THIS.py
+call git submodule update --init --recursive
+call dotnet build -c Release
+pause

Scripts/bat/readme.txt

@@ -0,0 +1,10 @@
+The files here will will, in order, build the game, copy the correct config file, launch the server, and launch the client.
+There are some variations of files, explained here
+
+The debug vs release build is simply what people dev in vs the actual server. The release build contains various 
+optimizations, while the debug build contains debugging tools. 
+If you're mapping, use the release build as it will run smoother.
+
+The Server config file simply matches the actual server config, while the other two have some cvar tweaks that come in 
+handy for their specific tasks. 
+Essentially only saves you some commands when you load in, but very convenient none the less.

Scripts/bat/runQuickAll.bat

@@ -0,0 +1,4 @@
+@echo off
+start runQuickServer.bat %*
+start runQuickClient.bat %*
+exit

Scripts/bat/runQuickClient.bat

@@ -0,0 +1,4 @@
+@echo off
+cd ../../
+call dotnet run --project Content.Client --no-build %*
+pause

Scripts/bat/runQuickServer.bat

@@ -0,0 +1,4 @@
+@echo off
+cd ../../
+call dotnet run --project Content.Server --no-build %*
+pause

Scripts/bat/runTestsIntegration.bat

@@ -0,0 +1,9 @@
+cd ..\..\
+dotnet restore
+dotnet build --configuration DebugOpt --no-restore /p:WarningsAsErrors=nullable /m
+mkdir Scripts\logs
+del Scripts\logs\Content.Tests.log
+dotnet test --no-build --configuration DebugOpt Content.Tests/Content.Tests.csproj -- NUnit.ConsoleOut=0 > Scripts\logs\Content.Tests.log
+del Scripts\logs\Content.IntegrationTests.log
+dotnet test --no-build --configuration DebugOpt Content.IntegrationTests/Content.IntegrationTests.csproj -- NUnit.ConsoleOut=0 NUnit.MapWarningTo=Failed > Scripts\logs\Content.IntegrationTests.log
+pause

Scripts/bat/runTestsYAML.bat

@@ -0,0 +1,7 @@
+cd ..\..\
+dotnet restore
+dotnet build --configuration DebugOpt --no-restore /p:WarningsAsErrors=nullable /m
+mkdir Scripts\logs
+del Scripts\logs\Content.YAMLLinter.log
+dotnet run --project Content.YAMLLinter/Content.YAMLLinter.csproj --no-build -- NUnit.ConsoleOut=0 > Scripts\logs\Content.YAMLLinter.log
+pause

Scripts/sh/buildAllDebug.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env sh
+
+# make sure to start from script dir
+if [ "$(dirname $0)" != "." ]; then
+  cd "$(dirname $0)"
+fi
+
+cd ../../
+
+python RUN_THIS.py
+git submodule update --init --recursive
+dotnet build -c Debug

Scripts/sh/buildAllRelease.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env sh
+
+# make sure to start from script dir
+if [ "$(dirname $0)" != "." ]; then
+  cd "$(dirname $0)"
+fi
+
+cd ../../
+
+python RUN_THIS.py
+git submodule update --init --recursive
+dotnet build -c Release

Scripts/sh/readme.txt

@@ -0,0 +1,10 @@
+The files here will will, in order, build the game, copy the correct config file, launch the server, and launch the client.
+There are some variations of files, explained here
+
+The debug vs release build is simply what people dev in vs the actual server. The release build contains various 
+optimizations, while the debug build contains debugging tools. 
+If you're mapping, use the release build as it will run smoother.
+
+The Server config file simply matches the actual server config, while the other two have some cvar tweaks that come in 
+handy for their specific tasks. 
+Essentially only saves you some commands when you load in, but very convenient none the less.

Scripts/sh/runQuickAll.sh

@@ -0,0 +1,14 @@
+#!/usr/bin/env sh
+
+# make sure to start from script dir
+if [ "$(dirname $0)" != "." ]; then
+    cd "$(dirname $0)"
+fi
+
+echo "will run both server and client in the same terminal so will give you both outputs at once"
+echo "dont mind fatl error relating to port 1212 does not seem to change anything"
+
+sh -e runQuickServer.sh &
+sh -e runQuickClient.sh
+
+exit

Scripts/sh/runQuickClient.sh

@@ -0,0 +1,9 @@
+#!/usr/bin/env sh
+
+# make sure to start from script dir
+if [ "$(dirname $0)" != "." ]; then
+    cd "$(dirname $0)"
+fi
+
+cd ../../
+dotnet run --project Content.Client --no-build

Scripts/sh/runQuickServer.sh

@@ -0,0 +1,9 @@
+#!/usr/bin/env sh
+
+# make sure to start from script dir
+if [ "$(dirname $0)" != "." ]; then
+    cd "$(dirname $0)"
+fi
+
+cd ../../
+dotnet run --project Content.Server --no-build