Skip to content

feat: Update build copy task to use multiple paths#69

Merged
Extremelyd1 merged 3 commits into
Extremelyd1:mainfrom
Liparakis:main
May 22, 2026
Merged

feat: Update build copy task to use multiple paths#69
Extremelyd1 merged 3 commits into
Extremelyd1:mainfrom
Liparakis:main

Conversation

@Liparakis
Copy link
Copy Markdown
Contributor

No description provided.

Comment thread SSMP/SSMP.csproj Outdated
</ItemGroup>

<Copy SourceFiles="@(Binaries)" DestinationFolder="$(SilksongFolder)/BepInEx/plugins/$(TargetName)"/>
<Copy SourceFiles="@(Binaries)" DestinationFolder="%(SilksongFolders.Identity)"/>
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means that the property name SilksongFolder from SilksongPath.props is no longer accurate right? Because we copy directory to its path rather than the subfolders /BepInEx/plugins/SSMP?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it's directly deploying to the specified path.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should probably be renamed then for clarity.

Also, what is the new syntax for defining multiple output paths?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will rename it but probably tomorrow.

Also, what is the new syntax for defining multiple output paths?

You need to have SilksongPath.props with this piece of metadata:
The path seperator is the ; character.

<Project>
   <PropertyGroup>
       <SilksongFolder>
           D:\Games\Hollow Knight - Silksong\BepInEx\plugins;
           D:\SteamLibrary\steamapps\common\Hollow Knight Silksong\BepInEx\plugins\SSMP
       </SilksongFolder>
   </PropertyGroup>
</Project>

Copy link
Copy Markdown
Owner

@Extremelyd1 Extremelyd1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't entirely agree with the way you've added items and properties, so I've reworked the configuration to what I think is the most straightforward and maintainable.

This way you can define multiple output directories by defining multiple OutputDirectory tags in the LocalBuildProperties.props file.

@Extremelyd1 Extremelyd1 merged commit 39443cb into Extremelyd1:main May 22, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants