Update custom assets warning about package versions

[Copilot]

The warning after the .csproj example in custom assets docs only mentioned matching Stride.Core.Assets version, but users also need to update TargetFrameworks and all other package versions to match their Stride installation.

Changes:

• Expanded warning to cover both TargetFrameworks and all package versions
• Added explicit note that 4.2.0.1 is shown for reference only

> [!Warning]
> Make sure that the `TargetFrameworks` and all package versions match your current Stride version. The example above shows version 4.2.0.1 for reference.

Fixes #455

Original prompt

Problem

The custom assets documentation page has a code example showing Stride package versions for 4.2.0.1, which may be misleading to users running different versions of Stride. This is reported in issue #455.

Solution

Update the existing warning after the .csproj code example to clarify that:

1. Both TargetFrameworks and all package versions should match the user's current Stride version
2. The example shows version 4.2.0.1 for reference only

File to Update

en/manual/scripts/custom-assets.md

Specific Changes

Replace the existing warning:

> [!Warning]
> Make sure that the version specified for `Stride.Core.Assets` matches the other package's versions.

With:

> [!Warning]
> Make sure that the `TargetFrameworks` and all package versions match your current Stride version. The example above shows version 4.2.0.1 for reference.

This change expands the warning to cover both the target framework and all package versions, making it clearer that users should update these values to match their installed Stride version.

Related to issue #455

This pull request was created as a result of the following prompt from Copilot chat.

Problem

The custom assets documentation page has a code example showing Stride package versions for 4.2.0.1, which may be misleading to users running different versions of Stride. This is reported in issue #455.

Solution

Update the existing warning after the .csproj code example to clarify that:

1. Both TargetFrameworks and all package versions should match the user's current Stride version
2. The example shows version 4.2.0.1 for reference only

File to Update

en/manual/scripts/custom-assets.md

Specific Changes

Replace the existing warning:

> [!Warning]
> Make sure that the version specified for `Stride.Core.Assets` matches the other package's versions.

With:

> [!Warning]
> Make sure that the `TargetFrameworks` and all package versions match your current Stride version. The example above shows version 4.2.0.1 for reference.

This change expands the warning to cover both the target framework and all package versions, making it clearer that users should update these values to match their installed Stride version.

Related to issue #455

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.