GothicProfessional

[damianut]

🚀 Let's get started

• [X] I confirm that I want the repository's name and description to be used for the patch.
• [X] I have familiarized myself with the documentation of Ninja.

Content scripts

• [X] Gothic 1
• [ ] Gothic Sequel
• [X] Gothic 2 Classic
• [X] Gothic 2 NotR

Ikarus and LeGo

• [X] Ikarus
• [ ] LeGo

Content initialization

• [X] Content initialization function

Menu initialization

• [ ] Menu initialization function

Menu scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Particle FX scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Visual FX scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Sound FX scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Music scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Camera scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Fight AI scripts

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Output units

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

Animations

• [ ] Gothic 1
• [ ] Gothic Sequel
• [ ] Gothic 2 Classic
• [ ] Gothic 2 NotR

[github-actions[bot]]

Initializing the project

Completed!

Duration: 1.1 seconds

---

# 🎉 GothicProfessional 🎉 #### You are now ready to start working on your Gothic patch. The following steps are recommended to get you started.

[!TIP] A VM script was created with which you can create the VDF using GothicVDFS

Next Steps

:one: Add Scripts

Add any necessary scripts in the subdirectories Content and System and register them in the respective SRC files. Be sure to follow the naming convention to ensure compatibility with other mods.

:two: Add Resources

If you have further resources like textures, meshes or animations, add them in the respective directory (_compiled) in the directory _work and add their paths to the VM script. See the comments inside the VM script.

:three: Build the Patch

In GothicVDFS click Builder and then Open Script. Navigate to and open GothicProfessional.vm. Adjust Root Path to the same directory. Confirm the contents of the fields and click Build volume. Alternatively, you can build the VDF using the automatic GitHub workflow of this repository.

:four: Consult the documentation

Have a look into the Ninja documentation to learn more about the possibilities of using Ninja. You can find the documentation here.

:five: Test the Patch

Throughly test your patch in Gothic with different mods. It is important to try various mods that do not use Ikarus!

:six: Setup auto-deployment on Steam Workshop (optional)

If you release your patch on the Steam Workshop for Gothic 1 and/or Gothic 2, you can enable auto-deployment of new versions by following the steps in `.github/workflows/build.yml`.

:seven: Increase Visibility on GitHub

To make your patch repository easier to find on GitHub, you may want to add the following common keyword topics by editing the repository details. gothic gothic1 gothic2 modding-gothic ninja daedalus