Along this tutorial we are creating the Allies side version of the Westerplatte assault mission. Hence, we need to have available the Westerplatte map. Just download the *.sd7 file, and place it at $HOME/.spring/maps/ folder.
We are using SpringLobby to start a "SpringBoard" game in Westerplatte map.
Right after launching SpringLobby, head to the Singleplayer tab.
We are selecting the Westerplatte map, the SpringBoard S44 game, and the 104 engine, as it can be appreciated in the following figure:
In this mission we have the Polish faction handled by the player, and the German faction managed by the AI. Therefore, we should add a nullAI bot, using the "Add bot..." button. Don't worry about starting positions, factions and colors. We are modifing them later. You are probably seeing something like that:
We are ready, press on "Start" button to launch SpringBoard!
After game loading, you are probably facing a map, without units. That's normal, in the campaign the default units are not spawned by default. Instead of that, user is responsible of setting the initial units.
Right now, we focus on the configuration of the scenario, including the teams.
To do that, select the Misc tab in the right panel, and then press the Info button. Fill the fields with the following values:
Name: S44 Westerplatte - allies
Description: Westerplatte assault (allies side)
Now we want to configure the teams. Indeed, we press the Teams button, which should show something similar to the following:
As you can see, there is a team, named "Team: 1", controlled by the player, and another team, called "Team: 0: NullAI", controlled by the AI.
Let's start editing "Team: 1" (the blue one), pressing on the Edit button. A new dialog is open, in which we shall set the following values:
Color: Select a brown color, like it is depicted in the following figure
Close the team edition dialog, and proceed to modify the other team, "Team: 0: NullAI", with the following values:
Color: Select a gray color, like it is depicted in the following figure
After closing the dialogs, you successfully set up your new mission!
Save and exit
Now we are saving the work. To do that press the 'Ctrl+Shift+S' keys combination (or use the Save project as... button), which will open a new dialog.
In such dialog, just write westerplatte_allies, and press OK. The game is probably hanging for a couple of seconds.
After saving the game, we are quitting SpringBoard. Hey! I want to continue working. Don't worry, we are soon visiting the next part of the tutorial.
But there are two main reasons to quit the current project:
First, we are using the non-patched 104 engine, which has very short available LUA memory.
Second, we are interested in preparing everything to directly work in such new project with a simple terminal command.
Hence, we are clicking the Exit button at top-left corner, and coming back to the OS.
Your project has been saved in $HOME/.spring/springboard/projects/westerplatte_allies (if you cannot find it, check in $HOME/.config/spring/springboard/projects/westerplatte_allies folder, conveniently swaping the commands below). However, we are specifically interested in making the project/game visible to spring, so we are creating a symbolic links typing:
ln -s $HOME/.spring/springboard/projects/westerplatte_allies $HOME/.spring/games/westerplatte_allies.sdd```Hereinafter, we'll always come back to our project executing the following command in a terminal:```$HOME/.spring/engine/104.0-longmem/bin/spring $HOME/.spring/games/westerplatte_allies.sdd/script-dev.txt```Now you are ready to move forward to the [next part of the tutorial](https://gitlab.com/Spring1944/spring1944/wikis/campaign/howto_deploy).