-
Notifications
You must be signed in to change notification settings - Fork 940
Fix incorrect unique item name casing - BloodSlayer #8376
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
base: master
Are you sure you want to change the base?
Conversation
|
Is this meant to be two words instead of one, kind of how we had Red Vex but BlackJade in 1.09? Should the correction here be to change this to Blood Slayer instead of Bloodslayer? Bloodslayer isn't a word. |
Stonecleaver, Crackrust, Thundercall, etc. |
1 similar comment
Stonecleaver, Crackrust, Thundercall, etc. |
While good examples to counter Bloodslayer not being a word, it still feels inconsistent with how BlackJade was modified to Black Jade and not Blackjade, no? Though, that was a unique monster name and not an item name, so maybe it doesn't have to be consistent between the two. Just pointing it out as something to think about for whomever reviews the PR I guess. |
I'm not sure why BlackJade was changed to Black Jade. It makes more sense to keep it as Blackjade because there was no case difference in vanilla and players read it as BLACKJADE. Problems like these are only visible in DevilutionX. |
StephenCWills
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why BlackJade was changed to Black Jade.
It was almost certainly because "Black Jade" is more consistent with "Red Vex" than "Blackjade". On that note, "Bloodslayer" is more consistent with "Hellslayer" than "Blood Slayer".
BloodSlayer -> Bloodslayer