-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can I set a custom name? #315
Comments
Hi! This isn't possible right now. Ludusavi will always display the name from the manifest. The aliases can be used for CLI input, but they're not used for display purposes. The closest thing right now would be making a custom game that's the same as the standard game, and then disabling (unchecking) the standard game in the backup list, but the standard name will still show up in the list as a disabled entry. I'm open to adding something to help with this, but I have some questions to get a better idea of your use case:
|
Yes, I tried to set a custom for him, but it caused me to have too many projects, which made him look a little confused, so I wondered if I could overwrite the original and keep it simple
|
I'd like to add something regarding this issue. Having a different display name causes the playnite plugin to not be able to backup some games. As an example, to make it more clear, it cannot distinguish between the "Control" game and its Ultimate Edition, which is called "Control Ultimate Edition". Therefore, unless changing the name to the latter by creating a custom game, it won't be able to perform the automatic playnite backup. But changing the name will cause to have duplicates, one called "Control" and the other "Control Ultimate Edition". |
This will be available in the next release:
|
This is great. This is so exciting |
What's your question?
I want to set the scanned game name to the name I'm used to. But with custom it turns into two pieces. Using an alias will result in the game not being found. How can I change the scanned game name
The text was updated successfully, but these errors were encountered: