Use <GUID> property if present for BepInExPluginGuid#20
Merged
ManlyMarco merged 2 commits intoBepInEx:masterfrom Mar 20, 2026
Merged
Use <GUID> property if present for BepInExPluginGuid#20ManlyMarco merged 2 commits intoBepInEx:masterfrom
ManlyMarco merged 2 commits intoBepInEx:masterfrom
Conversation
Contributor
Author
|
The templates can also be changed so they can store the GUID in this property when generating. |
ManlyMarco
approved these changes
Feb 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Using the AssemblyName isn't always useful or unique for plugin GUIDs, so an optional custom property can be defined so they can be kept separate, especially if a plugin developer decides to change the assembly name for whatever reason.