That "S" comes before "T" in the English alphabet (Race Selection Screen)

S

SquireZed

Well-known member
Generally hyphenation would be considered separately from alphabetization (which is apparently a word which I'm probably using wrong), with hyphenated entries coming either before or after non-hyphenated entries as if the hyphen itself were a character for consideration.

Also whoever manually updates the buttons for the character creation screen is probably very sad right now.
 
PersonMan

PersonMan

Well-known member
Incidentally Window's alphabetization ignores the hyphen, continuing as if it did not exist: putting Halfling between Half-Elf and Half-Orc.
 
H

Hawk

Well-known member
SteelStar said:
This will be fixed in Update 80.
Click to expand...

You respond to this? But not to actual bug reports for real problems, which sit there for months/years and still don't get fixed.

Like the annoying targeting problems of some cone attacks like horn of thunder, or the misfires of certain attacks, or the numerous cleric bugs, or bow-related issues, or hundreds of other combat-related problems.

Requiring time to fix problems is one thing, but it would be nice if some of the reports at least get acknowledged.
 
J

Jaspar

Well-known member
Hawk said:
You respond to this? But not to actual bug reports for real problems, which sit there for months/years and still don't get fixed.

Like the annoying targeting problems of some cone attacks like horn of thunder, or the misfires of certain attacks, or the numerous cleric bugs, or bow-related issues, or hundreds of other combat-related problems.

Requiring time to fix problems is one thing, but it would be nice if some of the reports at least get acknowledged.
Click to expand...

To be fair (to be fair) this was a 10 second fix and doesnt impact gameplay or need any level of testing beyond "can I still create a character with that race"). Im sure they are happy fixing all sorts of 10 second fixes if they didnt need much testing.
 
Visik

Visik

Well-known member
I'm not sure if I'm more baffled that someone cares enough to even mention an issue as trivial as this (though I guess I should acknowledge perfectionism is a very real thing), or that Steelstar was willing to even bother to consider it, let alone promise that it'll be fixed.

I mean, sure, it's a 5 minute fix, but it still has to be added to a bug list, fixed, tested, etc. Doesn't really seem worth the bother.

Still.. progress, I guess....
 
SteelStar

SteelStar

Senior Systems Designer
Visik said:
or that Steelstar was willing to even bother to consider it, let alone promise that it'll be fixed.
Click to expand...
The process really was
  1. Saw this thread
  2. I'd already fixed it over a month ago while adding the button for Duergar
  3. The fix is already verified through QA and in the U80 build
  4. There's no risk or legitimate controversy involved in stating outright that this particular issue will be fixed
  5. Took under 5 seconds to say it would be fixed in Update 80
  6. Went back to developing U80 features
It's really not more complicated than that, it's not a commentary on literally anything else. Saw something I could respond to, responded to it, went back to work.
 
PaleFox

PaleFox

Well-known member
SteelStar said:
The process really was
  1. Saw this thread
  2. I'd already fixed it over a month ago while adding the button for Duergar
  3. The fix is already verified through QA and in the U80 build
  4. There's no risk or legitimate controversy involved in stating outright that this particular issue will be fixed
  5. Took under 5 seconds to say it would be fixed in Update 80
  6. Went back to developing U80 features
It's really not more complicated than that, it's not a commentary on literally anything else. Saw something I could respond to, responded to it, went back to work.
Click to expand...
Wellllll..... aactualllllly.... Cordo is having trouble with a certain ring and your bulletpoint 4. <hihi>
 
H

Hawk

Well-known member
Jaspar said:
To be fair (to be fair) this was a 10 second fix and doesnt impact gameplay or need any level of testing beyond "can I still create a character with that race"). Im sure they are happy fixing all sorts of 10 second fixes if they didnt need much testing.
Click to expand...
SteelStar said:
The process really was
  1. Saw this thread
  2. I'd already fixed it over a month ago while adding the button for Duergar
  3. The fix is already verified through QA and in the U80 build
  4. There's no risk or legitimate controversy involved in stating outright that this particular issue will be fixed
  5. Took under 5 seconds to say it would be fixed in Update 80
  6. Went back to developing U80 features
It's really not more complicated than that, it's not a commentary on literally anything else. Saw something I could respond to, responded to it, went back to work.
Click to expand...

My point is being missed entirely. Like I said... it's understandable if bugs need time to be investigated or fixed...

But valid bug reports sit in the queue and on the forums for months, and get NOTHING in acknowledgment.

Where's that 5 seconds to respond to someone's 2 month old bug report (with bugs that have existed for YEARS)? Players would at least be partly satisfied if someone responded and said either:

A> "We've got this on our list, but we can't say when it will be fixed."
B> "We believe this is working as intended and would need more info to investigate if we are wrong."

It's really not asking for much, for people who are taking the time to help you make your game better. No one is asking for a reply 1 day after a report... but 2 months, 4 months, years... is too much.
 
H

Hobgoblin

Less Nerfy Nerfy more fixy fixy
SteelStar said:
The process really was
  1. Saw this thread
  2. I'd already fixed it over a month ago while adding the button for Duergar
  3. The fix is already verified through QA and in the U80 build
  4. There's no risk or legitimate controversy involved in stating outright that this particular issue will be fixed
  5. Took under 5 seconds to say it would be fixed in Update 80
  6. Went back to developing U80 features
It's really not more complicated than that, it's not a commentary on literally anything else. Saw something I could respond to, responded to it, went back to work.
Click to expand...
you work sir?


how dare you!


drop everything and work on the gamebreaking bug that i reported years ago and refuse to name again!

if you dont im gonna take away your coffee!
 
Visik

Visik

Well-known member
SteelStar said:
The process really was
  1. Saw this thread
  2. I'd already fixed it over a month ago while adding the button for Duergar
  3. The fix is already verified through QA and in the U80 build
  4. There's no risk or legitimate controversy involved in stating outright that this particular issue will be fixed
  5. Took under 5 seconds to say it would be fixed in Update 80
  6. Went back to developing U80 features
It's really not more complicated than that, it's not a commentary on literally anything else. Saw something I could respond to, responded to it, went back to work.
Click to expand...
🤣🤣🤣

OK, fair, but.. that's not what you said. You said, "This will be fixed in Update 80."
Not.. this is already fixed and that fix is coming out in Update 80.

It's a rather crucial distinction. Had you said the latter, I'd have had no comment.
 
You must log in or register to reply here.
Top